From: Jonathan Corbet <corbet@lwn.net>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Paul Moore <paul@paul-moore.com>
Subject: Re: [GIT PULL] tomoyo update for v6.12
Date: Wed, 02 Oct 2024 08:51:02 -0600 [thread overview]
Message-ID: <87ikua4kyx.fsf@trenco.lwn.net> (raw)
In-Reply-To: <7dce903c-2f76-43b2-bb6f-808cb50d0696@I-love.SAKURA.ne.jp>
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> writes:
>> Even stranger, to me at least, is the backdoor symbol-export mechanism.
>> That seems like ... not the way we do things. Was the need for this so
>> urgent that you couldn't try to get those symbols exported properly?
>
> Yes. This is a chicken-and-egg problem. Symbols not used by in-tree kernel
> code cannot be justified for export, but I can't prove that loadable LSM
> can work unless I export symbols.
Honestly, this is the part that concerns me the most. The normal way to
deal with this is to create a series with both the exports and the users
so that they can be evaluated together. Instead you seem to have
created just the sort of shim layer that we have not allowed in other
settings, then pushed it upstream without review.
What will you do if, for any reason, one or more of those symbols cannot
be exported? Either you will circumvent that decision indefinitely with
your "temporary hack", or you will remove the hack, regressing things
for your users. Neither seems like a good outcome; that is why we
normally want to actually review things like symbol exports before
pushing them into the mainline.
jon
next prev parent reply other threads:[~2024-10-02 14:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 10:43 Tetsuo Handa
2024-09-27 20:00 ` pr-tracker-bot
2024-09-28 13:54 ` Jonathan Corbet
2024-09-28 15:32 ` Tetsuo Handa
2024-10-02 14:51 ` Jonathan Corbet [this message]
2024-10-03 7:50 ` Christoph Hellwig
2024-10-01 14:00 ` Paul Moore
2024-10-01 16:36 ` Linus Torvalds
2024-10-01 18:22 ` Paul Moore
2024-10-02 3:31 ` Tetsuo Handa
2024-10-02 14:01 ` Paul Moore
2024-10-02 23:09 ` Tetsuo Handa
2024-10-02 23:50 ` Tetsuo Handa
2024-10-03 2:45 ` John Johansen
2024-10-03 4:26 ` Tetsuo Handa
2024-10-03 5:35 ` John Johansen
2024-10-03 6:16 ` Tetsuo Handa
2024-10-03 12:59 ` Tetsuo Handa
2024-10-05 4:06 ` John Johansen
2024-10-05 3:59 ` John Johansen
2024-10-03 15:39 ` Dr. Greg
2024-10-05 4:24 ` John Johansen
2024-10-03 2:33 ` John Johansen
2024-10-02 10:38 ` Dr. Greg
2024-10-02 14:35 ` Paul Moore
2024-10-03 2:24 ` John Johansen
2024-10-08 11:14 ` Dr. Greg
2024-10-08 18:25 ` Casey Schaufler
2024-10-11 17:06 ` Dr. Greg
2024-10-11 18:01 ` Casey Schaufler
2024-10-03 2:27 ` John Johansen
2024-10-03 15:43 ` Dr. Greg
2024-10-05 4:37 ` John Johansen
2024-10-04 18:40 ` Dr. Greg
2024-10-04 18:58 ` Paul Moore
2024-10-05 2:33 ` Dr. Greg
2024-10-05 16:21 ` Paul Moore
2024-10-07 11:21 ` Dr. Greg
2024-10-07 13:28 ` Paul Moore
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=87ikua4kyx.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=torvalds@linux-foundation.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®