public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill O'Donnell <billodo@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/4] xfs: xfs_rtbuf_get should check the bmapi_read results
Date: Thu, 31 May 2018 12:15:35 -0500	[thread overview]
Message-ID: <20180531171535.GB25547@redhat.com> (raw)
In-Reply-To: <152778443693.6891.16527148773204429254.stgit@magnolia>

On Thu, May 31, 2018 at 09:33:57AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
> 
> The xfs_rtbuf_get function should check the block mapping it gets back
> from bmapi_read.  If there are no mappings or the mapping isn't a real
> extent, we should return -EFSCORRUPTED rather than trying to read a
> garbage value.  We also require realtime bitmap blocks to be real,
> written allocations.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
looks fine...
Reviewed-by: Bill O'Donnell <billodo@redhat.com>

> ---
>  fs/xfs/libxfs/xfs_rtbitmap.c |    3 +++
>  1 file changed, 3 insertions(+)
> 
> 
> diff --git a/fs/xfs/libxfs/xfs_rtbitmap.c b/fs/xfs/libxfs/xfs_rtbitmap.c
> index 106be2d0bb88..7712f282d172 100644
> --- a/fs/xfs/libxfs/xfs_rtbitmap.c
> +++ b/fs/xfs/libxfs/xfs_rtbitmap.c
> @@ -90,6 +90,9 @@ xfs_rtbuf_get(
>  	if (error)
>  		return error;
>  
> +	if (nmap == 0 || !xfs_bmap_is_real_extent(&map))
> +		return -EFSCORRUPTED;
> +
>  	ASSERT(map.br_startblock != NULLFSBLOCK);
>  	error = xfs_trans_read_buf(mp, tp, mp->m_ddev_targp,
>  				   XFS_FSB_TO_DADDR(mp, map.br_startblock),
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2018-05-31 17:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 16:33 [PATCH 0/4] xfs-4.18: fix rtdev programming errors Darrick J. Wong
2018-05-31 16:33 ` [PATCH 1/4] xfs: xfs_rtword_t should be unsigned, not signed Darrick J. Wong
2018-05-31 17:09   ` Allison Henderson
2018-05-31 17:14   ` Bill O'Donnell
2018-05-31 16:33 ` [PATCH 2/4] xfs: xfs_rtbuf_get should check the bmapi_read results Darrick J. Wong
2018-05-31 17:09   ` Allison Henderson
2018-05-31 17:15   ` Bill O'Donnell [this message]
2018-05-31 16:34 ` [PATCH 3/4] xfs: strengthen rtalloc query range checks Darrick J. Wong
2018-05-31 17:09   ` Allison Henderson
2018-05-31 17:16   ` Bill O'Donnell
2018-05-31 16:34 ` [PATCH 4/4] xfs: fix xfs_rtalloc_rec units Darrick J. Wong
2018-05-31 17:09   ` Allison Henderson
2018-05-31 17:21   ` Bill O'Donnell

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=20180531171535.GB25547@redhat.com \
    --to=billodo@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@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