mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hongbo Li <lihongbo22@huawei.com>
To: Mohammed Anees <pvmohammedanees2003@gmail.com>,
	Kent Overstreet <kent.overstreet@linux.dev>
Cc: <syzbot+37186860aa7812b331d5@syzkaller.appspotmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-bcachefs@vger.kernel.org" <linux-bcachefs@vger.kernel.org>
Subject: Re: [PATCH resend v3] bcachefs: Fix NULL pointer dereference in bch2_opt_to_text
Date: Tue, 8 Oct 2024 10:23:08 +0800	[thread overview]
Message-ID: <f8fcc1e6-6de6-4d60-83a7-83e95a7d6b6e@huawei.com> (raw)
In-Reply-To: <20241005130229.9290-1-pvmohammedanees2003@gmail.com>



On 2024/10/5 21:02, Mohammed Anees wrote:
> This patch adds a bounds check to the bch2_opt_to_text function to prevent
> NULL pointer dereferences when accessing the opt->choices array. This
> ensures that the index used is within valid bounds before dereferencing.
> The new version enhances the readability.
> 
> Reported-and-tested-by: syzbot+37186860aa7812b331d5@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=37186860aa7812b331d5
> Signed-off-by: Mohammed Anees <pvmohammedanees2003@gmail.com>
> ---
> v3:
> - Moved bounds check above as default case.
> - Removed the nesterd if clauses.
> ---
>   fs/bcachefs/opts.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/bcachefs/opts.c b/fs/bcachefs/opts.c
> index 232be8a44051..84097235eea9 100644
> --- a/fs/bcachefs/opts.c
> +++ b/fs/bcachefs/opts.c
> @@ -427,7 +427,9 @@ void bch2_opt_to_text(struct printbuf *out,
>   			prt_printf(out, "%lli", v);
>   		break;
>   	case BCH_OPT_STR:
> -		if (flags & OPT_SHOW_FULL_LIST)
> +		if (v < opt->min || v >= opt->max - 1)
As definition, max is the right bound for value. opt->max - 1 is valid. 
May be you should remove the equals sign.

It should be no problem to just solve this null pointer issue() (How is 
this stack triggered, may be I lost something.), but this should be a 
general boundary check condition, strictly speaking, it's a check for 
the validity of the options' value.

Thanks,
Hongbo

> +			prt_printf(out, "(invalid option %lli)", v);
> +		else if (flags & OPT_SHOW_FULL_LIST)
>   			prt_string_option(out, opt->choices, v);
>   		else
>   			prt_str(out, opt->choices[v]);

  reply	other threads:[~2024-10-08  2:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-05 13:02 Mohammed Anees
2024-10-08  2:23 ` Hongbo Li [this message]
2024-10-08 13:51   ` Mohammed Anees
2024-10-09  1:28     ` Hongbo Li
2024-10-08 17:17 ` Kent Overstreet

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=f8fcc1e6-6de6-4d60-83a7-83e95a7d6b6e@huawei.com \
    --to=lihongbo22@huawei.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pvmohammedanees2003@gmail.com \
    --cc=syzbot+37186860aa7812b331d5@syzkaller.appspotmail.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®