From: Kees Cook <keescook@chromium.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Kees Cook <kees@kernel.org>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Ian Abbott <abbotti@mev.co.uk>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-hardening@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] comedi: Annotate struct comedi_lrange with __counted_by
Date: Sun, 1 Oct 2023 14:22:17 -0700 [thread overview]
Message-ID: <202310011421.C4F19D45@keescook> (raw)
In-Reply-To: <202310011405.7599BA9@keescook>
On Sun, Oct 01, 2023 at 02:05:46PM -0700, Kees Cook wrote:
> On Sun, Oct 01, 2023 at 09:14:02PM +0200, Julia Lawall wrote:
> > Kees,
> >
> > You can try the following.
>
> Cool! Yeah, this finds the example:
>
> drivers/comedi/drivers/rti800.c:74: struct comedi_lrange: field at offset 0 is the counter for the flex array
> drivers/comedi/drivers/rti800.c:83: struct comedi_lrange: field at offset 0 is the counter for the flex array
> drivers/comedi/drivers/rti800.c:92: struct comedi_lrange: field at offset 0 is the counter for the flex array
>
> I'll run it on the whole codebase...
It found only the struct comedi_lrange instances, but that's good to
know. :)
--
Kees Cook
next prev parent reply other threads:[~2023-10-01 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 9:14 [PATCH] comedi: Annotate struct comedi_lrange with __counted_by Christophe JAILLET
2023-09-30 20:57 ` Kees Cook
2023-10-01 7:25 ` Julia Lawall
2023-10-01 7:50 ` Christophe JAILLET
2023-10-01 7:45 ` Julia Lawall
2023-10-01 15:26 ` Kees Cook
2023-10-01 19:14 ` Julia Lawall
2023-10-01 21:05 ` Kees Cook
2023-10-01 21:22 ` Kees Cook [this message]
2023-10-01 22:21 ` Kees Cook
2023-10-02 5:38 ` Julia Lawall
2023-10-02 7:36 ` Kees Cook
2023-11-05 21:27 ` Christophe JAILLET
2023-10-01 6:43 ` Gustavo A. R. Silva
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=202310011421.C4F19D45@keescook \
--to=keescook@chromium.org \
--cc=abbotti@mev.co.uk \
--cc=christophe.jaillet@wanadoo.fr \
--cc=gustavoars@kernel.org \
--cc=hsweeten@visionengravers.com \
--cc=julia.lawall@inria.fr \
--cc=kees@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=trix@redhat.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.