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: <201205091857.14406.wolfgang.walter@stwm.de>
Date:	Wed, 9 May 2012 18:57:13 +0200
From:	Wolfgang Walter <wolfgang.walter@...m.de>
To:	David Miller <davem@...emloft.net>
Cc:	gregkh@...uxfoundation.org, stable@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: 3.3.x: e1000 and ixgbe hang

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.

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?

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ