linux.git/fs/read_write.c, branch v2.6.29

[CVE-2009-0029] System call wrappers part 20

2009-01-14T13:15:26+00:00

Signed-off-by: Heiko Carstens

[CVE-2009-0029] System call wrappers part 19

2009-01-14T13:15:26+00:00

Signed-off-by: Heiko Carstens

[CVE-2009-0029] System call wrappers part 16

2009-01-14T13:15:25+00:00

Signed-off-by: Heiko Carstens

[CVE-2009-0029] System call wrapper special cases

2009-01-14T13:15:18+00:00

System calls with an unsigned long long argument can't be converted with
the standard wrappers since that would include a cast to long, which in
turn means that we would lose the upper 32 bit on 32 bit architectures.
Also semctl can't use the standard wrapper since it has a 'union'
parameter.

So we handle them as special case and add some extra wrappers instead.

Signed-off-by: Heiko Carstens

[CVE-2009-0029] Convert all system calls to return a long

2009-01-14T13:15:14+00:00

Convert all system calls to return a long. This should be a NOP since all
converted types should have the same size anyway.
With the exception of sys_exit_group which returned void. But that doesn't
matter since the system call doesn't return.

Signed-off-by: Heiko Carstens

vfs: lseek(fd, 0, SEEK_CUR) race condition

2009-01-05T16:53:07+00:00

This patch fixes a race condition in lseek. While it is expected that
unpredictable behaviour may result while repositioning the offset of a
file descriptor concurrently with reading/writing to the same file
descriptor, this should not happen when merely *reading* the file
descriptor's offset.

Unfortunately, the only portable way in Unix to read a file
descriptor's offset is lseek(fd, 0, SEEK_CUR); however executing this
concurrently with read/write may mess up the position.

[with fixes from akpm]

Signed-off-by: Alain Knaff 
Signed-off-by: Andrew Morton 
Signed-off-by: Al Viro

[PATCH] generic_file_llseek tidyups

2008-10-23T09:12:59+00:00

Add kerneldoc for generic_file_llseek and generic_file_llseek_unlocked,
use sane variable names and unclutter the code.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

Remove BKL from remote_llseek v2

2008-07-02T21:06:27+00:00

- Replace remote_llseek with generic_file_llseek_unlocked (to force compilation
failures in all users)
- Change all users to either use generic_file_llseek_unlocked directly or
take the BKL around. I changed the file systems who don't use the BKL
for anything (CIFS, GFS) to call it directly. NCPFS and SMBFS and NFS
take the BKL, but explicitely in their own source now.

I moved them all over in a single patch to avoid unbisectable sections.

Open problem: 32bit kernels can corrupt fpos because its modification
is not atomic, but they can do that anyways because there's other paths who
modify it without BKL.

Do we need a special lock for the pos/f_version = 0 checks?

Trond says the NFS BKL is likely not needed, but keep it for now
until his full audit.

v2: Use generic_file_llseek_unlocked instead of remote_llseek_unlocked
    and factor duplicated code (suggested by hch)

Cc: Trond.Myklebust@netapp.com
Cc: swhiteho@redhat.com
Cc: sfrench@samba.org
Cc: vandrove@vc.cvut.cz

Signed-off-by: Andi Kleen 
Signed-off-by: Andi Kleen 
Signed-off-by: Jonathan Corbet

fs: use loff_t type instead of long long

2008-04-22T22:17:11+00:00

Use offset type consistently.

Signed-off-by: David Sterba 
Signed-off-by: Linus Torvalds

remove the unused exports of sys_open/sys_read

2008-02-08T17:22:36+00:00

These exports (which aren't used and which are in fact dangerous to use
because they pretty much form a security hole to use) have been marked
_UNUSED since 2.6.24 with removal in 2.6.25.  This patch is their final
departure from the Linux kernel tree.

Signed-off-by: Arjan van de Ven 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds