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

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

2023-07-20 Thread Finn Thain
On Fri, 21 Jul 2023, Dave Chinner wrote: > > I suspect that this is one of those catch-22 situations: distros are > > going to enable every feature under the sun. That doesn't mean that > > anyone is actually _using_ them these days. I think the value of filesystem code is not just a question o

Re: maintainer communication

2013-12-23 Thread Finn Thain
On Mon, 23 Dec 2013, Thorsten Glaser wrote: > Finn Thain dixit: > > >Why is CONFIG_SERIAL_PMACZILOG to be disabled? And why was > > See the discussion in the thread before this message. I've seen no discussion of this on debian-68k or linux-m68k. What discussion are

Re: maintainer communication (was Re: Debian kernel regression, was Re: Modernizing a Macintosh LC III)

2013-12-23 Thread Finn Thain
On Mon, 23 Dec 2013, Thorsten Glaser wrote: > > CONFIG_EARLY_PRINTK=y and CONFIG_SERIAL_PMACZILOG=n Why is CONFIG_SERIAL_PMACZILOG to be disabled? And why was CONFIG_EARLY_PRINTK disabled? > I think we need to file bugs in the BTS for each of these instances in > the future, instead of trying