From: Jens Axboe <jens.axboe@oracle.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Chuck Ebbert <cebbert@redhat.com>,
neilb@suse.de, nfs@lists.sourceforge.net,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: nfsd oops in current -git
Date: Fri, 13 Jul 2007 22:43:54 +0200 [thread overview]
Message-ID: <20070713204353.GB5328@kernel.dk> (raw)
In-Reply-To: <4697DF7F.3030400@trash.net>
On Fri, Jul 13 2007, Patrick McHardy wrote:
> Jens Axboe wrote:
> >>>On 07/13/2007 09:40 AM, Patrick McHardy wrote:
> >>>
> >>>>I get this oops with current -git:
> >>>>
> >>>>[ 3437.018923] Pid: 4432, comm: nfsd Not tainted 2.6.22 #5
> >>>>[ 3437.018926] RIP: 0010:[<ffffffff81054eff>] [<ffffffff81054eff>]
> >>>>put_page+0x4/0xb3
>
> > Patrick, does this work?
>
>
> Seems to work fine, thanks Jens.
Wonderful, thanks for testing!
--
Jens Axboe
prev parent reply other threads:[~2007-07-13 20:44 UTC|newest]
Thread overview: 6+ 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:33 ` Jens Axboe
2007-07-13 16:50 ` Jens Axboe
2007-07-13 20:24 ` Patrick McHardy
2007-07-13 20:43 ` Jens Axboe [this message]
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=20070713204353.GB5328@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=cebbert@redhat.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox