All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9e39ac154d8781441e60@syzkaller.appspotmail.com>
To: boris@bur.io, clm@fb.com, dsterba@suse.com, dsterba@suse.cz,
	 hdanton@sina.com, josef@toxicpanda.com,
	linux-btrfs@vger.kernel.org,  linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com,
	wqu@suse.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in folio_unlock (2)
Date: Fri, 06 Sep 2024 18:25:02 -0700	[thread overview]
Message-ID: <0000000000009e4fa906217d6447@google.com> (raw)
In-Reply-To: <0000000000009e614206177b0968@google.com>

syzbot suspects this issue was fixed by commit:

commit 478574370bef7951fbd9ef5155537d6cbed49472
Author: Boris Burkov <boris@bur.io>
Date:   Mon Jul 22 23:49:45 2024 +0000

    btrfs: make cow_file_range_inline() honor locked_page on error

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13bf909f980000
start commit:   256abd8e550c Linux 6.10-rc7
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=42a432cfd0e579e0
dashboard link: https://syzkaller.appspot.com/bug?extid=9e39ac154d8781441e60
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12984185980000

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

#syz fix: btrfs: make cow_file_range_inline() honor locked_page on error

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

      parent reply	other threads:[~2024-09-07  1:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 16:24 [syzbot] [btrfs?] kernel BUG in folio_unlock (2) syzbot
2024-05-02 23:22 ` Hillf Danton
2024-05-03  0:01   ` syzbot
2024-05-15 16:45 ` David Sterba
2024-09-07  1:25 ` 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=0000000000009e4fa906217d6447@google.com \
    --to=syzbot+9e39ac154d8781441e60@syzkaller.appspotmail.com \
    --cc=boris@bur.io \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=hdanton@sina.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=wqu@suse.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.