From: James Morris <jmorris@namei.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
James Morris <james.l.morris@oracle.com>,
John Johansen <john.johansen@canonical.com>,
"Serge E. Hallyn" <serge.hallyn@ubuntu.com>,
Eric Paris <eparis@redhat.com>,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] Yama: remove locking from delete path
Date: Tue, 20 Nov 2012 14:46:35 +1100 (EST) [thread overview]
Message-ID: <alpine.LRH.2.02.1211201445410.1844@tundra.namei.org> (raw)
In-Reply-To: <CAGXu5jJe0-nu2e+QAGeYGiufumXd7JR-z_JCt+OCHVKhmnvN1Q@mail.gmail.com>
On Mon, 19 Nov 2012, Kees Cook wrote:
> On Mon, Nov 19, 2012 at 6:23 PM, James Morris <jmorris@namei.org> wrote:
> > On Mon, 19 Nov 2012, Kees Cook wrote:
> >
> >> Instead of locking the list during a delete, mark entries as invalid
> >> and trigger a workqueue to clean them up. This lets us easily handle
> >> task_free from interrupt context.
> >>
> >> Cc: Sasha Levin <sasha.levin@oracle.com>
> >> Signed-off-by: Kees Cook <keescook@chromium.org>
> >
> > This doesn't apply cleanly to my -next branch.
>
> Did you already apply this from last week?
> https://lkml.org/lkml/2012/11/13/808
Nope.
>
> > Kees: can you think about using git to push changes to me for Yama?
>
> If this pace of changes keeps up, sure thing.
In any case, please check that your patches apply cleanly to my -next
branch.
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2012-11-20 3:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 23:34 Kees Cook
2012-11-20 2:23 ` James Morris
2012-11-20 3:01 ` Kees Cook
2012-11-20 3:46 ` James Morris [this message]
2012-11-20 3:45 ` Serge Hallyn
2012-11-20 6:14 ` Kees Cook
2012-11-20 6:53 ` Kees Cook
2012-11-20 12:24 ` Tetsuo Handa
2012-11-20 16:07 ` Kees Cook
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=alpine.LRH.2.02.1211201445410.1844@tundra.namei.org \
--to=jmorris@namei.org \
--cc=eparis@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge.hallyn@ubuntu.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
all inboxes | Powered by JetHome®