linux-kernel - 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]

Message-Id: <20080915.150746.24873255.davem@davemloft.net>
Date:	Mon, 15 Sep 2008 15:07:46 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jeff@...zik.org
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [git patches] net driver fixes

From: Jeff Garzik <jeff@...zik.org>
Date: Mon, 15 Sep 2008 17:24:59 -0400

> So, my takeaway from this is...
> 
> 1) Creating a bugzilla entry magically makes a bug fix acceptable?

It adds more credence to the bug.  Because it's usually reported
by a user.

> 2) We no longer want "this kills the driver" fixes?

I don't take that away from what I said.

Why is it so important to fix something "RIGHT NOW" that
has existed forever?  Where were these fixes during the
merge window?

> I disagree with that logic, and I seriously doubt Linus wants to turn
> away serious fixes to serious problems.

He wants the time outside of the merge window to work on fixing
regressions and exploitable problems.  This is so that the process
actually ends at some point.

> You just rejected patches that (a) fixed dead ethernet [de2104x],

And it's getting submitted now, because?!?

 (b) fixed an
> oops [WAN], and

It's WAN, it's been there forever, who cares and why now?

> (c) fixed memory corruption [ehea].

Again, it's been there for quite some time, why is it "now"
all of sudden now important to integrate this fix?
--
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/