From: Kees Cook <keescook@chromium.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Mansour Moufid <mansourmoufid@gmail.com>, cocci@inria.fr
Subject: Re: matching an arbitrary struct or union (but not scalars)
Date: Mon, 20 Sep 2021 21:11:12 -0700 [thread overview]
Message-ID: <202109202109.69B0020@keescook> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2109181812421.2929@hadrien>
On Sat, Sep 18, 2021 at 06:13:32PM +0200, Julia Lawall wrote:
>
>
> On Sat, 18 Sep 2021, Kees Cook wrote:
>
> > On Sat, Sep 18, 2021 at 08:40:19AM -0700, Kees Cook wrote:
> > > Yeah, this is for the kernel. Thanks for helping with this! I was able
> > > to continue the construction and get it working. :)
> >
> > I spoke too soon; it fails on the kernel with:
> > EXN: Coccinelle_modules.Common.Timeout
>
> What is your command line? If it times out on one file, it should just
> move on to the next one.
To work around potential intermixed output, I rewrite the normal
coccicheck arguments that uses --jobs to launch $nproc many spatch
instances with -max and -index. I will switch back to using --jobs and
see if I still get corrupted patches... (It's been a while since I
created this alternative workflow.)
-Kees
--
Kees Cook
next prev parent reply other threads:[~2021-09-21 4:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202109161609.9AB60A934B@keescook>
2021-09-17 4:35 ` matching an arbitrary struct or union (but not scalars) Mansour Moufid
2021-09-17 6:37 ` Julia Lawall
2021-09-17 6:34 ` Julia Lawall
2021-09-17 19:16 ` Mansour Moufid
2021-09-18 15:40 ` Kees Cook
2021-09-18 15:49 ` Kees Cook
2021-09-18 16:13 ` Julia Lawall
2021-09-21 4:11 ` Kees Cook [this message]
2021-09-21 5:37 ` Julia Lawall
2021-09-18 16:12 ` Julia Lawall
2021-09-18 18:50 ` Julia Lawall
2021-09-21 4:08 ` Kees Cook
2021-09-21 5:35 ` 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=202109202109.69B0020@keescook \
--to=keescook@chromium.org \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=mansourmoufid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.