Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 14 Aug 2023 17:24:37 +0200
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
Message-ID: <2023081404-stuffy-relic-d126@gregkh>
References: <CALcu4rbCwMHyi3w7Ruv=eRw-nq7+cxz8fJ+WCoN932mDjg-vBg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALcu4rbCwMHyi3w7Ruv=eRw-nq7+cxz8fJ+WCoN932mDjg-vBg@mail.gmail.com>
Precedence: bulk

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