From: Alexander Grund <theflamefire89@gmail.com>
To: stable@vger.kernel.org
Cc: Alexander Grund <theflamefire89@gmail.com>
Subject: [PATCH 4.9 0/1] selinux: drop super_block backpointer from superblock_security_struct
Date: Mon, 8 Aug 2022 13:59:21 +0200 [thread overview]
Message-ID: <20220808115922.331003-1-theflamefire89@gmail.com> (raw)
This backports a commit from upstream which I would consider a cleanup
as well as a (minor) performance fix due to less memory being used and
avoiding an unneccessary pointer dereferencing, i.e. the change
from `sbsec->sb->s_root` to `sb->s_root`.
However as it changes the `superblock_security_struct` please check if
this violates any API/ABI stability requirements which I'm not aware of.
Ondrej Mosnacek (1):
selinux: drop super_block backpointer from superblock_security_struct
security/selinux/hooks.c | 5 ++---
security/selinux/include/objsec.h | 1 -
2 files changed, 2 insertions(+), 4 deletions(-)
--
2.25.1
next reply other threads:[~2022-08-08 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 11:59 Alexander Grund [this message]
2022-08-08 11:59 ` [PATCH 4.9 1/1] selinux: drop super_block backpointer from superblock_security_struct Alexander Grund
2022-08-08 13:28 ` [PATCH 4.9 0/1] " Greg KH
2022-08-11 9:46 ` Alexander Grund
2022-08-11 10:20 ` Greg KH
2022-08-11 10:21 ` Greg KH
2022-08-11 11:04 ` Alexander Grund
2022-08-11 13:46 ` Greg KH
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=20220808115922.331003-1-theflamefire89@gmail.com \
--to=theflamefire89@gmail.com \
--cc=stable@vger.kernel.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