From: Pratyush Yadav <pratyush@kernel.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
David Hildenbrand <david@kernel.org>,
Daniel Verkamp <dverkamp@chromium.org>,
Jeff Xu <jeffxu@google.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Hugh Dickins <hughd@google.com>,
linux-man@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] man/man2const/F_{ADD,GET}_SEALS.2const: document F_SEAL_EXEC
Date: Fri, 29 May 2026 15:28:25 +0200 [thread overview]
Message-ID: <2vxzjysm2vly.fsf@kernel.org> (raw)
In-Reply-To: <ahmPrpekhMwD-8fD@devuan> (Alejandro Colomar's message of "Fri, 29 May 2026 15:12:39 +0200")
On Fri, May 29 2026, Alejandro Colomar wrote:
> Hi Pratyush,
>
> On 2026-05-29T14:40:44+0200, Pratyush Yadav wrote:
>> From: "Pratyush Yadav (Google)" <pratyush@kernel.org>
>>
>> F_SEAL_EXEC was added in Linux v6.3. It seals the exec bits of the
>> memfd. Document it.
>>
>> Signed-off-by: Pratyush Yadav (Google) <pratyush@kernel.org>
>> ---
>>
>> Notes:
>> I discovered this was missing when working on [0]. I had to look at the
>> code to figure out how it was supposed to behave.
>>
>> Disclaimer: I used help from Gemini to write this patch, mainly because
>> I don't know the man page syntax. If the man-pages project also uses the
>> AI-assisted tags as Linux, feel free to add:
>>
>> Assisted-by: Gemini:gemini-3.1-pro
>
> $ head -n13 CONTRIBUTING.d/ai
> Name
> AI - artificial intelligence policy
>
> Description
> It is expressly forbidden to contribute to this project any
> content that has been created or derived with the assistance of
> AI tools.
>
> This includes AI assistive tools used in the contributing
> process, even if such tools do not directly generate the
> contributed code but are used to derive the contribution. For
> example, AI linters, AI static analyzers, and AI tools that
> summarize input are forbidden.
Oh, well, that's a bummer :-(. I do understand the concerns, especially
the copyright one, but unfortunately I'm bummed about redoing an
otherwise perfectly good patch. These AI tools do make this sort of
stuff a tad bit easier.
Anyway, as you say, the amount of text is relatively small so I can redo
it by hand.
>
> If you only used it for formatting, and the text is entirely yours, I
> guess you'll be able to write it again from scratch easily (it's not
> a lot of text, anyway).
>
> To proceed clean, you should remove the patch entirely, and write it
> again from scratch, only looking at surrounding code and other pages,
> but not looking at the contaminated patch.
>
> If you have any doubts about the man(7) language, I can help, or even
> fix things for you (as long as it's reasonably easy to do so).
>
> Thanks!
>
>
> Have a lovely day!
> Alex
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-05-29 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 12:40 [PATCH] man/man2const/F_{ADD,GET}_SEALS.2const: document F_SEAL_EXEC Pratyush Yadav
2026-05-29 13:12 ` Alejandro Colomar
2026-05-29 13:28 ` Pratyush Yadav [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=2vxzjysm2vly.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=alx@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dverkamp@chromium.org \
--cc=hughd@google.com \
--cc=jeffxu@google.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.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.