netdev - Re: [PATCH 1/1] tg3: Avoid Send BD corruption

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20080911.163020.209586511.davem@davemloft.net>
Date:	Thu, 11 Sep 2008 16:30:20 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mchan@...adcom.com
Cc:	mcarlson@...adcom.com, netdev@...r.kernel.org, andy@...yhouse.net
Subject: Re: [PATCH 1/1] tg3: Avoid Send BD corruption

From: "Michael Chan" <mchan@...adcom.com>
Date: Thu, 11 Sep 2008 16:19:28 -0700

> OK, we'll resubmit this for net-next then.  But I still think this one
> should qualify.  We do internal testing to find as many problems as
> possible so that real users don't see too many of them.

If driver authors can do these kinds of things to their heart's
content, and then submit lots of patches fixing all the bugs they
find, where are we able to draw the line?

That's the problem.  And right now my (and Linus's) solution is to push
back and say no unless it meets strict criteria.
--
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