public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Kernel janitors website?
Date: Fri, 15 Feb 2013 11:46:52 +0000	[thread overview]
Message-ID: <20130215114652.GE6853@mwanda> (raw)
In-Reply-To: <87d2w2u5qv.fsf@steelpick.2x.cz>

On Fri, Feb 15, 2013 at 10:39:55AM +0000, Anuz Pratap Singh Tomar wrote:
> On Fri, Feb 15, 2013 at 10:14 AM, Dan Carpenter <dan.carpenter@oracle.com>wrote:
> 
> > On Fri, Feb 15, 2013 at 10:24:09AM +0100, Julia Lawall wrote:
> > > > Everything in staging/ is supposed to be being developed with the
> > > > goal of getting out.  The exception would the android code.
> > >
> > > OK, at one point, some code was put there that was on the way out, unless
> > > someone complained, rather than on the way in.  I think it was around the
> > > time of the final elimination of the big kernel lock.  But perhaps it was
> > > an isolated incident.  If all of the code in staging is actually of
> > > interest, maybe I should pay more attention to it in the future :)
> >
> > Oh, yes.  Telephony, serial/ and tty/ were that way.  They have been
> > deleted now.
> >
> > I think the only driver on its way out now is the one under net/.
> >
> > Is there a way to find out what all bugs exists for staging? I did search
> on bugzilla.kernel.org for keyword "staging" but the bug list seemed to be
> bit outdated or bugs fixed etc. Any other place to look for staging bugs?

Run smatch against drivers/staging/csr:

for i in $(find drivers/staging/csr -name \*.c) ; do
	~/path/to/smatch/smatch_scripts/kchecker --spammy $i
done

No error handling for kmalloc()
Locking bugs in uf_check_inactivity()
drivers/staging/csr/unifi_sme.c:884 unifi_cfg_get_info()
	warn: check that 'cfg_ap_config.shortSlotTimeEnabled'
	doesn't leak information
drivers/staging/csr/netdev.c:1989 indicate_rx_skb() warn: variable
	dereferenced before check 'dev' (see line 1979)
drivers/staging/csr/unifi_pdu_processing.c:2707
	uf_handle_uspframes_delivery() warn: was && intended here
	instead of ||?
drivers/staging/csr/csr_wifi_hip_card_sdio.c:2411
	unifi_identify_hw() error: we previously assumed
	'card->helper' could be null (see line 2404)

regards,
dan carpenter


  parent reply	other threads:[~2013-02-15 11:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 18:09 Kernel janitors website? Michal Sojka
2013-02-15  8:40 ` Dan Carpenter
2013-02-15  8:50 ` Julia Lawall
2013-02-15  9:21 ` Dan Carpenter
2013-02-15  9:24 ` Julia Lawall
2013-02-15  9:29 ` Michal Sojka
2013-02-15 10:14 ` Dan Carpenter
2013-02-15 11:46 ` Dan Carpenter [this message]
2013-02-15 13:49 ` walter harms
2013-02-15 16:31 ` Michal Sojka

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=20130215114652.GE6853@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.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