From: ally heev <allyheev@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>,
Christian Brauner <brauner@kernel.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH v2] overlayfs: fix uninitialized pointers with free attribute
Date: Wed, 19 Nov 2025 12:43:18 +0530 [thread overview]
Message-ID: <0c11915eda500f12ed56dd77875c96f53c496fbf.camel@gmail.com> (raw)
In-Reply-To: <CAOQ4uxgLYwpwyoecazZovz490i3bPYSGRsi74NZQE4N4NT5q_A@mail.gmail.com>
On Sat, 2025-11-15 at 14:59 +0100, Amir Goldstein wrote:
[...]
> Christian,
>
> Mind picking this one?
>
> Thanks,
> Amir.
>
We might want to wait. There's an ongoing discussion going on about
this rule
https://lore.kernel.org/lkml/58fd478f408a34b578ee8d949c5c4b4da4d4f41d.camel@HansenPartnership.com/.
Mostly likely, I might have to revert to v1 of this patch
> > fs/overlayfs/params.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/overlayfs/params.c b/fs/overlayfs/params.c
> > index 63b7346c5ee1c127a9c33b12c3704aa035ff88cf..37086f73ac3ecfcd1c09ae6eccbb69723006e031 100644
> > --- a/fs/overlayfs/params.c
> > +++ b/fs/overlayfs/params.c
> > @@ -448,7 +448,7 @@ static int ovl_parse_layer(struct fs_context *fc, struct fs_parameter *param,
> > err = ovl_do_parse_layer(fc, param->string, &layer_path, layer);
> > break;
> > case fs_value_is_file: {
> > - char *buf __free(kfree);
> > + char *buf __free(kfree) = NULL;
> > char *layer_name;
> >
> > buf = kmalloc(PATH_MAX, GFP_KERNEL_ACCOUNT);
> >
> > ---
> > base-commit: c9cfc122f03711a5124b4aafab3211cf4d35a2ac
> > change-id: 20251105-aheev-uninitialized-free-attr-overlayfs-6873964429e0
> >
> > Best regards,
> > --
> > Ally Heev <allyheev@gmail.com>
> >
Thanks,
Ally
next prev parent reply other threads:[~2025-11-19 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 13:41 [PATCH v2] overlayfs: fix uninitialized pointers with free attribute Ally Heev
2025-11-15 13:59 ` Amir Goldstein
2025-11-19 7:13 ` ally heev [this message]
2025-11-21 7:44 ` ally heev
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=0c11915eda500f12ed56dd77875c96f53c496fbf.camel@gmail.com \
--to=allyheev@gmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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;
as well as URLs for NNTP newsgroup(s).