From: SeongJae Park <sj@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Qing Zhao <qing.zhao@oracle.com>,
linux-hardening@vger.kernel.org
Subject: Re: [RFC PATCH] mm/damon/sysfs: add __counted_by() annotation
Date: Sat, 26 Aug 2023 00:54:47 +0000 [thread overview]
Message-ID: <20230826005447.109776-1-sj@kernel.org> (raw)
In-Reply-To: <202308251426.94092475C3@keescook>
Hi Kees,
On Fri, 25 Aug 2023 14:32:34 -0700 Kees Cook <keescook@chromium.org> wrote:
> On Fri, Aug 25, 2023 at 02:04:41AM +0000, SeongJae Park wrote:
> > Commit dd06e72e68bc ("Compiler Attributes: Add __counted_by macro")
> > added __counted_by() annotation. The underlying attribute for the
> > feature is still under development, but adopting it can improve the
> > readability of the code. Apply it to four dynamic arrays in DAMON sysfs
> > code.
> >
> > Signed-off-by: SeongJae Park <sj@kernel.org>
> > ---
> > mm/damon/sysfs.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/mm/damon/sysfs.c b/mm/damon/sysfs.c
> > index 808a8efe0523..36a176f38726 100644
> > --- a/mm/damon/sysfs.c
> > +++ b/mm/damon/sysfs.c
> > @@ -93,7 +93,7 @@ static const struct kobj_type damon_sysfs_region_ktype = {
> >
> > struct damon_sysfs_regions {
> > struct kobject kobj;
> > - struct damon_sysfs_region **regions_arr;
> > + struct damon_sysfs_region **regions_arr __counted_by(nr);
> > int nr;
> > };
>
> Unfortunately this isn't supported yet for non-flexible-array-members:
>
> mm/damon/sysfs.c:96:14: error: 'counted_by' attribute may not be specified for a non-array field
> 96 | struct damon_sysfs_region **regions_arr __counted_by(nr);
> | ^~~~~
>
> We'll have to wait a bit before we can add this patch.
Thank you for checking this and let me know. Ok, I will wait.
> Thank you for
> getting it ready, though!
Owing to your previous contributions. Thank you for helping me make DAMON code
better to read :)
> This support is next in line. :)
>
> The FAM support is likely ready to land, though[1]. I just tested it
> today.
>
> -Kees
>
> [1] https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628459.html
>
> --
> Kees Cook
>
Thanks,
SJ
prev parent reply other threads:[~2023-08-26 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 2:04 [RFC PATCH] mm/damon/sysfs: add __counted_by() annotation SeongJae Park
2023-08-25 21:32 ` Kees Cook
2023-08-26 0:54 ` SeongJae Park [this message]
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=20230826005447.109776-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qing.zhao@oracle.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.