From: Takashi Iwai <tiwai@suse.de>
To: Julia Lawall <Julia.Lawall@lip6.fr>
Cc: Jaroslav Kysela <perex@perex.cz>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH 0/10] fix error return code
Date: Mon, 20 Aug 2012 11:04:59 +0200 [thread overview]
Message-ID: <s5hobm6q6h0.wl%tiwai@suse.de> (raw)
In-Reply-To: <1345359780-18647-1-git-send-email-Julia.Lawall@lip6.fr>
At Sun, 19 Aug 2012 09:02:51 +0200,
Julia Lawall wrote:
>
> These patches fix cases where the return code appears to be unintentially
> nonnegative.
The patch 10/10 seems missing. Or are all 9 patches? The patch
number suddenly changes to X/9 from 4.
In anyway, the patches 3, 5, 6, 7, 8 and 9 are applied.
I leave patches 1, 2 and 4 to Mark.
thanks,
Takashi
>
> The complete semantic match that finds the problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @ok exists@
> identifier f,ret,i;
> expression e;
> constant c;
> @@
>
> f(...) {
> <+...
> (
> return -c@i;
> |
> ret = -c@i;
> ... when != ret = e
> return ret;
> |
> if (ret < 0) { ... return ret; }
> )
> ...+> }
>
> @r exists@
> identifier ret,l,ok.f;
> expression e1,e2,e3;
> statement S;
> position p1,p2,p3;
> @@
>
> f(...) {
> ... when any
> (
> if@p1 (\(ret < 0\|ret != 0\))
> { ... return ret; }
> |
> ret@p1 = 0
> )
> ... when != ret = e1
> when != &ret
> (
> if (<+... ret = e3 ...+>) S
> |
> if (<+... &ret ...+>) S
> |
> if@p2(...)
> {
> ... when != ret = e2
> when forall
> return@p3 ret;
> }
> )
> ... when any
> }
>
> @bad exists@
> position r.p1,r.p2;
> statement S1,S2;
> identifier r.ret;
> expression e1;
> @@
>
> (
> if@p1 (\(ret < 0\|ret != 0\)) S1
> |
> ret@p1 = 0
> )
> ... when any
> ret = e1
> ... when any
> if@p2(...) S2
>
> @bad2@
> position r.p1,r.p2;
> identifier r.ret;
> expression e1;
> statement S2;
> @@
>
> ret@p1 = 0
> ... when != if (...) { ... ret = e1 ... return ret; }
> when any
> if@p2(...) S2
>
>
> @script:python depends on !bad && !bad2@
> p1 << r.p1;
> p2 << r.p2;
> p3 << r.p3;
> @@
>
> cocci.print_main("",p1)
> cocci.print_secs("",p2)
> cocci.print_secs("",p3)
> // </smpl>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2012-08-20 9:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 7:02 Julia Lawall
2012-08-19 7:02 ` [PATCH 2/10] sound/soc/fsl/imx-sgtl5000.c: " Julia Lawall
2012-08-20 19:44 ` Mark Brown
2012-08-19 7:02 ` [PATCH 1/10] sound/soc/ux500/ux500_msp_i2s.c: better use devm functions and " Julia Lawall
2012-08-19 7:02 ` [PATCH 8/9] sound/pci/rme9652/hdspm.c: " Julia Lawall
2012-08-19 7:02 ` [PATCH 7/9] sound/pci/sis7019.c: " Julia Lawall
2012-08-19 23:04 ` David Dillow
2012-08-19 7:02 ` [PATCH 6/9] sound/pci/ctxfi/ctatc.c: " Julia Lawall
2012-08-19 7:02 ` [PATCH 5/9] sound/atmel/ac97c.c: " Julia Lawall
2012-08-19 7:02 ` [PATCH 3/10] sound/atmel/abdac.c: " Julia Lawall
2012-08-19 7:02 ` [PATCH 9/9] sound/ppc/snd_ps3.c: " Julia Lawall
2012-08-19 7:03 ` [PATCH 4/9] sound/soc/omap/am3517evm.c: " Julia Lawall
2012-08-20 6:09 ` Jarkko Nikula
2012-08-20 9:04 ` Takashi Iwai [this message]
2012-08-20 9:15 ` [alsa-devel] [PATCH 0/10] " Julia Lawall
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=s5hobm6q6h0.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Julia.Lawall@lip6.fr \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
/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
all inboxes | Powered by JetHome®