From: walt <wa1ter@myrealbox.com>
To: nfs@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfsd oops in current -git
Date: Fri, 13 Jul 2007 12:18:19 -0700 [thread overview]
Message-ID: <f78j5t$ttc$1@sea.gmane.org> (raw)
In-Reply-To: <20070713165001.GV5328@kernel.dk>
Jens Axboe wrote:
>>> On 07/13/2007 09:40 AM, Patrick McHardy wrote:
>>>> I get this oops with current -git:
...
> Patrick, does this work?
>
> diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
> index 8604e35..945b1ce 100644
> --- a/fs/nfsd/vfs.c
> +++ b/fs/nfsd/vfs.c
> @@ -879,6 +879,7 @@ nfsd_vfs_read(struct svc_rqst *rqstp, struct svc_fh *fhp, struct file *file,
> .u.data = rqstp,
> };
>
> + rqstp->rq_resused = 1;
> host_err = splice_direct_to_actor(file, &sd, nfsd_direct_splice_actor);
> } else {
> oldfs = get_fs();
>
Hi Jens,
I'm not Patrick, but this patch fixes the nfsd problem I posted about
in the webservers-stopped-working thread earlier today. Many thanks.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-07-13 19:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 13:40 nfsd oops in current -git Patrick McHardy
2007-07-13 16:27 ` Chuck Ebbert
2007-07-13 16:27 ` Chuck Ebbert
2007-07-13 16:33 ` Jens Axboe
2007-07-13 16:33 ` Jens Axboe
2007-07-13 16:50 ` Jens Axboe
2007-07-13 16:50 ` Jens Axboe
2007-07-13 19:18 ` walt [this message]
2007-07-13 20:24 ` Patrick McHardy
2007-07-13 20:24 ` Patrick McHardy
2007-07-13 20:43 ` Jens Axboe
2007-07-13 20:43 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='f78j5t$ttc$1@sea.gmane.org' \
--to=wa1ter@myrealbox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.