linux-kernel - Re: 3.5-rc6 printk formatting problem during oom-kill.

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]

Date:	Thu, 12 Jul 2012 13:02:42 -0400
From:	Dave Jones <davej@...hat.com>
To:	Kay Sievers <kay@...y.org>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg Kroah-Hartmann <greg@...ah.com>
Subject: Re: 3.5-rc6 printk formatting problem during oom-kill.

On Thu, Jul 12, 2012 at 06:47:57PM +0200, Kay Sievers wrote:
 
 > >  > > Also, I have no idea how the hell the 'Modules linked in:' line (9th line) ended up being printed /after/ the
 > >  > > module listing began (2nd line).
 > 
 > They do not belong together. The second line is just another call to
 > the same print_modules() done from:
 >     arch/x86/kernel/dumpstack_64.c :: show_regs()
 > 
 > While we already called print_modules() a few cycles earlier from:
 >    kernel/watchdog :: watchdog_timer_fn()

ah, derp. Good spotting.
 
 > Hmm, it does not trigger your pattern. I tried adding an rmmod in that
 > loop, but that crashes after a few seconds. Some modules are just not
 > meant to be removed. :)

yeah, that's bothersome. TTBOMK, we've never survived a 'load all modules/unload all modules' ever.
 
 > I forced the watchdog to trigger by setting the timeout to 1s, but all
 > looks still fine:
 > 
 > Could it possibly be that we get some sort of corruption somewhere
 > else while running trinity and load modules?

I suppose anything is possible, but it's surprisingly consistent.

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