public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6e493c165d26d6fcbf72@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, penguin-kernel@i-love.sakura.ne.jp,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] [ocfs2?] possible deadlock in dqget
Date: Mon, 20 Oct 2025 09:30:01 -0700	[thread overview]
Message-ID: <68f66389.050a0220.1be48.000e.GAE@google.com> (raw)
In-Reply-To: <7b1f58cb-d42f-4357-816b-22d65792f041@I-love.SAKURA.ne.jp>

Hello,

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

Reported-by: syzbot+6e493c165d26d6fcbf72@syzkaller.appspotmail.com
Tested-by: syzbot+6e493c165d26d6fcbf72@syzkaller.appspotmail.com

Tested on:

commit:         211ddde0 Linux 6.18-rc2
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=154adde2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=568e69ca0c2fa75
dashboard link: https://syzkaller.appspot.com/bug?extid=6e493c165d26d6fcbf72
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=11b4dde2580000

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

  reply	other threads:[~2025-10-20 16:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01  8:09 [syzbot] [ext4?] [ocfs2?] possible deadlock in dqget syzbot
2025-10-19  8:33 ` Tetsuo Handa
2025-10-19  8:58   ` syzbot
2025-10-20 13:27   ` Tetsuo Handa
2025-10-20 16:30     ` syzbot [this message]
2025-10-21 10:38     ` Tetsuo Handa
2025-10-21 11:01       ` syzbot
2025-10-21 22:02       ` Tetsuo Handa
2025-10-22  5:01         ` 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=68f66389.050a0220.1be48.000e.GAE@google.com \
    --to=syzbot+6e493c165d26d6fcbf72@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --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