diff options
| author | NeilBrown <neilb@suse.de> | 2008-06-19 02:11:09 +0200 |
|---|---|---|
| committer | J. Bruce Fields <bfields@citi.umich.edu> | 2008-06-23 19:02:50 +0200 |
| commit | 599eb3046a1380f31c65715f3940184c531c90cb (patch) | |
| tree | 559719d700d80fc2acef1ff77506daa351cebba9 /fs/binfmt_em86.c | |
| parent | nfsd: fix race in nfsd_nrthreads() (diff) | |
| download | linux-599eb3046a1380f31c65715f3940184c531c90cb.tar.xz linux-599eb3046a1380f31c65715f3940184c531c90cb.zip | |
knfsd: nfsd: Handle ERESTARTSYS from syscalls.
OCFS2 can return -ERESTARTSYS from write requests (and possibly
elsewhere) if there is a signal pending.
If nfsd is shutdown (by sending a signal to each thread) while there
is still an IO load from the client, each thread could handle one last
request with a signal pending. This can result in -ERESTARTSYS
which is not understood by nfserrno() and so is reflected back to
the client as nfserr_io aka -EIO. This is wrong.
Instead, interpret ERESTARTSYS to mean "try again later" by returning
nfserr_jukebox. The client will resend and - if the server is
restarted - the write will (hopefully) be successful and everyone will
be happy.
The symptom that I narrowed down to this was:
copy a large file via NFS to an OCFS2 filesystem, and restart
the nfs server during the copy.
The 'cp' might get an -EIO, and the file will be corrupted -
presumably holes in the middle where writes appeared to fail.
Signed-off-by: Neil Brown <neilb@suse.de>
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Diffstat (limited to 'fs/binfmt_em86.c')
0 files changed, 0 insertions, 0 deletions