netdev - Re: [git patches] net driver fixes

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]

Date:	Mon, 15 Sep 2008 16:45:43 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [git patches] net driver fixes

On Mon, Sep 15, 2008 at 01:27:16PM -0700, David Miller wrote:
> From: Jeff Garzik <jeff@...zik.org>
> Date: Mon, 15 Sep 2008 16:17:50 -0400
> 
> > On Mon, Sep 15, 2008 at 12:09:17PM -0700, David Miller wrote:
> > > From: Jeff Garzik <jeff@...zik.org>
> > > Date: Sat, 13 Sep 2008 16:35:48 -0400
> > > 
> > > > Includes several fixes from my slice of the akpm patch pie.
> > > 
> > > Which of these have regression and/or bugzilla entries?
> > > 
> > > This is too much and I want to see it trimmed down.
> > 
> > What do you not want?  The two warning fixes (mlx4, cs89x0) akpm seemed
> > to want in 2.6.27, the 8139too change is cosmetic.  The other stuff is
> > critical AFAICS.
> 
> I'll take another look at the queue and try to give you some
> more specific feedback.
> 
> I can think of about 3 or 4 entries on the posted regression
> list that might be appropriate, so I essentially expected to
> see that many commits, give or take one or two.

Don't stick strictly to that list...  We want an oops fix even if
the oops is present in 2.6.26.  We want a spinlock fix that makes a
driver work properly on SMP, even if that bug is present in 2.6.26.  We
want a build fix, etc.

	Jeff



--
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