All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Christoph Hellwig <hch@lst.de>, oe-lkp@lists.linux.dev, lkp@intel.com
Subject: Re: [hch-misc:btrfs-bio-split] [btrfs]  b7c9bcdc17: BUG:KASAN:use-after-free_in__blk_bios_map_sg
Date: Thu, 19 Jan 2023 16:10:44 +0100	[thread overview]
Message-ID: <20230119151044.GA28290@lst.de> (raw)
In-Reply-To: <Y8adDdqXX6ptkU7X@xsang-OptiPlex-9020>

Hi Oliver,

I've still not been able to reproduce the issue locally, but identified
a potential issue.  Any chance you could force a re-run of this test
group in the current hch-misc:btrfs-bio-split branch?

On Tue, Jan 17, 2023 at 09:05:17PM +0800, Oliver Sang wrote:
> hi, Christoph Hellwig,
> 
> On Tue, Jan 17, 2023 at 09:20:42AM +0100, Christoph Hellwig wrote:
> > On Tue, Jan 17, 2023 at 03:57:20PM +0800, kernel test robot wrote:
> > > 
> > > Greeting,
> > > 
> > > FYI, we noticed BUG:KASAN:use-after-free_in__blk_bios_map_sg due to commit (built with gcc-11):
> > > 
> > > commit: b7c9bcdc17f3d9a546470cca6dbf717254ca5291 ("btrfs: remove stripe boundary calculation for buffered I/O")
> > 
> > This seems like a really odd commit to hit such a bug.  How reliably
> > was the bisection?
> > 
> 
> the issue doesn't always happen, but with a relatively high rate.
> and the parent doesn't show this issue.
> 
> b45951da8e8f13e6 b7c9bcdc17f3d9a546470cca6db
> ---------------- ---------------------------
>        fail:runs  %reproduction    fail:runs
>            |             |             |
>            :20          80%          16:20    dmesg.BUG:KASAN:use-after-free_in__blk_bios_map_sg
> 
> BTW,
> we noticed the commit date is just recent, not sure if a porting commit?
> so just sent out the report FYI
> 
> commit b7c9bcdc17f3d9a546470cca6dbf717254ca5291
> Author:     Qu Wenruo <wqu@suse.com>
> AuthorDate: Tue Nov 30 17:21:58 2021 +0800
> Commit:     Christoph Hellwig <hch@lst.de>
> CommitDate: Thu Jan 12 15:01:55 2023 +0100
> 
>     btrfs: remove stripe boundary calculation for buffered I/O
---end quoted text---

  parent reply	other threads:[~2023-01-19 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17  7:57 [hch-misc:btrfs-bio-split] [btrfs] b7c9bcdc17: BUG:KASAN:use-after-free_in__blk_bios_map_sg kernel test robot
2023-01-17  8:20 ` Christoph Hellwig
2023-01-17 13:05   ` Oliver Sang
2023-01-17 13:31     ` Christoph Hellwig
2023-01-19 15:10     ` Christoph Hellwig [this message]
2023-01-24 12:50       ` Oliver Sang
2023-01-24 13:10         ` Christoph Hellwig

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=20230119151044.GA28290@lst.de \
    --to=hch@lst.de \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.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.