From: Alexander Grund <theflamefire89@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.9 0/1] selinux: drop super_block backpointer from superblock_security_struct
Date: Thu, 11 Aug 2022 11:46:09 +0200 [thread overview]
Message-ID: <7769a909-9054-3215-dd3e-00bfb822d003@gmail.com> (raw)
In-Reply-To: <YvEPfSBGdBV0ZohA@kroah.com>
On 08.08.22 15:28, Greg KH wrote:
> 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.
Isn't "doing less" also worth the patch?
I mean this patch removes a superflous pointer of the superblock struct
making the kernel use less memory.
It also saves a code line and operation during init and removes the
(somewhat hidden in syntax) superflous indirect access (and hence memory read)
of a pointer already available (likely even in a register) during get/set_mnt_opts.
Of course the effect here is small but I think cleanups are always good to avoid
a "death by a thousand cuts" scenario, i.e. that even small things help.
But of course you may disagree, just wanted to provide my reasoning especially
as you wrote earlier that deleting code is always good and I thought this
patch fits that.
Thanks,
Alex
next prev parent reply other threads:[~2022-08-11 9:46 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 ` [PATCH 4.9 0/1] " Greg KH
2022-08-11 9:46 ` Alexander Grund [this message]
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=7769a909-9054-3215-dd3e-00bfb822d003@gmail.com \
--to=theflamefire89@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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