linux-kernel - Re: 3.3.x: e1000 and ixgbe hang

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: <20120509180727.GA14152@kroah.com>
Date:	Wed, 9 May 2012 11:07:27 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Wolfgang Walter <wolfgang.walter@...m.de>
Cc:	David Miller <davem@...emloft.net>, stable@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: 3.3.x: e1000 and ixgbe hang

On Wed, May 09, 2012 at 06:57:13PM +0200, Wolfgang Walter wrote:
> Am Mittwoch, 9. Mai 2012 schrieben Sie:
> > From: Wolfgang Walter <wolfgang.walter@...m.de>
> > Date: Wed, 9 May 2012 11:07:11 +0200
> >
> > > c) Dave Miller is a busy man.
> >
> > Therefore pinging me on crap like this makes me a more busy man, so
> > don't do it, unless you want it to take even longer for me to get
> > to it.
> 
> I don't understand why you are so unfriendly.
> 
> I didn't sent you any mail nor did I complain to you. If you read my first 
> mail on this issue then you will see that.

You were complaining to me, about how David isn't working fast enough to
solve a problem that is affecting you, when he said he would take care
of it when he got the chance to.

You didn't say it in so many words, but that was the general gist of it.
And I don't blame David for being brisk, I think it was really crappy of
you to do that.

> But when we are at it: I think that when a bug in a stable kernel is found and 
> the final fix is known it is bad practice to hord that patch till submission 
> without letting stable@ know about it. I don't mean that the patch should go 
> into the stable tree immediately. Of course it makes sense to wait some time 
> to see if it works in Linus' tree. But why should other people waste their 
> time hunting a bug already solved? And why deny people the fix?

No one is "denying" anyone anything, it's all open, you are free to take
the patch and do with it what you want, if you need to.  Some of us have
other responsibilities and tasks and will get to things as soon as we
possibly can.

In other words, trust us, if you don't, that's fine, then do it
yourself, but to try to route around the documented and well-working
procedures that we have in place, is flat out rude.

greg k-h
--
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/