From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] userns: Add forward declaration of struct seq_file in user_namespace.h
Date: Fri, 30 May 2025 08:27:14 -0500 [thread overview]
Message-ID: <87ldqegrf1.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <aDlty06JvlGwTfKk@gondor.apana.org.au> (Herbert Xu's message of "Fri, 30 May 2025 16:35:23 +0800")
Herbert Xu <herbert@gondor.apana.org.au> writes:
> Add forward declaration of struct seq_file before using it in
> function prototype.
I don't see anything wrong with doing that.
However:
> Fixes: 9cc46516ddf4 ("userns: Add a knob to disable setgroups on a per
> user namespace basis")
That description seems to be lacking something. The code as has been
fine since 2014 and there is no conditional compilation involved.
Did some other change cause a declaration of seq_file not to be present?
Did user_namespace.h get included somewhere new and that new location
doesn't wind up declaring seq_file?
Especially since fixes tags tend to get code back ported I would
appreciate a bit more context on why this is a problem in 2025 when
it hasn't been a problem for the last decade.
Thank you,
Eric Biederman
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>
> diff --git a/include/linux/user_namespace.h b/include/linux/user_namespace.h
> index a0bb6d012137..5c7aa940b1aa 100644
> --- a/include/linux/user_namespace.h
> +++ b/include/linux/user_namespace.h
> @@ -16,6 +16,8 @@
> #define UID_GID_MAP_MAX_BASE_EXTENTS 5
> #define UID_GID_MAP_MAX_EXTENTS 340
>
> +struct seq_file;
> +
> struct uid_gid_extent {
> u32 first;
> u32 lower_first;
next prev parent reply other threads:[~2025-05-30 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 8:35 Herbert Xu
2025-05-30 13:27 ` Eric W. Biederman [this message]
2025-05-31 7:08 ` Herbert Xu
2025-05-31 11:07 ` Eric W. Biederman
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=87ldqegrf1.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
/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®