linux-kernel - Re: [GIT pull] timer fixes for 3.4

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: <CA+55aFzP-DmGUqGcnxj2mq-mvmOXA7k-zgOrdDRY3WA9N5dmBg@mail.gmail.com>
Date:	Thu, 12 Apr 2012 15:31:29 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Sasikantha Babu <sasikanth.v19@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: [GIT pull] timer fixes for 3.4

On Thu, Apr 12, 2012 at 3:26 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
>
> I ran it through all the various (outdated) distros I have handy and
> the printk didn't show once.
>
> I tried to figure out the reason for this NULL pointer thing, but
> there is no trace of it on the intarwebs at all.

Ok. If we don't see any reports of messages, we can certainly remove it.

That said, would people actually *report* those messages?

In general, for things like this, it's probably better to just make
the change (especially if you have several distros you can test), and
then add a printk_once() for the case that changed. Then, if people
actually report it as some program stopping to work, the dmesg
hopefully clues us in about the reason for the program not working.
But that would have needed to happen during the merge window, it's too
late now.

Whatever. We'll see if somebody reports the message.

                     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/