linux-kernel - Re: Linux 2.6.25-rc4

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: <20080307090257.GC24047@elte.hu>
Date:	Fri, 7 Mar 2008 10:02:57 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Linux 2.6.25-rc4


* Jens Axboe <jens.axboe@...cle.com> wrote:

> > no luck - a few hundred successful randconfig bootups overnight 
> > (with a rather complex userspace startup to full X plus networking, 
> > and the testbox is used via the network to compile the next random 
> > kernel as well - etc.) and no failure at all. So there's not much we 
> > can do at this point - i'll keep you updated if anything new happens 
> > in the tests.
> 
> OK, so it could possibly be something else or perhaps something that's 
> existed for a long time.
> 
> To capture vital debugging information for cases like this, I had an 
> idea for a sysrq key that would dump queue and io scheduler info for 
> all known block devices. That should help pin point where the problem 
> lies. If we have any letters left in the sysrq namespace :-)

btw., we should reserve one sysrq letter as a "meta" character. If that 
letter is 'X' [for Xtended SysRq] then SysRq-X SysRq-B could dump the 
block info.

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