All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+858534c396b0cdd291d2@syzkaller.appspotmail.com>
To: Johannes.Thumshirn@wdc.com, clm@fb.com, dsterba@suse.com,
	dsterba@suse.cz, josef@toxicpanda.com,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	osandov@fb.com, sweettea-kernel@dorminy.me,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in cow_file_range_inline
Date: Fri, 20 Jan 2023 16:36:24 -0800	[thread overview]
Message-ID: <0000000000001bde1e05f2bb5be8@google.com> (raw)
In-Reply-To: <00000000000080bb5c05ebe34a4d@google.com>

syzbot suspects this issue was fixed by commit:

commit 8bb808c6ad91ec3d332f072ce8f8aa4b16e307e0
Author: David Sterba <dsterba@suse.com>
Date:   Thu Nov 3 13:39:01 2022 +0000

    btrfs: don't print stack trace when transaction is aborted due to ENOMEM

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15521666480000
start commit:   337a0a0b63f1 Merge tag 'net-6.1-rc3-1' of git://git.kernel..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=1d3548a4365ba17d
dashboard link: https://syzkaller.appspot.com/bug?extid=858534c396b0cdd291d2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16e5a422880000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16387a16880000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: btrfs: don't print stack trace when transaction is aborted due to ENOMEM

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2023-01-21  0:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 22:18 [syzbot] WARNING in cow_file_range_inline syzbot
2022-10-26  7:30 ` Johannes Thumshirn
2022-10-26  8:14   ` David Sterba
2023-01-21  0:36 ` syzbot [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=0000000000001bde1e05f2bb5be8@google.com \
    --to=syzbot+858534c396b0cdd291d2@syzkaller.appspotmail.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osandov@fb.com \
    --cc=sweettea-kernel@dorminy.me \
    --cc=syzkaller-bugs@googlegroups.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.