public inbox for [email protected]
 help / color / mirror / Atom feed
From: Dan Carpenter <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Jaegeuk Kim <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	[email protected], [email protected],
	[email protected]
Subject: Re: Fwd: [ammarfaizi2-block:google/android/kernel/common/upstream-f2fs-stable-linux-5.15.y 115/361] fs/f2fs/data.c:996 f2fs_grab_read_bio() warn: variable dereferenced before check 'bio' (see line 995)
Date: Mon, 23 Jan 2023 15:37:22 +0300	[thread overview]
Message-ID: <Y85/gtltbiWCv+jB@kadam> (raw)
In-Reply-To: <[email protected]>

On Mon, Jan 23, 2023 at 07:24:17PM +0700, Ammar Faizi wrote:
> commit e8e3f1a12d05d0aef2c819664890b540dfb055af
> Author:     Christoph Hellwig <[email protected]>
> AuthorDate: Mon Feb 28 14:41:22 2022 +0200
> Commit:     Jaegeuk Kim <[email protected]>
> CommitDate: Thu Apr 28 15:51:57 2022 -0700
> 
>     f2fs: don't pass a bio to f2fs_target_device
>     Set the bdev at bio allocation time by changing the f2fs_target_device
>     calling conventions, so that no bio needs to be passed in.
>     Signed-off-by: Christoph Hellwig <[email protected]>
>     Reviewed-by: Chao Yu <[email protected]>
>     Link: https://lore.kernel.org/r/[email protected]
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This link doesn't have the bug.  It seems like it was caused by a merge
issue.

Simple enough to fix either way.

regards,
dan carpenter


      reply	other threads:[~2023-01-23 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 12:03 [ammarfaizi2-block:google/android/kernel/common/upstream-f2fs-stable-linux-5.15.y 115/361] fs/f2fs/data.c:996 f2fs_grab_read_bio() warn: variable dereferenced before check 'bio' (see line 995) Dan Carpenter
2023-01-23 12:22 ` Ammar Faizi
2023-01-23 12:24 ` Fwd: " Ammar Faizi
2023-01-23 12:37   ` Dan Carpenter [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=Y85/gtltbiWCv+jB@kadam \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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