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: <200809250112.40661.elendil@planet.nl>
Date:	Thu, 25 Sep 2008 01:12:39 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
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 Thursday 25 September 2008, Linus Torvalds wrote:
> 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).

Yep, I agree it's basically harmless and I have been ignoring it. But that 
does not make it less annoying as, because of the call trace, it will 
continue to show up in logcheck mails every time.

If no other solution is found soon, would a patch to just skip the sysctl 
table check for this particular case be acceptable?
--
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/