From: Julia Lawall <julia.lawall@lip6.fr>
To: "Nicolas Palix (LIG)" <Nicolas.Palix@imag.fr>
Cc: Kees Cook <keescook@chromium.org>,
Julia Lawall <Julia.Lawall@lip6.fr>,
linux-kernel@vger.kernel.org,
Gilles Muller <Gilles.Muller@lip6.fr>,
Michal Marek <mmarek@suse.com>,
cocci@systeme.lip6.fr
Subject: Re: [PATCH] coccicheck: Fix missing 0 index in kill loop
Date: Tue, 17 May 2016 16:33:58 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1605171633460.3068@hadrien> (raw)
In-Reply-To: <573B2B89.7060004@imag.fr>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 977 bytes --]
On Tue, 17 May 2016, Nicolas Palix (LIG) wrote:
> Le 16/05/16 14:55, Kees Cook a écrit :
> > By default, "seq" counts from 1, but processes were starting counting
> > from 0, so when interrupted, coccicheck would leave the 0th process
> > running.
> >
> > Signed-off-by: Kees Cook <keescook@chromium.org>
>
> Acked-by: Nicolas Palix <nicolas.palix@imag.fr>
Acked-by: Julia Lawall <julia.lawall@lip6.fr>
>
>
> > ---
> > scripts/coccicheck | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/scripts/coccicheck b/scripts/coccicheck
> > index b2d758188f2f..dd85a455b2ba 100755
> > --- a/scripts/coccicheck
> > +++ b/scripts/coccicheck
> > @@ -98,7 +98,7 @@ run_cmd() {
> > }
> >
> > kill_running() {
> > - for i in $(seq $(( NPROC - 1 )) ); do
> > + for i in $(seq 0 $(( NPROC - 1 )) ); do
> > if [ $VERBOSE -eq 2 ] ; then
> > echo "Killing ${SPATCH_PID[$i]}"
> > fi
> >
>
>
> --
> Nicolas Palix
> http://lig-membres.imag.fr/palix/
>
>
next prev parent reply other threads:[~2016-05-17 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 12:55 Kees Cook
2016-05-17 14:32 ` Nicolas Palix (LIG)
2016-05-17 14:33 ` Julia Lawall [this message]
2016-05-19 7:57 ` Michal Marek
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=alpine.DEB.2.10.1605171633460.3068@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=Nicolas.Palix@imag.fr \
--cc=cocci@systeme.lip6.fr \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.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
all inboxes | Powered by JetHome®