Re: sym scsi driver problem with 2.6.26 or newer debian kernel on p610 (fwd)

2009-06-13 Thread Matthew Wilcox
On Sat, Jun 13, 2009 at 09:49:31PM +0200, Guennadi Liakhovetski wrote: > Forwarding to the scsi mailing list and driver maintainer. It's an interrupt problem. Talk to the powerpc people, not me. -- Matthew Wilcox Intel Open Source Technology Centre "B

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

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: please rebuild survex 1.0.25

2003-05-06 Thread Matthew Wilcox
On Tue, May 06, 2003 at 01:57:33PM +0100, Wookey wrote: > Hi guys, > > Survex has been stuck for a while waiting on the libwxgtk2.2 -> 2.4 > transition. > > libwxgtk-2.4 has now compiled on all architectures so survex should too (it > previously failed due to missing libwxgtk2.4-dev on hppa and p

Packages stuck in Uploaded

2003-10-17 Thread Matthew Wilcox
You probably just want to give this package back to the buildd: base/pcmcia-cs_3.2.2-1.3: Uploaded by dan-voltaire [extra:out-of-date] Previous state was Building until 2003 Sep 26 12:11:51 -- "It's not Hollywood. War is real, war is primarily not about defeat or victory, it is about death.

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: [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 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