public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b74150fd2ef40e716ca2@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
	 syzbot@syzkaller.appspot.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [overlayfs?] WARNING in fast_dput
Date: Sun, 30 Nov 2025 00:54:04 -0800	[thread overview]
Message-ID: <692c062c.a70a0220.d98e3.0168.GAE@google.com> (raw)
In-Reply-To: <20251130071116.724635-1-kartikey406@gmail.com>

Hello,

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

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

Tested on:

commit:         7d31f578 Add linux-next specific files for 20251128
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14231112580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6336d8e94a7c517d
dashboard link: https://syzkaller.appspot.com/bug?extid=b74150fd2ef40e716ca2
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=13ab3912580000

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

       reply	other threads:[~2025-11-30  8:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251130071116.724635-1-kartikey406@gmail.com>
2025-11-30  8:54 ` syzbot [this message]
2025-11-29 13:05 [syzbot] [overlayfs?] WARNING in fast_dput syzbot
2025-11-29 21:58 ` Hillf Danton
2025-11-29 22:18   ` syzbot
2025-11-30 10:52 ` Hillf Danton
2025-11-30 11:41   ` syzbot
2025-12-01  8:58 ` Amir Goldstein
2025-12-01  9:06   ` Al Viro
2025-12-01  9:07   ` Aleksandr Nogikh
2025-12-01 11:05     ` Amir Goldstein
2025-12-01 11:07       ` Aleksandr Nogikh
2025-12-01 12:11         ` Amir Goldstein
2025-12-01 10:18   ` 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=692c062c.a70a0220.d98e3.0168.GAE@google.com \
    --to=syzbot+b74150fd2ef40e716ca2@syzkaller.appspotmail.com \
    --cc=kartikey406@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot@syzkaller.appspot.com \
    --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