| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20070428202701.GA30343@flint.arm.linux.org.uk> Date: Sat, 28 Apr 2007 21:27:01 +0100 From: Russell King <rmk+lkml@....linux.org.uk> To: Adrian Bunk <bunk@...sta.de> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Diego Calleja <diegocg@...il.com>, Chuck Ebbert <cebbert@...hat.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Linux 2.6.21 On Sat, Apr 28, 2007 at 09:53:20PM +0200, Adrian Bunk wrote: > We are already quite good at ignoring bug reports that come through > linux-kernel, and it's an _advantage_ of the kernel Bugzilla to see more > than 1600 open bugs because this tells how bad we are at handling bugs. > How many thousand bug reports have been ignored during the same time on > linux-kernel? However, look at this bug: http://bugme.osdl.org/show_bug.cgi?id=7760 It's outside my knowledge to be able to fix for various reasons: 1. I don't know _anything_ about IXP4xx hardware, so I'm not the right person to own this bug. 2. I've no idea who's looking after IXP4xx stuff now. (When it was posted to the ARM kernel list by Rob, it was ignored so I guess the IXP4xx maintainer isn't watching for bugs, if such a person even exists.) 3. I've little idea about why the MM page allocation is failing early. 4. The ARM DMA bounce code is a hack, and I'm pretty sure that this failure is a result of trying to use this contorted code instead of the relevant subsystems having a correct DMA mask. Can you make any suggestion what should be done about this bug? I'm personally very tempted to close it as "won't fix" (I wish there was a "can't fix" category.) As for my other bugs: http://bugme.osdl.org/show_bug.cgi?id=8149 Again, EP93xx is not my thing, but I've recently merged a patch to allow AMBA PL010 uarts (which are present on this platform) to use the clock control API. The EP93xx people (provided they're willing) now need to do whatever's required to resolve that bug. (Hopefully they've taken ownership of that bug now.) http://bugme.osdl.org/show_bug.cgi?id=4270 http://bugme.osdl.org/show_bug.cgi?id=5875 http://bugme.osdl.org/show_bug.cgi?id=7750 I'm no longer serial maintainer. Bug IDs after about 7000 reflect bugs submitted since I've resigned my serial maintainership, and therefore I've ignored them. It's far easier to ignore bug reports in bugzilla than it is to get categories reassigned (to whom? - dunno) or even deleted (if no one steps up presumably that's what needs to happen?) http://bugme.osdl.org/show_bug.cgi?id=7389 This one isn't a regression, or even a bug IMHO, but could be viewed as undesirable behaviour. Fixing it is utterly non-trivial though. A serial port which happens to have an IrDA device on it is still a serial port at the end of the day, and as long as we have legacy probing, a serial port at a standard COM port address will be detected as such. There's never been any facility in the kernel to get around serial ports being at standard COM port addresses. Moreover, there's a whole class of applications which want IrDA devices to be presented to userspace as a serial port rather than a special network device, so unilaterally ignoring IrDA devices which look like serial is not really an option. Basically, IrDA and serial need to develop a way to work in harmony with each other. That's a long-term thing though. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists