From: Roland McGrath <roland@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: David Howells <dhowells@redhat.com>,
jmorris@namei.org, chrisw@sous-sol.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, eparis@redhat.com,
sds@tycho.nsa.gov, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 1/2] CRED: Rename cred_exec_mutex to reflect that it's a guard against ptrace
Date: Sun, 10 May 2009 16:29:38 -0700 (PDT) [thread overview]
Message-ID: <20090510232938.A62E1FC35D@magilla.sf.frob.com> (raw)
In-Reply-To: Oleg Nesterov's message of Saturday, 9 May 2009 20:59:06 +0200 <20090509185906.GB10396@redhat.com>
> Hmm. Ingo's "rename ptrace_may_access => ptrace_access_check" conflicts
> with my patch too.
Andrew seemed to want a different name choice too, so that will have to be
resolved before we worry about patch conflicts.
> Andrew, Roland, I guess I should re-send
>
> ptrace-ptrace_attach-check-pf_kthread-exit_state-instead-of-mm.patch
> ptrace-cleanup-check-set-of-pt_ptraced-during-attach.patch
> ptrace-do-not-use-task_lock-for-attach.patch
>
> patches?
I guess so too. Your series of changes is more substantial and potentially
controversial or problematic than the various renamings, so I think it
makes sense to settle and merge the renamings first.
Thanks,
Roland
next prev parent reply other threads:[~2009-05-10 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 12:55 David Howells
2009-05-08 12:55 ` [PATCH 2/2] CRED: Guard the setprocattr security hook " David Howells
2009-05-10 22:37 ` James Morris
2009-05-09 18:59 ` [PATCH 1/2] CRED: Rename cred_exec_mutex to reflect that it's a guard " Oleg Nesterov
2009-05-10 23:29 ` Roland McGrath [this message]
2009-05-11 11:33 ` Ingo Molnar
2009-05-10 22:37 ` James Morris
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=20090510232938.A62E1FC35D@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=dhowells@redhat.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=sds@tycho.nsa.gov \
/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®