From: Bian Naimeng <biannm@cn.fujitsu.com>
To: yo mama <mamamia69@gmail.com>
Cc: linux-nfs@vger.kernel.org, Benny Halevy <bhalevy@panasas.com>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000020
Date: Thu, 29 Jul 2010 12:39:20 +0800 [thread overview]
Message-ID: <4C5105F8.5050101@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTikYDGpeX8kcK3ygFzjM+bYMFTtqr8Wgx+CygUt8@mail.gmail.com>
> Hello,
>
> I am running Kernel version 2.6.35-rc5-pnfs and notice there is kernel
> crash everytime i run iozone on the mounted directory. Is there a
> patch already developed for this bug which i can apply. Please see the
> error message from message log.
>
I'm not sure it's ok, please try it.
----
nfs_writeargs.lock_context always NULL at direct write procedure,
it will cause kernel panic when encode stateid.
Signed-off-by: Bian Naimeng <biannm@cn.fujitsu.com>
---
fs/nfs/direct.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/fs/nfs/direct.c b/fs/nfs/direct.c
index 3ef9b0c..cb2e1fd 100644
--- a/fs/nfs/direct.c
+++ b/fs/nfs/direct.c
@@ -801,6 +801,7 @@ static ssize_t nfs_direct_write_schedule_segment(struct nfs_direct_req *dreq,
data->cred = msg.rpc_cred;
data->args.fh = NFS_FH(inode);
data->args.context = ctx;
+ data->args.lock_context = nfs_get_lock_context(ctx);
data->args.offset = pos;
data->args.pgbase = pgbase;
data->args.pages = data->pagevec;
--
1.6.5.2
--
Regards
Bian Naimeng
next prev parent reply other threads:[~2010-07-29 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 18:14 BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 yo mama
2010-07-29 4:39 ` Bian Naimeng [this message]
2010-07-30 18:28 ` Trond Myklebust
[not found] ` <1280514531.12852.23.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-07-31 4:56 ` yo mama
[not found] ` <AANLkTi=nA8FCQrOB09uqCfFyduSATgzg-Q2GyZk-D+GP-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-01 18:18 ` Benny Halevy
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=4C5105F8.5050101@cn.fujitsu.com \
--to=biannm@cn.fujitsu.com \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mamamia69@gmail.com \
/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