linux-kernel - Re: 3.3-rc2 snd_pcm lockdep backtrace

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120208181014.GA6188@zod.bos.redhat.com>
Date:	Wed, 8 Feb 2012 13:10:15 -0500
From:	Josh Boyer <jwboyer@...hat.com>
To:	Maciej Rutecki <maciej.rutecki@...il.com>
Cc:	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
	kernel-team@...oraproject.org
Subject: Re: 3.3-rc2 snd_pcm lockdep backtrace

On Wed, Feb 08, 2012 at 06:54:08PM +0100, Maciej Rutecki wrote:
> On poniedziałek, 6 lutego 2012 o 15:56:22 Josh Boyer wrote:
> 
> I created a Bugzilla entry at 
> https://bugzilla.kernel.org/show_bug.cgi?id=42746
> for your bug report, please add your address to the CC list in there, thanks!

Er... why exactly?

I mean, great I don't really mind at all that a bugzilla.kernel.org bug
was opened, but

1) there's already a bug opened in the RH bugzilla for this
2) I've already emailed the upstream developers and list about it
3) ALSA actually has it's own bug tool

so unless the ALSA devs are going to do something with that particular
bug I don't see a huge amount of value.

As an aside, I'm basically an intermediary here.  The original reporter
in the RHT bug should probably add their email to CC.

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