From: Greg KH <gregkh@linuxfoundation.org>
To: Yikebaer Aizezi <yikebaer61@gmail.com>
Cc: linux-kernel@vger.kernel.org, tj@kernel.org
Subject: Re: WARNING in kernfs_remove_by_name_ns
Date: Mon, 14 Aug 2023 17:24:37 +0200 [thread overview]
Message-ID: <2023081404-stuffy-relic-d126@gregkh> (raw)
In-Reply-To: <CALcu4rbCwMHyi3w7Ruv=eRw-nq7+cxz8fJ+WCoN932mDjg-vBg@mail.gmail.com>
On Mon, Aug 14, 2023 at 02:49:47PM +0800, Yikebaer Aizezi wrote:
> Hello,
>
> When using Healer to fuzz the Linux-6.5-rc5, the following crash
> was triggered.
>
> HEAD commit: 52a93d39b17dc7eb98b6aa3edb93943248e03b2f (tag: v6.5-rc5)
> git tree: upstream
>
> And I also tried to reproduce this crash on Latest Linux-6.5-rc6, it
> still exist.
Great, can you work with the proper subsystem maintainers to resolve
this (hint, look at the traceback, it's not a sysfs issue...)
Wait:
> memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=8437 'syz-executor'
> loop1: detected capacity change from 0 to 32768
> BTRFS: device fsid 84eb0a0b-d357-4bc1-8741-9d3223c15974 devid 1
> transid 7 /dev/loop1 scanned by syz-executor (8437)
> BTRFS info (device loop1): using xxhash64 (xxhash64-generic) checksum algorithm
> BTRFS info (device loop1): disk space caching is enabled
> BTRFS info (device loop1): enabling ssd optimizations
> BTRFS info (device loop1): auto enabling async discard
> FAULT_INJECTION: forcing a failure.
You forced a failure, and look, things failed!
Success!
Why is this an issue, don't force failures, and then all should be good,
right?
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-14 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 6:49 Yikebaer Aizezi
2023-08-14 15:24 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-23 12:51 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=2023081404-stuffy-relic-d126@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yikebaer61@gmail.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
all inboxes | Powered by JetHome®