public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sat, 28 Sep 2024 07:54:57 -0600	[thread overview]
Message-ID: <877cavdgsu.fsf@trenco.lwn.net> (raw)
In-Reply-To: <0c4b443a-9c72-4800-97e8-a3816b6a9ae2@I-love.SAKURA.ne.jp>

Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> writes:

> The following changes since commit ada1986d07976d60bed5017aa38b7f7cf27883f7:
>
>   tomoyo: fallback to realpath if symlink's pathname does not exist (2024-09-25 22:30:59 +0900)
>
> are available in the Git repository at:
>
>   git://git.code.sf.net/p/tomoyo/tomoyo.git tags/tomoyo-pr-20240927
>
> for you to fetch changes up to ada1986d07976d60bed5017aa38b7f7cf27883f7:
>
>   tomoyo: fallback to realpath if symlink's pathname does not exist (2024-09-25 22:30:59 +0900)
> ----------------------------------------------------------------
> One bugfix patch, one preparation patch, and one conversion patch.

[...]

> I was delivering pure LKM version of TOMOYO (named AKARI) to users who
> cannot afford rebuilding their distro kernels with TOMOYO enabled. But
> since the LSM framework was converted to static calls, it became more
> difficult to deliver AKARI to such users. Therefore, I decided to update
> TOMOYO so that people can use mostly LKM version of TOMOYO with minimal
> burden for both distributors and users.

I must confess that this change confuses me a bit.  Loadable LSM modules
have been out of the picture for a long time, has that changed now?

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?

Thanks,

jon

  parent reply	other threads:[~2024-09-28 13:55 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 10:43 [GIT PULL] tomoyo update for v6.12 Tetsuo Handa
2024-09-27 20:00 ` pr-tracker-bot
2024-09-28 13:54 ` Jonathan Corbet [this message]
2024-09-28 15:32   ` Tetsuo Handa
2024-10-02 14:51     ` Jonathan Corbet
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=877cavdgsu.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