All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"schumaker.anna@gmail.com" <schumaker.anna@gmail.com>
Cc: "Anna.Schumaker@Netapp.com" <Anna.Schumaker@Netapp.com>
Subject: Re: [PATCH] NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return()
Date: Wed, 19 May 2021 16:42:58 +0000	[thread overview]
Message-ID: <9b54027028a9a7322b6f06748c4499174a238866.camel@hammerspace.com> (raw)
In-Reply-To: <20210519160635.333057-1-Anna.Schumaker@Netapp.com>

On Wed, 2021-05-19 at 12:06 -0400, schumaker.anna@gmail.com wrote:
> From: Anna Schumaker <Anna.Schumaker@Netapp.com>
> 
> Commit de144ff4234f changes _pnfs_return_layout() to call
> pnfs_mark_matching_lsegs_return() passing NULL as the struct
> pnfs_layout_range argument. Unfortunately,
> pnfs_mark_matching_lsegs_return() doesn't check if we have a value
> here
> before dereferencing it, causing an oops.
> 
> I'm able to hit this crash consistently when running connectathon
> basic
> tests on NFS v4.1/v4.2 against Ontap.
> 
> Fixes: de144ff4234f ("NFSv4: Don't discard segments marked for return
> in _pnfs_return_layout()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
> ---
>  fs/nfs/pnfs.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/nfs/pnfs.c b/fs/nfs/pnfs.c
> index 03e0b34c4a64..6d720afb7b70 100644
> --- a/fs/nfs/pnfs.c
> +++ b/fs/nfs/pnfs.c
> @@ -2484,12 +2484,12 @@ pnfs_mark_matching_lsegs_return(struct
> pnfs_layout_hdr *lo,
>                         set_bit(NFS_LSEG_LAYOUTRETURN, &lseg-
> >pls_flags);
>                 }
>  
> -       if (remaining) {
> +       if (remaining && return_range) {
>                 pnfs_set_plh_return_info(lo, return_range->iomode,
> seq);
>                 return -EBUSY;
>         }
>  
> -       if (!list_empty(&lo->plh_return_segs)) {
> +       if (return_range && !list_empty(&lo->plh_return_segs)) {
>                 pnfs_set_plh_return_info(lo, return_range->iomode,
> seq);
>                 return 0;

This patch would mean we fail to mark the layout for return in
situations where we clearly should be doing so. The lack of a
return_range doesn't indicate that we don't want to return any layouts,
but rather that we want to return all layouts.

I suggest rather changing the caller, _pnfs_return_layout() to move
that declaration of 'struct pnfs_layout_range range' out of the if
statement so that it can be passed as an argument instead of NULL.

>         }

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2021-05-19 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 16:06 [PATCH] NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return() schumaker.anna
2021-05-19 16:42 ` Trond Myklebust [this message]
2021-05-19 16:47   ` Anna Schumaker

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=9b54027028a9a7322b6f06748c4499174a238866.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=Anna.Schumaker@Netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=schumaker.anna@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 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.