From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Grund <theflamefire89@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.9 0/1] selinux: drop super_block backpointer from superblock_security_struct
Date: Mon, 8 Aug 2022 15:28:29 +0200 [thread overview]
Message-ID: <YvEPfSBGdBV0ZohA@kroah.com> (raw)
In-Reply-To: <20220808115922.331003-1-theflamefire89@gmail.com>
On Mon, Aug 08, 2022 at 01:59:21PM +0200, Alexander Grund wrote:
> 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.
There is no internal stable API/ABI in the kernel, including in the
stable releases.
But, we only take patches that actually do something. This one doesn't
do anything at all, and has no measurable performance or bugfix that I
can determine at all.
So no need for it, sorry,
greg k-h
next prev parent reply other threads:[~2022-08-08 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 11:59 [PATCH 4.9 0/1] selinux: drop super_block backpointer from superblock_security_struct Alexander Grund
2022-08-08 11:59 ` [PATCH 4.9 1/1] " Alexander Grund
2022-08-08 13:28 ` Greg KH [this message]
2022-08-11 9:46 ` [PATCH 4.9 0/1] " 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=YvEPfSBGdBV0ZohA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=theflamefire89@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.