Re: [syzbot] [hfs?] WARNING in hfs_write_inode

2023-07-21 Thread gene heskett
On 7/21/23 09:19, Theodore Ts'o wrote: On Fri, Jul 21, 2023 at 06:14:04PM +1000, Finn Thain wrote: 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

Re: [syzbot] [hfs?] WARNING in hfs_write_inode

2023-07-21 Thread Theodore Ts'o
On Fri, Jul 21, 2023 at 06:14:04PM +1000, Finn Thain wrote: > > 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. You are incorr

Re: [syzbot] [hfs?] WARNING in hfs_write_inode

2023-07-21 Thread gene heskett
On 7/21/23 04:31, Finn Thain wrote: 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 me

Re: [syzbot] [hfs?] WARNING in hfs_write_inode

2023-07-21 Thread Finn Thain
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