From: syzbot <syzbot+bfc9a0ccf0de47d04e8c@syzkaller.appspotmail.com>
To: amir73il@gmail.com, brauner@kernel.org, hdanton@sina.com,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
miklos@szeredi.hu, neil@brown.name, neilb@ownmail.net,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [overlayfs?] WARNING in shmem_unlink (2)
Date: Thu, 27 Nov 2025 23:28:03 -0800 [thread overview]
Message-ID: <69294f03.a70a0220.d98e3.0132.GAE@google.com> (raw)
In-Reply-To: <20251128065521.9509-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+bfc9a0ccf0de47d04e8c@syzkaller.appspotmail.com
Tested-by: syzbot+bfc9a0ccf0de47d04e8c@syzkaller.appspotmail.com
Tested on:
commit: e538109a Merge tag 'drm-fixes-2025-11-28' of https://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17bc7e12580000
kernel config: https://syzkaller.appspot.com/x/.config?x=38a0c4cddc846161
dashboard link: https://syzkaller.appspot.com/bug?extid=bfc9a0ccf0de47d04e8c
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=17af2e12580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-11-28 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 20:36 [syzbot] [overlayfs?] WARNING in shmem_unlink (2) syzbot
2025-11-27 21:42 ` NeilBrown
2025-11-27 23:41 ` Hillf Danton
2025-11-27 23:56 ` syzbot
2025-11-28 1:16 ` NeilBrown
2025-11-28 1:22 ` [PATCH] ovl: fail ovl_lock_rename_workdir() if either target is unhashed NeilBrown
2025-11-28 6:55 ` Hillf Danton
2025-11-28 7:28 ` syzbot [this message]
2025-11-28 9:39 ` Christian Brauner
2025-11-28 9:54 ` Amir Goldstein
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=69294f03.a70a0220.d98e3.0132.GAE@google.com \
--to=syzbot+bfc9a0ccf0de47d04e8c@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=neil@brown.name \
--cc=neilb@ownmail.net \
--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