mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrey Rahmatullin <wrar@altlinux.org>
Cc: Peter Volkov <pva@gentoo.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31 regression: system hang after pptp connection established
Date: Fri, 18 Sep 2009 08:48:56 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0909180843210.4950@localhost.localdomain> (raw)
In-Reply-To: <20090918153744.GJ28743@wrars-comp.wrarsdomain>



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

      reply	other threads:[~2009-09-18 15:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 19:59 Peter Volkov
2009-09-17 20:42 ` Linus Torvalds
2009-09-17 21:12   ` Linus Torvalds
2009-09-18 11:20     ` Peter Volkov
2009-09-18 14:16       ` Linus Torvalds
2009-09-18 15:37 ` Andrey Rahmatullin
2009-09-18 15:48   ` Linus Torvalds [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.01.0909180843210.4950@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pva@gentoo.org \
    --cc=wrar@altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®