From: Pavel Emelyanov <xemul@parallels.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: "khlebnikov@openvz.org" <khlebnikov@openvz.org>,
"gorcunov@openvz.org" <gorcunov@openvz.org>,
Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: c/r: broken locking when executing map_files
Date: Wed, 02 May 2012 21:34:13 +0400 [thread overview]
Message-ID: <4FA17015.1000504@parallels.com> (raw)
In-Reply-To: <1335979380.10666.6.camel@lappy>
On 05/02/2012 09:23 PM, Sasha Levin wrote:
> Hi all,
>
> I've stumbled on several lockdep warnings when playing with the new files created under /proc/[pid], specifically 'map_files'.
>
> My theory is that files under map_files shouldn't be executable,
These are symlinks and x bit on them doesn't mean anything, but anyway, thanks for catching this.
> but since I'm not sure what the usermode code for
> c/r does exactly, I should probably confirm that first. If it's indeed the case, you can probably skip
> the rest of this mail.
>
> First, if I try to simply execute one of the mappings:
prev parent reply other threads:[~2012-05-02 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 17:23 c/r: broken locking when executing map_files Sasha Levin
2012-05-02 17:27 ` Cyrill Gorcunov
2012-05-03 17:31 ` Cyrill Gorcunov
2012-05-05 18:20 ` Vasiliy Kulikov
2012-05-05 18:53 ` Cyrill Gorcunov
2012-05-05 19:32 ` Cyrill Gorcunov
2012-05-06 20:21 ` Vasiliy Kulikov
2012-05-06 20:49 ` Cyrill Gorcunov
2012-05-11 17:56 ` Vasiliy Kulikov
2012-05-11 18:18 ` Cyrill Gorcunov
2012-05-02 17:34 ` Pavel Emelyanov [this message]
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=4FA17015.1000504@parallels.com \
--to=xemul@parallels.com \
--cc=davej@redhat.com \
--cc=gorcunov@openvz.org \
--cc=khlebnikov@openvz.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.