From: John Johansen <john.johansen@canonical.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Neeraj Upadhyay <Neeraj.Upadhyay@amd.com>,
paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
"Shukla, Santosh" <Santosh.Shukla@amd.com>,
"Narayan, Ananth" <Ananth.Narayan@amd.com>,
raghavendra.kodsarathimmappa@amd.com, koverstreet@google.com,
paulmck@kernel.org, boqun.feng@gmail.com,
vinicius.gomes@intel.com
Subject: Re: [RFC 0/9] Nginx refcount scalability issue with Apparmor enabled and potential solutions
Date: Fri, 8 Mar 2024 12:09:48 -0800 [thread overview]
Message-ID: <3b880c7c-0d19-4bb6-9f0f-fb69047f41cd@canonical.com> (raw)
In-Reply-To: <CAGudoHFkDmGuPQDLf6rfiJxUdqFxjeeM-_9rFCApSrBYzfyRmA@mail.gmail.com>
On 3/2/24 02:23, Mateusz Guzik wrote:
> On 2/9/24, John Johansen <john.johansen@canonical.com> wrote:
>> On 2/6/24 20:40, Neeraj Upadhyay wrote:
>>> Gentle ping.
>>>
>>> John,
>>>
>>> Could you please confirm that:
>>>
>>> a. The AppArmor refcount usage described in the RFC is correct?
>>> b. Approach taken to fix the scalability issue is valid/correct?
>>>
>>
>> Hi Neeraj,
>>
>> I know your patchset has been waiting on review for a long time.
>> Unfortunately I have been very, very busy lately. I will try to
>> get to it this weekend, but I can't promise that I will be able
>> to get the review fully done.
>>
>
> Gentle prod.
>
> Any chances of this getting reviewed in the foreseeable future? Would
> be a real bummer if the patchset fell through the cracks.
>
yes, sorry I have been unavailable for the last couple of weeks. I am
now back, I have a rather large backlog to try catching up on but this
is has an entry on the list.
next prev parent reply other threads:[~2024-03-08 20:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 11:11 [RFC 0/9] Nginx refcount scalability issue with Apparmor enabled and potential solutions Neeraj Upadhyay
2024-01-10 11:18 ` [RFC 1/9] doc: Add document for apparmor refcount management Neeraj Upadhyay
2024-01-10 11:18 ` [RFC 2/9] apparmor: Switch labels to percpu refcount in atomic mode Neeraj Upadhyay
2024-01-10 11:18 ` [RFC 3/9] apparmor: Switch unconfined namespaces refcount to percpu mode Neeraj Upadhyay
2024-01-10 11:18 ` [RFC 4/9] apparmor: Add infrastructure to reclaim percpu labels Neeraj Upadhyay
2024-01-10 11:18 ` [RFC 5/9] apparmor: Switch intree labels to percpu mode Neeraj Upadhyay
2024-01-10 11:18 ` [RFC 6/9] apparmor: Initial prototype for optimizing ref switch Neeraj Upadhyay
2024-01-10 11:18 ` [RFC 7/9] percpu-rcuref: Add basic infrastructure Neeraj Upadhyay
2024-01-10 11:18 ` [RFC 8/9] apparmor: Switch labels to percpu rcurefcount in unmanaged mode Neeraj Upadhyay
2024-01-10 11:18 ` [RFC 9/9] apparmor: Switch unconfined and in tree labels to managed ref mode Neeraj Upadhyay
2024-02-07 4:40 ` [RFC 0/9] Nginx refcount scalability issue with Apparmor enabled and potential solutions Neeraj Upadhyay
2024-02-09 17:33 ` John Johansen
2024-03-02 10:23 ` Mateusz Guzik
2024-03-08 20:09 ` John Johansen [this message]
2024-05-24 21:10 ` Mateusz Guzik
2024-05-24 21:51 ` John Johansen
2024-05-28 13:29 ` Mateusz Guzik
2024-05-29 0:37 ` John Johansen
2024-05-29 9:38 ` Mateusz Guzik
2024-05-30 4:19 ` Neeraj Upadhyay
2024-05-30 5:59 ` John Johansen
2024-05-30 9:47 ` Mateusz Guzik
2024-05-31 0:17 ` John Johansen
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=3b880c7c-0d19-4bb6-9f0f-fb69047f41cd@canonical.com \
--to=john.johansen@canonical.com \
--cc=Ananth.Narayan@amd.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=Santosh.Shukla@amd.com \
--cc=boqun.feng@gmail.com \
--cc=gautham.shenoy@amd.com \
--cc=jmorris@namei.org \
--cc=koverstreet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=paul@paul-moore.com \
--cc=paulmck@kernel.org \
--cc=raghavendra.kodsarathimmappa@amd.com \
--cc=serge@hallyn.com \
--cc=vinicius.gomes@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).