From: Oleg Nesterov <oleg@redhat.com>
To: Pavel Emelyanov <xemul@parallels.com>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
Alexey Dobriyan <adobriyan@gmail.com>,
James Bottomley <jbottomley@parallels.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Matthew Helsley <matt.helsley@gmail.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: + fs-epoll-add-procfs-fdinfo-helper.patch added to -mm tree
Date: Tue, 13 Nov 2012 15:50:50 +0100 [thread overview]
Message-ID: <20121113145050.GA13691@redhat.com> (raw)
> struct signalfd_ctx {
> + seqcount_t cnt;
> sigset_t sigmask;
> };
> ...
> @@ -278,7 +302,9 @@ SYSCALL_DEFINE4(signalfd4, int, ufd, sig
> return -EINVAL;
> }
> spin_lock_irq(¤t->sighand->siglock);
> + write_seqcount_begin(&ctx->cnt);
> ctx->sigmask = sigmask;
> + write_seqcount_end(&ctx->cnt);
> spin_unlock_irq(¤t->sighand->siglock);
This doesn't look right.
The problem is, the current locking is broken, ->siglock can not serialize
->sigmask changes. Just suppose the the child inherits sigfd from parent
and they both do sys_signalfd4() at the same time.
Nothing really bad can happen, that is why nobody bothers to fix this.
But this patch makes the thing worse, write_seqcount_begin() must be
serialized correctly.
Oleg.
next reply other threads:[~2012-11-13 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 14:50 Oleg Nesterov [this message]
2012-11-13 15:53 ` + fs-epoll-add-procfs-fdinfo-helper.patch added to -mm tree Cyrill Gorcunov
2012-11-13 16:20 ` Cyrill Gorcunov
2012-11-13 16:49 ` Oleg Nesterov
2012-11-13 17:01 ` Cyrill Gorcunov
2012-11-13 17:14 ` Cyrill Gorcunov
2012-11-13 17:47 ` Oleg Nesterov
2012-11-13 17:53 ` Cyrill Gorcunov
2012-11-13 17:55 ` Oleg Nesterov
-- strict thread matches above, loose matches on Subject: below --
2012-11-13 1:06 akpm
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=20121113145050.GA13691@redhat.com \
--to=oleg@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bfields@fieldses.org \
--cc=gorcunov@openvz.org \
--cc=jbottomley@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.helsley@gmail.com \
--cc=viro@ZenIV.linux.org.uk \
--cc=xemul@parallels.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 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.