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

2023-07-20 Thread Matthew Wilcox
On Fri, Jul 21, 2023 at 11:03:28AM +1000, Finn Thain wrote: > 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 thes

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

2023-07-20 Thread Matthew Wilcox
On Thu, Jul 20, 2023 at 05:38:52PM -0400, Jeffrey Walton wrote: > On Thu, Jul 20, 2023 at 2:39 PM Matthew Wilcox wrote: > > > > On Thu, Jul 20, 2023 at 07:50:47PM +0200, John Paul Adrian Glaubitz wrote: > > > > Then we should delete the HFS/HFS+ filesy

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

2023-07-20 Thread Matthew Wilcox
On Thu, Jul 20, 2023 at 07:50:47PM +0200, John Paul Adrian Glaubitz wrote: > > Then we should delete the HFS/HFS+ filesystems. They're orphaned in > > MAINTAINERS and if distros are going to do such a damnfool thing, > > then we must stop them. > > Both HFS and HFS+ work perfectly fine. And if di

Re: a small C program to test xdm's /dev/mem reading on your architecture

2002-08-26 Thread Matthew Wilcox
On Mon, Aug 26, 2002 at 09:10:54PM +0200, Marcus Brinkmann wrote: > Also, reading /dev/mem doesn't sound very secure at all (even if it works) > because the patterns in the memory of a computer are probably predictable > and a lot of information can be observed from the outside (which processes > a

Re: a small C program to test xdm's /dev/mem reading on your architecture

2002-08-26 Thread Matthew Wilcox
On Mon, Aug 26, 2002 at 09:06:00AM -0400, Carlos O'Donell wrote: > Done. I've submitted the output for HPPA boxes running 32 and 64-bit > kernels. Looks like they pass without any problem. I'll pass on the yes, but it may well crash them. some parts of /dev/mem map random IO addresses which may