From: Kees Cook <kees@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Q: arch/mips && __secure_computing(sd) with sd != NULL
Date: Sat, 18 Jan 2025 12:25:38 -0800 [thread overview]
Message-ID: <202501181223.1BA4E6A5@keescook> (raw)
In-Reply-To: <20250118162238.GA31924@redhat.com>
On Sat, Jan 18, 2025 at 05:22:38PM +0100, Oleg Nesterov wrote:
> Note that if we change arch/mips we can do more cleanups, in particular
> __secure_computing(sd) no longer needs the argument.
Yeah, seems like reasonable clean-up. The argument is a leftover from
x86 having sd pre-populated under certain paths.
--
Kees Cook
prev parent reply other threads:[~2025-01-18 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 16:22 Q: arch/mips && __secure_computing(sd) with sd != NULL Oleg Nesterov
2025-01-18 20:25 ` Kees Cook [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=202501181223.1BA4E6A5@keescook \
--to=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=tsbogend@alpha.franken.de \
--cc=wad@chromium.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