linux-kernel - Re: What made this bug report better?

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 24 Feb 2009 18:58:55 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Sitsofe Wheeler <sitsofe@...oo.com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: What made this bug report better?

On Tue, Feb 24, 2009 at 08:16:12AM +0000, Sitsofe Wheeler wrote:
> On Tue, Feb 24, 2009 at 01:43:22PM +1030, Rusty Russell wrote:
> > On Friday 20 February 2009 20:57:05 Sitsofe Wheeler wrote:
> > > What happened this time that made things succesful? Was the original
> > > mail too big? Did it not make it to the list?
> > 
> > Frederic was the difference; he pulled me in by CC'ing me, once he figured
> > out it was my bug.
> 
> Rusty, Ingo: Thanks for letting me know!
> 
> Frederic: What information are you looking for in bug reports? 


Like everyone, the most possible matching traces, locking states, and other
states (irq, atomic, ...), well it depends on the particular case.

The best thing is to provide a way to reproduce it, that's what you did, so
that we can use specific tracers for specific issues.


> What sort of areas interest you?

You mean, what I'm interested in the kernel?
All the kernel :-)
Though I have a preference for the kernel core, and improving tracing
because I'm lazy and I like when there are tools which do most of the things
for me.
 
> -- 
> Sitsofe | http://sucs.org/~sits/

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