From: Fengguang Wu <fengguang.wu@intel.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [SUNPRC] BUG: unable to handle kernel NULL pointer dereference at 0000000000000070
Date: Fri, 11 Jan 2013 13:22:50 +0800 [thread overview]
Message-ID: <20130111052250.GA13133@localhost> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA9119984C5@SACEXCMBX04-PRD.hq.netapp.com>
On Fri, Jan 11, 2013 at 04:24:45AM +0000, Trond Myklebust wrote:
> On Fri, 2013-01-11 at 10:46 +0800, Fengguang Wu wrote:
> > tree: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
> > commit: 51b63a538c54cb9c3b83c4d62572cf18da165cba [1/1] SUNRPC: Ensure we release the socket write lock if the rpc_task exits early
> >
> > [ 106.308511] md: autorun ...
> > [ 106.309477] md: ... autorun DONE.
> > [ 107.923634] BUG: unable to handle kernel NULL pointer dereference at 0000000000000070
> > [ 107.926207] IP: [<ffffffff82a7c8ac>] xprt_release+0x24/0x1cb
> Hi Fengguang,
>
> Thanks for testing! The above Oops should be fixed in commit
> 87ed50036b866db2ec2ba16b2a7aec4a2b0b7c39, which is in the current
> linux-next branch on git.linux-nfs.org. It was due to a missing test for
> task->tk_client != NULL.
Yes, sorry that bug was actually caught several days before, however
I was too busy to look into it..
> I should also have fixed the RCU dereference warning that the build
> robot found on Tuesday.
Trond, thank you for the fixes!
Thanks,
Fengguang
prev parent reply other threads:[~2013-01-11 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130111024644.GA9508@localhost>
2013-01-11 4:24 ` [SUNPRC] BUG: unable to handle kernel NULL pointer dereference at 0000000000000070 Myklebust, Trond
2013-01-11 5:22 ` Fengguang Wu [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=20130111052250.GA13133@localhost \
--to=fengguang.wu@intel.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/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