From: syzbot <syzbot+ec9fab8b7f0386b98a17@syzkaller.appspotmail.com>
To: amir73il@gmail.com, hdanton@sina.com,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
miklos@szeredi.hu, neil@brown.name,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [overlayfs?] WARNING in shmem_unlink
Date: Mon, 18 Aug 2025 02:47:03 -0700 [thread overview]
Message-ID: <68a2f697.050a0220.e29e5.009e.GAE@google.com> (raw)
In-Reply-To: <20250818091720.4948-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+ec9fab8b7f0386b98a17@syzkaller.appspotmail.com
Tested-by: syzbot+ec9fab8b7f0386b98a17@syzkaller.appspotmail.com
Tested on:
commit: c17b750b Linux 6.17-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15e1eba2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e9f694461848a008
dashboard link: https://syzkaller.appspot.com/bug?extid=ec9fab8b7f0386b98a17
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=1413a442580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-08-18 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 3:08 [syzbot] [overlayfs?] WARNING in shmem_unlink syzbot
2025-08-16 5:42 ` Hillf Danton
2025-08-16 6:20 ` syzbot
2025-08-17 19:52 ` Amir Goldstein
2025-08-18 0:33 ` NeilBrown
2025-08-18 9:17 ` Hillf Danton
2025-08-18 9:47 ` syzbot [this message]
2025-08-18 11:16 ` Amir Goldstein
2025-08-18 21:35 ` NeilBrown
2025-08-27 18:23 ` Amir Goldstein
2025-08-27 18:48 ` syzbot
2025-08-17 19:52 ` Forwarded: syzbot
[not found] <CAMV7Lq7rBzOwpyRZjjs9UkXFbfgw_YPX_RvN1gx0rwn0+e=V7A@mail.gmail.com>
2025-08-17 19:59 ` [syzbot] [overlayfs?] WARNING in shmem_unlink 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=68a2f697.050a0220.e29e5.009e.GAE@google.com \
--to=syzbot+ec9fab8b7f0386b98a17@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--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=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.