Re: [syzbot] [hfs?] WARNING in hfs_write_inode
- To: Matthew Wilcox <willy@infradead.org>
- Cc: Dave Chinner <david@fromorbit.com>, Jeff Layton <jlayton@kernel.org>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, Dmitry Vyukov <dvyukov@google.com>, Viacheslav Dubeyko <slava@dubeyko.com>, Arnd Bergmann <arnd@arndb.de>, Linus Torvalds <torvalds@linux-foundation.org>, syzbot <syzbot+7bb7cd3595533513a9e7@syzkaller.appspotmail.com>, Andrew Morton <akpm@linux-foundation.org>, christian.brauner@ubuntu.com, Damien Le Moal <damien.lemoal@opensource.wdc.com>, Linux FS Devel <linux-fsdevel@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>, syzkaller-bugs@googlegroups.com, ZhangPeng <zhangpeng362@huawei.com>, linux-m68k@lists.linux-m68k.org, debian-ports <debian-ports@lists.debian.org>
- Subject: Re: [syzbot] [hfs?] WARNING in hfs_write_inode
- From: Finn Thain <fthain@linux-m68k.org>
- Date: Fri, 21 Jul 2023 18:14:04 +1000 (AEST)
- Message-id: <[🔎] 3eca2dab-df70-9d91-52a1-af779e3c2e04@linux-m68k.org>
- In-reply-to: <[🔎] ZLnbN4Mm9L5wCzOK@casper.infradead.org>
- References: <46F233BB-E587-4F2B-AA62-898EB46C9DCE@dubeyko.com> <Y7bw7X1Y5KtmPF5s@casper.infradead.org> <50D6A66B-D994-48F4-9EBA-360E57A37BBE@dubeyko.com> <CACT4Y+aJb4u+KPAF7629YDb2tB2geZrQm5sFR3M+r2P1rgicwQ@mail.gmail.com> <ZLlvII/jMPTT32ef@casper.infradead.org> <[🔎] 2d0bd58fb757e7771d13f82050a546ec5f7be8de.camel@physik.fu-berlin.de> <[🔎] ZLl2Fq35Ya0cNbIm@casper.infradead.org> <[🔎] 868611d7f222a19127783cc8d5f2af2e42ee24e4.camel@kernel.org> <[🔎] ZLmzSEV6Wk+oRVoL@dread.disaster.area> <[🔎] 60b57ae9-ff49-de1d-d40d-172c9e6d43d5@linux-m68k.org> <[🔎] ZLnbN4Mm9L5wCzOK@casper.infradead.org>
On Fri, 21 Jul 2023, Matthew Wilcox wrote:
>
> You've misunderstood. Google have decided to subject the entire kernel
> (including obsolete unmaintained filesystems) to stress tests that it's
> never had before. IOW these bugs have been there since the code was
> merged. There's nothing to back out. There's no API change to blame.
> It's always been buggy and it's never mattered before.
>
I'm not blaming the unstable API for the bugs, I'm blaming it for the
workload. A stable API (like a userspace API) decreases the likelihood
that overloaded maintainers have to orphan a filesystem implementation.
Reply to: