linux-kernel - Re: 2.6.31 regression: system hang after pptp connection established

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

Message-ID: <alpine.LFD.2.01.0909180843210.4950@localhost.localdomain>
Date:	Fri, 18 Sep 2009 08:48:56 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andrey Rahmatullin <wrar@...linux.org>
cc:	Peter Volkov <pva@...too.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.31 regression: system hang after pptp connection
 established

On Fri, 18 Sep 2009, Andrey Rahmatullin wrote:
>
> On Thu, Sep 17, 2009 at 11:59:13PM +0400, Peter Volkov wrote:
> > Is this problem known? 
> Yes, it's described at http://bugzilla.kernel.org/show_bug.cgi?id=14179
> since Tuesday.
> 
> On Fri, Sep 18, 2009 at 07:16:39AM -0700, Linus Torvalds wrote:
> > > The patch fixes the problem here. Thank you very much.
> > Hey, thank _you_ for the sysrq output, that made it quite debuggable.
> > Committed as 202c4675c, and I cc'd stable.
> Thanks for the fix, but should I send bugreports directly here next time
> instead of filing a bug in bugzilla.kernel.org and waiting for response
> that will never come?

Bugzilla is great, but you should _also_ target the maintainers directly 
and let them know.  And especially if you have bisected things, always cc 
everybody that is listed in the commit.

Otherwise, what happens is that other people not directly involved will 
eventually look at the regression list, and see it - but that generally 
happens much later. So things will get fixed from just the bugzilla report 
too, but you'll have a much longer latency than required.

In fact, if you can bisect it to a single commit (especially a small one 
like this), then bugzilla is the secondary, rather than the primary place. 
Bugzilla is great for keeping track of things and trying to avoid losing 
reports, but that comes at the expense of not being very convenient for 
short-term stuff.

So if you have a very targeted bugreport, and know who to send a report 
to, try the direct route first. Then, if nothing happens immediately, open 
a bugzilla (or open the bugzilla immediately, just in case, but see it 
as a "fallback" thing).

			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/