linux-kernel - Re: Warning/Oops report of the week of September 16th, 2008

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.1.10.0809241541320.3265@nehalem.linux-foundation.org>
Date:	Wed, 24 Sep 2008 15:45:30 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Frans Pop <elendil@...net.nl>
cc:	linux-kernel@...r.kernel.org,
	Arjan van de Ven <arjan@...radead.org>, tglx@...x.de,
	mingo@...e.hu
Subject: Re: Warning/Oops report of the week of September 16th, 2008

On Thu, 25 Sep 2008, Frans Pop wrote:
> 
> > Rank 6: parport_device_proc_register (warning)
> >         Reported 62 times (3942 total reports)
> >         Duplicate /proc registration in the parport driver
> >         This warning was last seen in version 2.6.26.3, and first seen
> >         in 2.6.24-rc5.
> 
> Note that I'm still seeing this in 2.6.27-rc7. This is now one of the 
> oldest entries in the list and as it happens for *every* print job, it's 
> quite an annoying one.
> 
> Unfortunately I still cannot get kerneloops to work for me.

Al and Arjan looked at this one at the KS, and quite frankly, the warning 
is just bogus.

Or rather, it's a warnign about the parport /proc interface. The fact is, 
the parport code can generate multiple "instances" of things that 
time-slice on the port, but they have all ended up always just registering 
under the same name. IOW, it's a bug in the _user_ interface, not the 
kernel.

I'd like to remove the file entirely (probably nobody uses it), but Al 
said he could perhaps send patches to extend it (yet leave the old name to 
point to the first instance, the way it always has). 

In the meantime, that warning is just best ignored entirely. It's not a 
kernel bug per se, or even anything that is fixable without changing 
exported user interfaces that in my opinion aren't necessarily even 
_worth_ changing (the only reasonable change is extending on the insane 
interface that nobody cares about).

I think Arjan agreed to just remove it from his statistics, but maybe he's 
just ignoring _new_ entries ;)

			Linus
--
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/