From: Dave Jones <davej@redhat.com>
To: gregkh@linuxfoundation.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: rtl8821ae.
Date: Sun, 2 Feb 2014 11:05:12 -0500 [thread overview]
Message-ID: <20140202160512.GA4946@redhat.com> (raw)
In-Reply-To: <52ee2ee736e00_2c3211fc86c5851f@209.249.196.67.mail>
On Sun, Feb 02, 2014 at 03:41:27AM -0800, scan-admin@coverity.com wrote:
>
> Please find the latest report on new defect(s) introduced to Linux found with Coverity Scan.
>
> Defect(s) Reported-by: Coverity Scan
> Showing 20 of 83 defect(s)
Ugh, this is even worse than the usual realtek drivers. (With the exception of rtl8188eu)
All 83 of those new defects came from this new driver, and while there's
a bunch of "who cares" type things in there, there's a load of stuff that
needs fixing a lot more urgently than CodingStyle issues or anything else in the TODO
for that driver.
A bigger problem though, is what is the plan for these realtek drivers ?
They've been in staging forever. rtl8187se has been there for _five_ years with
no indication it's ever getting promoted to first class status.
The git logs are littered mostly with CodingStyle cleanups, sparse cleanups and such,
meanwhile for five years they've had out of bounds reads, overflows, and such
for this whole time. Even worse, when one of the drivers gets fixes for actual
problems like this, they never make it back to Realtek, who clone the same
old shitty driver they shipped last time, and reintroduce new variants of the
same damn bugs, and then we import the new turd into staging and start all over again.
I get the whole "a shit driver is better than no driver", but there's no discernable
effort to ever improve this pile, just to keep adding to it.
Dave
next parent reply other threads:[~2014-02-02 16:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52ee2ee736e00_2c3211fc86c5851f@209.249.196.67.mail>
2014-02-02 16:05 ` Dave Jones [this message]
2014-02-02 18:01 ` rtl8821ae Greg KH
2014-02-02 18:07 ` rtl8821ae Stefan Lippers-Hollmann
2014-02-02 19:36 ` rtl8821ae Malcolm Priestley
2014-02-03 17:05 ` rtl8821ae Larry Finger
2014-02-03 20:02 ` rtl8821ae Dan Carpenter
2014-02-03 20:12 ` rtl8821ae Dan Carpenter
2014-02-03 20:18 ` rtl8821ae Linus Torvalds
[not found] ` <CAN8YU5PJWqnaBN_oaZ-yZjV-s9oCkKPa4ebk-kNbhPSgpd3_wQ@mail.gmail.com>
2014-02-04 9:28 ` rtl8821ae Dan Carpenter
2014-02-04 14:41 ` rtl8821ae Andrea Merello
2014-02-04 15:42 ` rtl8821ae Larry Finger
2014-02-04 17:57 ` rtl8821ae Larry Finger
2014-02-04 19:57 ` rtl8821ae Andrea Merello
2014-02-04 23:05 ` rtl8821ae Larry Finger
2014-02-05 10:52 ` rtl8821ae Andrea Merello
2014-02-05 12:34 ` rtl8821ae Dan Carpenter
2014-02-05 14:49 ` rtl8821ae Andrea Merello
2014-02-04 18:00 ` rtl8821ae Linus Torvalds
2014-02-03 20:19 ` rtl8821ae Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140202160512.GA4946@redhat.com \
--to=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).