From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Kees Cook <keescook@chromium.org>,
Fengguang Wu <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: yama_ptrace_access_check(): possible recursive locking detected
Date: Wed, 15 Aug 2012 16:30:21 +0200 [thread overview]
Message-ID: <1345041021.31459.88.camel@twins> (raw)
In-Reply-To: <20120815130159.GA3221@redhat.com>
On Wed, 2012-08-15 at 15:01 +0200, Oleg Nesterov wrote:
> BTW, set_task_comm()->wmb() and memset() should die. There are
> not needed afaics, and the comment is misleading.
As long as we guarantee there's always a terminating '\0', now strlcpy()
doesn't pad the result, however if we initialize the ->comm to all 0s in
fork() or thereabouts, we should get this guarantee from the strlcpy()
since that will never replace the last byte with anything but 0.
That barrier is indeed completely pointless as there's no pairing
barrier anywhere.
next prev parent reply other threads:[~2012-08-15 14:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 13:47 yama_ptrace_access_check(): possible recursive locking detected Fengguang Wu
2012-07-26 15:41 ` Oleg Nesterov
2012-07-30 17:00 ` Kees Cook
2012-08-10 1:39 ` Kees Cook
2012-08-10 1:52 ` Fengguang Wu
2012-08-14 21:16 ` Kees Cook
2012-08-15 3:01 ` Fengguang Wu
2012-08-15 5:56 ` Kees Cook
2012-08-15 8:05 ` Peter Zijlstra
2012-08-15 13:01 ` Oleg Nesterov
2012-08-15 14:30 ` Peter Zijlstra [this message]
2012-08-15 17:56 ` Oleg Nesterov
2012-08-15 18:09 ` Kees Cook
2012-08-15 18:17 ` Oleg Nesterov
2012-08-15 18:30 ` Kees Cook
2012-08-15 18:44 ` Alan Cox
2012-08-15 18:43 ` 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=1345041021.31459.88.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.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