All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7aef76bdb53b83d62a9e@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dmantipov@yandex.ru,
	jlbec@evilplan.org,  joseph.qi@linux.alibaba.com,
	kartikey406@gmail.com,  linux-kernel@vger.kernel.org,
	lvc-project@linuxtesting.org, mark@fasheh.com,
	 ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_set_new_buffer_uptodate (2)
Date: Wed, 14 Jan 2026 19:46:02 -0800	[thread overview]
Message-ID: <696862fa.050a0220.58bed.000b.GAE@google.com> (raw)
In-Reply-To: <676c3718.050a0220.2f3838.037f.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 93ce0ff117b0c468961d7c296a03ad57e1e8da9f
Author: Deepanshu Kartikey <kartikey406@gmail.com>
Date:   Thu Oct 30 15:30:03 2025 +0000

    ocfs2: validate cl_bpc in allocator inodes to prevent divide-by-zero

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=143ebd9a580000
start commit:   499551201b5f Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=6a2b862bf4a5409f
dashboard link: https://syzkaller.appspot.com/bug?extid=7aef76bdb53b83d62a9e
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=136ab2df980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=124f6f30580000

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

#syz fix: ocfs2: validate cl_bpc in allocator inodes to prevent divide-by-zero

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

  parent reply	other threads:[~2026-01-15  3:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25 16:47 [syzbot] [ocfs2?] kernel BUG in ocfs2_set_new_buffer_uptodate (2) syzbot
2024-12-26 15:53 ` [syzbot] Re: kernel BUG in ocfs2_set_new_buffer_uptodate() syzbot
2024-12-27 10:54 ` syzbot
2025-10-22 14:00 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 552c50713f273b494ac6c77052032a49bc9255e2 syzbot
2025-10-24  7:11 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-5.10.y syzbot
2025-10-24  7:15 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-6.1.y syzbot
2025-10-24  7:15 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-6.12.y syzbot
2025-10-28 10:40 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux-5.10.y syzbot
2025-10-28 10:41 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux-6.1.y syzbot
2025-10-28 10:42 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux-6.12.y syzbot
2025-10-28 18:19 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-5.10.y syzbot
2025-10-28 18:21 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-6.1.y syzbot
2025-10-28 18:22 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-6.12.y syzbot
2025-10-29  6:21 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-5.10.y syzbot
2025-10-29  6:25 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-6.1.y syzbot
2025-10-29  6:27 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-6.12.y syzbot
2026-01-15  3:46 ` syzbot [this message]
     [not found] <20241226155305.Yro_e%dmantipov@yandex.ru>
2024-12-26 16:26 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_set_new_buffer_uptodate (2) syzbot
     [not found] <20241227105402.odBU4%dmantipov@yandex.ru>
2024-12-27 11:38 ` syzbot
     [not found] <20251022140016.A5JqV%dmantipov@yandex.ru>
2025-10-22 14:36 ` syzbot
     [not found] <20251024071154.COzwR%dmantipov@yandex.ru>
2025-10-24  9:32 ` syzbot
     [not found] <20251024071521.fbtQk%dmantipov@yandex.ru>
2025-10-24 12:42 ` syzbot
     [not found] <20251024071532.gsUD9%dmantipov@yandex.ru>
2025-10-24 14:04 ` syzbot
     [not found] <20251028104006.trzAA%dmantipov@yandex.ru>
2025-10-28 10:44 ` syzbot
     [not found] <20251028104120.GnIG9%dmantipov@yandex.ru>
2025-10-28 10:46 ` syzbot
     [not found] <20251028104159.Yh5Ro%dmantipov@yandex.ru>
2025-10-28 10:50 ` syzbot
     [not found] <20251028181937.VGTo3%dmantipov@yandex.ru>
2025-10-28 19:31 ` syzbot
     [not found] <20251028182104.36i6Z%dmantipov@yandex.ru>
2025-10-28 20:48 ` syzbot
     [not found] <20251028182255.i5pLj%dmantipov@yandex.ru>
2025-10-28 21:54 ` syzbot
     [not found] <20251029062153.ZEpQh%dmantipov@yandex.ru>
2025-10-29  8:56 ` syzbot
     [not found] <20251029062548.p-W3Z%dmantipov@yandex.ru>
2025-10-29 13:06 ` syzbot
     [not found] <20251029062741.5wX4O%dmantipov@yandex.ru>
2025-10-29 16:15 ` 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=696862fa.050a0220.58bed.000b.GAE@google.com \
    --to=syzbot+7aef76bdb53b83d62a9e@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmantipov@yandex.ru \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=kartikey406@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --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.