diff options
| author | Christoph Lameter <christoph@graphe.net> | 2005-06-23 00:10:17 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-06-23 09:45:33 -0700 |
| commit | 45778ca819accab1a4a3378b3566cab0f189164f (patch) | |
| tree | 9214491346c8d2d91eb1a11cb6c2e6a9387e4290 /fs/nfs | |
| parent | 280dedb8d64ccfe1166ae03d3b254fc3b65de6a5 (diff) | |
| download | kernel_samsung_smdk4412-45778ca819accab1a4a3378b3566cab0f189164f.tar.gz kernel_samsung_smdk4412-45778ca819accab1a4a3378b3566cab0f189164f.tar.bz2 kernel_samsung_smdk4412-45778ca819accab1a4a3378b3566cab0f189164f.zip | |
[PATCH] Remove f_error field from struct file
The following patch removes the f_error field and all checks of f_error.
Trond said:
f_error was introduced for NFS, and made sense when we were guaranteed
always to have a file pointer around when write errors occurred. Since
then, we have (for various reasons) had to introduce the nfs_open_context in
order to track the file read/write state, and it made sense to move our
f_error tracking there too.
Signed-off-by: Christoph Lameter <christoph@lameter.com>
Acked-by: Trond Myklebust <trond.myklebust@fys.uio.no>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/nfs')
| -rw-r--r-- | fs/nfs/direct.c | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/fs/nfs/direct.c b/fs/nfs/direct.c index d6a30c844de..6537f2c4ae4 100644 --- a/fs/nfs/direct.c +++ b/fs/nfs/direct.c @@ -751,11 +751,6 @@ nfs_file_direct_write(struct kiocb *iocb, const char __user *buf, size_t count, retval = -EFAULT; if (!access_ok(VERIFY_READ, iov.iov_base, iov.iov_len)) goto out; - if (file->f_error) { - retval = file->f_error; - file->f_error = 0; - goto out; - } retval = -EFBIG; if (limit != RLIM_INFINITY) { if (pos >= limit) { |