From: Jeff Layton <jlayton@redhat.com>
To: trond.myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org, andros@netapp.com
Subject: Re: [PATCH] nfs: fix NULL pointer dereference in nfs4_fl_prepare_ds
Date: Thu, 26 Sep 2013 10:19:41 -0400 [thread overview]
Message-ID: <20130926101941.3487b3a6@corrin.poochiereds.net> (raw)
In-Reply-To: <1380140457-27408-1-git-send-email-jlayton@redhat.com>
On Wed, 25 Sep 2013 16:20:57 -0400
Jeff Layton <jlayton@redhat.com> wrote:
> In the event that there is an error connecting to a DS, we currently
> zero out the ds pointer and then try to dereference it to clear the
> NFS4DS_CONNECTING bit.
>
> Fix this by clearing the bit unconditionally before zeroing out the
> pointer.
>
> Cc: Andy Adamson <andros@netapp.com>
> Cc: <stable@vger.kernel.org> # v3.10+
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
> fs/nfs/nfs4filelayoutdev.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/nfs/nfs4filelayoutdev.c b/fs/nfs/nfs4filelayoutdev.c
> index 95604f6..816cda8 100644
> --- a/fs/nfs/nfs4filelayoutdev.c
> +++ b/fs/nfs/nfs4filelayoutdev.c
> @@ -819,11 +819,11 @@ nfs4_fl_prepare_ds(struct pnfs_layout_segment *lseg, u32 ds_idx)
> int err;
>
> err = nfs4_ds_connect(s, ds);
> + nfs4_clear_ds_conn_bit(ds);
> if (err) {
> nfs4_mark_deviceid_unavailable(devid);
> ds = NULL;
> }
> - nfs4_clear_ds_conn_bit(ds);
> } else {
> /* Either ds is connected, or ds is NULL */
> nfs4_wait_ds_connect(ds);
Trond,
Please disregard this patch. There's another problem in here that we'll
need to fix too. Andy will be sending along a replacement patch later
that should fix this bug and the other problems too.
--
Jeff Layton <jlayton@redhat.com>
prev parent reply other threads:[~2013-09-26 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 20:20 [PATCH] nfs: fix NULL pointer dereference in nfs4_fl_prepare_ds Jeff Layton
2013-09-26 14:19 ` Jeff Layton [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=20130926101941.3487b3a6@corrin.poochiereds.net \
--to=jlayton@redhat.com \
--cc=andros@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.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;
as well as URLs for NNTP newsgroup(s).