Re: [PATCH v4] apparmor: Use a memory pool instead per-CPU caches

[PATCH 1/2] apparmor: Use a memory pool instead per-CPU caches · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-04-05
[PATCH 2/2] apparmor: Switch to GFP_KERNEL where possible · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-04-05
Re: [PATCH 2/2] apparmor: Switch to GFP_KERNEL where possible · John Johansen <john.johansen@canonical.com> · 2019-05-07
Re: [PATCH 1/2] apparmor: Use a memory pool instead per-CPU caches · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-04-15
Re: [PATCH 1/2] apparmor: Use a memory pool instead per-CPU caches · John Johansen <john.johansen@canonical.com> · 2019-04-28
Re: [PATCH 1/2] apparmor: Use a memory pool instead per-CPU caches · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-04-30
Re: [PATCH 1/2] apparmor: Use a memory pool instead per-CPU caches · John Johansen <john.johansen@canonical.com> · 2019-05-01
Re: [PATCH 1/2] apparmor: Use a memory pool instead per-CPU caches · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-05-02
Re: [PATCH 1/2] apparmor: Use a memory pool instead per-CPU caches · Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> · 2019-05-02
Re: [PATCH 1/2] apparmor: Use a memory pool instead per-CPU caches · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-05-02
Re: [PATCH 1/2] apparmor: Use a memory pool instead per-CPU caches · Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> · 2019-05-02
[PATCH v2] apparmor: Use a memory pool instead per-CPU caches · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-05-03
[PATCH v3] apparmor: Use a memory pool instead per-CPU caches · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-05-03
Re: [PATCH v3] apparmor: Use a memory pool instead per-CPU caches · Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> · 2019-05-03
[PATCH v4] apparmor: Use a memory pool instead per-CPU caches · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-05-03
Re: [PATCH v4] apparmor: Use a memory pool instead per-CPU caches · John Johansen <john.johansen@canonical.com> · 2019-05-07
Re: [PATCH v4] apparmor: Use a memory pool instead per-CPU caches · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-10-02
Re: [PATCH v4] apparmor: Use a memory pool instead per-CPU caches · John Johansen <john.johansen@canonical.com> · 2019-10-02
Re: [PATCH v4] apparmor: Use a memory pool instead per-CPU caches · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2019-10-02
Re: [PATCH 1/2] apparmor: Use a memory pool instead per-CPU caches · John Johansen <john.johansen@canonical.com> · 2019-05-02

From: John Johansen <john.johansen@canonical.com>
Date: 2019-10-02 15:48:11

On 10/2/19 1:59 AM, Sebastian Andrzej Siewior wrote:

On 2019-05-07 12:57:04 [-0700], John Johansen wrote:

quoted

I am going to pull this into my tree and let it sit in linux-next
for a cycle so we can get better testing on this before it is pushed
out

We talked about this during the merge window for 5.2-rc1. These changes
were not part of 5.4-rc1. Was there a fallout, anything I can help with?

I have some patches that are required on top of them. I didn't chase down
all the issues/get the patches done until after -rc6 so everything waits
for the next cycle. I am going to update apparmor-next with the new stack
this week.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help