From: Markus Elfring <Markus.Elfring@web.de>
To: Zhen Lei <thunder.leizhen@huawei.com>,
selinux@vger.kernel.org, Ondrej Mosnacek <omosnace@redhat.com>,
Paul Moore <paul@paul-moore.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jeff Vander Stoep <jeffv@google.com>,
Nick Kralevich <nnk@google.com>
Subject: Re: [PATCH] selinux: Fix potential counting error in avc_add_xperms_decision()
Date: Wed, 7 Aug 2024 14:06:29 +0200 [thread overview]
Message-ID: <ed7f98e2-596b-4e4a-bc8a-d88543eeaa6d@web.de> (raw)
In-Reply-To: <d3f95ed9-a8f2-aedb-9097-0ac420d5bfa1@huaweicloud.com>
>>>> The count increases only when a node is successfully added to
>>>> the linked list.
>>>
>>> 1. Please improve such a change description with an imperative wording.
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.11-rc2#n94
>> Ok, I'll try to improve it.
> I see this patch has been merged into selinux/stable-6.11.
Interesting …
> So I decided not to change it, and I re-examined it,
Further collateral evolution can become more helpful,
can't it?
> and it seems that there is no problem you mentioned.
There are obviously different preferences involved for patch review processes.
Regards,
Markus
next prev parent reply other threads:[~2024-08-07 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 6:51 [PATCH 1/1] selinux: Fix potential counting error in avc_add_xperms_decision() thunder.leizhen
2024-08-06 13:25 ` Stephen Smalley
2024-08-06 21:55 ` Paul Moore
2024-08-07 6:27 ` Leizhen (ThunderTown)
2024-08-06 16:30 ` [PATCH] " Markus Elfring
2024-08-07 9:16 ` Leizhen (ThunderTown)
2024-08-07 11:21 ` Leizhen (ThunderTown)
2024-08-07 12:06 ` Markus Elfring [this message]
2024-08-07 13:20 ` Leizhen (ThunderTown)
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=ed7f98e2-596b-4e4a-bc8a-d88543eeaa6d@web.de \
--to=markus.elfring@web.de \
--cc=jeffv@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nnk@google.com \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=thunder.leizhen@huawei.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.