From: Andrew Price <anprice@redhat.com>
To: Fox Chen <foxhlchen@gmail.com>
Cc: rpeterso@redhat.com, agruenba@redhat.com,
cluster-devel@redhat.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [Cluster-devel] [PATCH] gfs2: gfs2_read_sb: put gfs2_assert inside the loop
Date: Mon, 5 Oct 2020 14:23:03 +0100 [thread overview]
Message-ID: <ca694fc8-5f1b-ebf0-b891-c9a20225704f@redhat.com> (raw)
In-Reply-To: <20201003063143.13093-1-foxhlchen@gmail.com>
On 03/10/2020 07:31, Fox Chen wrote:
> for (x = 2;; x++) {
> ...
> gfs2_assert(sdp, x <= GFS2_MAX_META_HEIGHT); <--- after
> ...
> if (d != sdp->sd_heightsize[x - 1] || m)
> break;
> sdp->sd_heightsize[x] = space;
> }
>
> sdp->sd_max_height = x
> gfs2_assert(sdp, sdp->sd_max_height <= GFS2_MAX_META_HEIGHT) <--- before
>
> Before this patch, gfs2_assert is put outside of the loop of
> sdp->sd_heightsize[x] calculation. When something goes wrong,
So this looks related to one of the recent syzbot reports, where the
"something goes wrong" is the block size in the on-disk superblock was
zeroed and that leads eventually to this out-of-bounds write. The
correct fix in that case would be to add a validity check for the block
size in gfs2_check_sb().
Andy
> x exceeds the size of GFS2_MAX_META_HEIGHT, it may already crash inside
> the loop when
>
> sdp->sd_heightsize[x] = space
>
> tries to reach the out-of-bound
> location, gfs2_assert won't help here.
>
> This patch fixes this by moving gfs2_assert into the loop.
> We will check x value each time to see if it exceeds GFS2_MAX_META_HEIGHT.
>
> Signed-off-by: Fox Chen <foxhlchen@gmail.com>
> ---
> fs/gfs2/ops_fstype.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
> index 6d18d2c91add..6cc32e3010f2 100644
> --- a/fs/gfs2/ops_fstype.c
> +++ b/fs/gfs2/ops_fstype.c
> @@ -333,6 +333,7 @@ static int gfs2_read_sb(struct gfs2_sbd *sdp, int silent)
> u64 space, d;
> u32 m;
>
> + gfs2_assert(sdp, x <= GFS2_MAX_META_HEIGHT);
> space = sdp->sd_heightsize[x - 1] * sdp->sd_inptrs;
> d = space;
> m = do_div(d, sdp->sd_inptrs);
> @@ -343,7 +344,6 @@ static int gfs2_read_sb(struct gfs2_sbd *sdp, int silent)
> }
> sdp->sd_max_height = x;
> sdp->sd_heightsize[x] = ~0;
> - gfs2_assert(sdp, sdp->sd_max_height <= GFS2_MAX_META_HEIGHT);
>
> sdp->sd_max_dents_per_leaf = (sdp->sd_sb.sb_bsize -
> sizeof(struct gfs2_leaf)) /
>
next prev parent reply other threads:[~2020-10-05 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 6:31 Fox Chen
2020-10-05 12:59 ` Andreas Gruenbacher
2020-10-05 13:23 ` Andrew Price [this message]
2020-10-05 14:08 ` [Cluster-devel] " Fox Chen
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=ca694fc8-5f1b-ebf0-b891-c9a20225704f@redhat.com \
--to=anprice@redhat.com \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=foxhlchen@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@redhat.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
all inboxes | Powered by JetHome®