public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7aef76bdb53b83d62a9e@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_set_new_buffer_uptodate (2)
Date: Tue, 28 Oct 2025 14:54:02 -0700	[thread overview]
Message-ID: <69013b7a.050a0220.32483.01dd.GAE@google.com> (raw)
In-Reply-To: <20251028182255.i5pLj%dmantipov@yandex.ru>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+7aef76bdb53b83d62a9e@syzkaller.appspotmail.com
Tested-by: syzbot+7aef76bdb53b83d62a9e@syzkaller.appspotmail.com

Tested on:

commit:         4fc43deb Linux 6.12.55
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-6.12.y
console output: https://syzkaller.appspot.com/x/log.txt?x=177e6fe2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=52b41b67187b07bc
dashboard link: https://syzkaller.appspot.com/bug?extid=7aef76bdb53b83d62a9e
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=16ac432f980000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2025-10-28 21:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251028182255.i5pLj%dmantipov@yandex.ru>
2025-10-28 21:54 ` syzbot [this message]
     [not found] <20251029062741.5wX4O%dmantipov@yandex.ru>
2025-10-29 16:15 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_set_new_buffer_uptodate (2) syzbot
     [not found] <20251029062548.p-W3Z%dmantipov@yandex.ru>
2025-10-29 13:06 ` syzbot
     [not found] <20251029062153.ZEpQh%dmantipov@yandex.ru>
2025-10-29  8:56 ` syzbot
     [not found] <20251028182104.36i6Z%dmantipov@yandex.ru>
2025-10-28 20:48 ` syzbot
     [not found] <20251028181937.VGTo3%dmantipov@yandex.ru>
2025-10-28 19:31 ` syzbot
     [not found] <20251028104159.Yh5Ro%dmantipov@yandex.ru>
2025-10-28 10:50 ` syzbot
     [not found] <20251028104120.GnIG9%dmantipov@yandex.ru>
2025-10-28 10:46 ` syzbot
     [not found] <20251028104006.trzAA%dmantipov@yandex.ru>
2025-10-28 10:44 ` syzbot
     [not found] <20251024071532.gsUD9%dmantipov@yandex.ru>
2025-10-24 14:04 ` syzbot
     [not found] <20251024071521.fbtQk%dmantipov@yandex.ru>
2025-10-24 12:42 ` syzbot
     [not found] <20251024071154.COzwR%dmantipov@yandex.ru>
2025-10-24  9:32 ` syzbot
     [not found] <20251022140016.A5JqV%dmantipov@yandex.ru>
2025-10-22 14:36 ` syzbot
     [not found] <20241227105402.odBU4%dmantipov@yandex.ru>
2024-12-27 11:38 ` syzbot
     [not found] <20241226155305.Yro_e%dmantipov@yandex.ru>
2024-12-26 16:26 ` syzbot
2024-12-25 16:47 syzbot
2026-01-15  3:46 ` 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=69013b7a.050a0220.32483.01dd.GAE@google.com \
    --to=syzbot+7aef76bdb53b83d62a9e@syzkaller.appspotmail.com \
    --cc=dmantipov@yandex.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox