All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+15669ec8c35ddf6c3d43@syzkaller.appspotmail.com>
To: chao@kernel.org, hanqi@vivo.com, jaegeuk@kernel.org,
	 linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] kernel BUG in new_curseg (2)
Date: Tue, 11 Feb 2025 05:14:03 -0800	[thread overview]
Message-ID: <67ab4d1b.050a0220.3d72c.0062.GAE@google.com> (raw)
In-Reply-To: <675cd64e.050a0220.37aaf.00bb.GAE@google.com>

syzbot has bisected this issue to:

commit 84b5bb8bf0f6a78c232a20c2eecdbb8112ac2703
Author: Qi Han <hanqi@vivo.com>
Date:   Fri Oct 25 09:18:23 2024 +0000

    f2fs: modify f2fs_is_checkpoint_ready logic to allow more data to be written with the CP disable

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11d1f1b0580000
start commit:   a64dcfb451e2 Linux 6.14-rc2
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=13d1f1b0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=15d1f1b0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4b1ef007dfb9422f
dashboard link: https://syzkaller.appspot.com/bug?extid=15669ec8c35ddf6c3d43
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=166931b0580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12be72a4580000

Reported-by: syzbot+15669ec8c35ddf6c3d43@syzkaller.appspotmail.com
Fixes: 84b5bb8bf0f6 ("f2fs: modify f2fs_is_checkpoint_ready logic to allow more data to be written with the CP disable")

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


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+15669ec8c35ddf6c3d43@syzkaller.appspotmail.com>
To: chao@kernel.org, hanqi@vivo.com, jaegeuk@kernel.org,
	 linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] kernel BUG in new_curseg (2)
Date: Tue, 11 Feb 2025 05:14:03 -0800	[thread overview]
Message-ID: <67ab4d1b.050a0220.3d72c.0062.GAE@google.com> (raw)
In-Reply-To: <675cd64e.050a0220.37aaf.00bb.GAE@google.com>

syzbot has bisected this issue to:

commit 84b5bb8bf0f6a78c232a20c2eecdbb8112ac2703
Author: Qi Han <hanqi@vivo.com>
Date:   Fri Oct 25 09:18:23 2024 +0000

    f2fs: modify f2fs_is_checkpoint_ready logic to allow more data to be written with the CP disable

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11d1f1b0580000
start commit:   a64dcfb451e2 Linux 6.14-rc2
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=13d1f1b0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=15d1f1b0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4b1ef007dfb9422f
dashboard link: https://syzkaller.appspot.com/bug?extid=15669ec8c35ddf6c3d43
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=166931b0580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12be72a4580000

Reported-by: syzbot+15669ec8c35ddf6c3d43@syzkaller.appspotmail.com
Fixes: 84b5bb8bf0f6 ("f2fs: modify f2fs_is_checkpoint_ready logic to allow more data to be written with the CP disable")

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

  parent reply	other threads:[~2025-02-11 13:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-14  0:50 [f2fs-dev] [syzbot] [f2fs?] kernel BUG in new_curseg (2) syzbot
2024-12-14  0:50 ` syzbot
2025-02-10 21:42 ` [f2fs-dev] " syzbot
2025-02-10 21:42   ` syzbot
2025-02-11  5:15   ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-02-11  5:15     ` Chao Yu
2025-02-11  5:32     ` [f2fs-dev] " syzbot
2025-02-11  5:32       ` syzbot
2025-02-11  6:09   ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-02-11  6:09     ` Chao Yu
2025-02-11  6:35     ` [f2fs-dev] " syzbot
2025-02-11  6:35       ` syzbot
2025-02-11 13:14 ` syzbot [this message]
2025-02-11 13:14   ` syzbot

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=67ab4d1b.050a0220.3d72c.0062.GAE@google.com \
    --to=syzbot+15669ec8c35ddf6c3d43@syzkaller.appspotmail.com \
    --cc=chao@kernel.org \
    --cc=hanqi@vivo.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --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.