linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Dan Carpenter <dan.carpenter@oracle.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: Joe Perches <joe@perches.com>,
	Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	devel@driverdev.osuosl.org,
	Sudip Mukherjee <sudip@vectorindia.org>,
	linux-wireless@vger.kernel.org, Stable <stable@vger.kernel.org>,
	netdev@vger.kernel.org, Haggai Eran <haggai.eran@gmail.com>,
	Arek Rusniak <arek.rusi@gmail.com>
Subject: Re: [PATCH] staging: r8712u: Fix kernel warning for improper call of del_timer_sync()
Date: Tue, 26 May 2015 11:40:31 -0500	[thread overview]
Message-ID: <5564A1FF.8080301@lwfinger.net> (raw)
In-Reply-To: <20150526154826.GJ11588@mwanda>

On 05/26/2015 10:48 AM, Dan Carpenter wrote:
> On Tue, May 26, 2015 at 07:14:01AM -0700, Greg KH wrote:
>> I take the blame for any problems with Outreachy patches.  Given the
>> huge volume of them, one bug out of 900 isn't that bad of a percentage.
>
> We don't get many bugs through outreachy, but this isn't the first one.
> For example, in March and April people complained about:
>
> 95745e9b1de2 ('staging: lustre: Use kasprintf.')
> 45de432775d6 ('Staging: rtl8712: Use memdup_user() instead of copy_from_user()')
>
> There have been others but I have a short memory.  We have this
> discussion every time.  How come no one caught this bug in review??  Oh,
> it never went through the list.
>
> I'm fine with 5 bugs per 900 patches or whatever.  I wish that the
> patches came to the list, but I get that that would double your review
> workload to review 900 patches on the outreachy list and again on the
> normal dev list.

Adding the maintainer to the original list would still be a good step. I'm not 
sure that I would have caught "rtl8712: Use memdup_user() instead of 
copy_from_user()" in review, but I certainly would have seen that it was not 
proper to do a blanket substitution of del_timer_sync() for a wrapper that used 
del_timer().

Obviously the awful coding in rtl8712 contains more traps to trick the novices 
than does most code. It also predates a lot of changes in checkpatch.pl and 
contains a lot of low-hanging fruit.

Larry


  reply	other threads:[~2015-05-26 16:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-23 21:16 [PATCH] staging: r8712u: Fix kernel warning for improper call of del_timer_sync() Larry Finger
2015-05-24 19:03 ` Haggai Eran
2015-05-25  0:11   ` Larry Finger
2015-05-25  9:17     ` Dan Carpenter
     [not found]       ` <CAK-LDb+1WscLTFw=NDY=_aUOGw72a4wRsqCU-1N+KJ11k15S5w@mail.gmail.com>
2015-05-25 10:12         ` Dan Carpenter
2015-05-25 15:52         ` Larry Finger
2015-05-25 17:37       ` Joe Perches
2015-05-26  4:46         ` Sudip Mukherjee
2015-05-26  4:55           ` Joe Perches
2015-05-26  5:02             ` Sudip Mukherjee
2015-05-26  5:07               ` Joe Perches
2015-05-26  5:30                 ` Sudip Mukherjee
2015-05-26 15:31                   ` Larry Finger
2015-05-26 14:14                 ` Greg KH
2015-05-26 14:48                   ` Joe Perches
2015-05-26 16:35                     ` Greg KH
2015-05-26 17:06                       ` Joe Perches
2015-05-26 20:25                         ` Dan Carpenter
2015-05-26 20:30                         ` Greg KH
2015-05-26 20:09                       ` Dan Carpenter
2015-05-26 15:48                   ` Dan Carpenter
2015-05-26 16:40                     ` Larry Finger [this message]
2015-05-25 16:02 ` Larry Finger
2015-05-31  2:53   ` Greg KH
2015-05-31  2:54     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2015-05-25  4:42 Sudip Mukherjee
2015-05-25 15:59 ` Larry Finger

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=5564A1FF.8080301@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=arek.rusi@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=haggai.eran@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sudip@vectorindia.org \
    --cc=sudipm.mukherjee@gmail.com \
    /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).