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: <C5551D9AAB213A418B7FD5E4A6F30A0702F95B64@ORSMSX106.amr.corp.intel.com>
Date:	Tue, 21 Feb 2012 19:51:54 +0000
From:	"Rose, Gregory V" <gregory.v.rose@...el.com>
To:	David Miller <davem@...emloft.net>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [RFC V3 PATCH] rtnetlink: Fix problem with buffer allocation

> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Tuesday, February 21, 2012 11:49 AM
> To: Rose, Gregory V
> Cc: netdev@...r.kernel.org
> Subject: Re: [RFC V3 PATCH] rtnetlink: Fix problem with buffer allocation
> 
> From: "Rose, Gregory V" <gregory.v.rose@...el.com>
> Date: Tue, 21 Feb 2012 17:46:27 +0000
> 
> > Having seen no other review comments on this RFC or the related
> > iproute2 RFC I'll go ahead and work with Jeff Kirsher to get these
> > patches pushed for application.
> 
> What do you mean by this?  Simply repost this patch with the fix I
> asked for, and do it ASAP.
> 
> These are not Intel device driver specific changes, there is absolutely
> no need to get Jeff involved at all.  It can only make things take more
> time and add more red tape to the process of getting this urgent fix
> propagated.
> 
> I've been extremely patient allowing you to take more than a week or
> two to code up this fix for something which causes very serious
> regressions for users, don't add any new things that will consume even
> more time.

OK, I'll post it ASAP.

- Greg

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ