From: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
To: Paul Moore <paul@paul-moore.com>
Cc: "James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Christian Brauner" <brauner@kernel.org>,
"Dave Chinner" <dchinner@redhat.com>,
"Casey Schaufler" <casey@schaufler-ca.com>,
"John Johansen" <john.johansen@canonical.com>,
"Micah Morton" <mortonm@chromium.org>,
"Günther Noack" <gnoack3000@gmail.com>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Mickaël Salaün" <mic@digikod.net>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
"Vivek Goyal" <vgoyal@redhat.com>
Subject: Re: [PATCH] security, lsm: security_old_inode_init_security() Handle multi LSM registration
Date: Sun, 2 Apr 2023 22:03:11 +0200 [thread overview]
Message-ID: <ZCnff6gUjU89zfAb@valentin-vidic.from.hr> (raw)
In-Reply-To: <CAHC9VhT6VXwybScqsnYHHtbHNPoWMVQJzQ7VAccm2MWZEz+5Dw@mail.gmail.com>
On Sun, Apr 02, 2023 at 11:14:33AM -0400, Paul Moore wrote:
> If you have the time, could you try a patch we have queued up in the
> lsm/next branch? We are in the process of removing
> security_old_inode_init_security() and transitioning all the callers
> over to security_inode_init_security(), and I believe the ocfs2 patch
> for this should solve the problem you are seeing, can you test it on
> your system and let us know?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git/patch/?id=de3004c874e740304cc4f4a83d6200acb511bbda
Great, thanks for the pointer. This patch also works for me as I don't
see the crash anymore. Can it also be included in the 6.1 LTS kernel
since this is were I first noticed the problem?
--
Valentin
next prev parent reply other threads:[~2023-04-02 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 21:41 Valentin Vidic
2023-04-02 15:14 ` Paul Moore
2023-04-02 20:03 ` Valentin Vidić [this message]
2023-04-03 19:28 ` Paul Moore
2023-04-05 15:30 ` Valentin Vidić
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=ZCnff6gUjU89zfAb@valentin-vidic.from.hr \
--to=vvidic@valentin-vidic.from.hr \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=dchinner@redhat.com \
--cc=gnoack3000@gmail.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=mortonm@chromium.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=vgoyal@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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®