mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: Pavel Emelyanov <xemul@parallels.com>,
	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>,
	linux-kernel@vger.kernel.org
Subject: Re: + fs-epoll-add-procfs-fdinfo-helper.patch added to -mm tree
Date: Tue, 13 Nov 2012 17:49:51 +0100	[thread overview]
Message-ID: <20121113164951.GA18665@redhat.com> (raw)
In-Reply-To: <20121113162056.GK7808@moon>

On 11/13, Cyrill Gorcunov wrote:
>
>  struct signalfd_ctx {
> +	rwlock_t lock;
>  	sigset_t sigmask;

Oh, I don't think.

rwlock_t is horrible in general, and what it can buy for signalfd?
A plain spinlock would be better. Or seqlock_t.

Whatever you do, you are trying to introduce the lock which should
serialize the access to ->sigmask correctly. In this case I think
you should split this change into 2 patches. The first one should
fix the locking, imo. sys_signalfd4() should not use ->siglock at
all, and the users which take ->siglock to read ->sigmask should be
updated.

Or,

> +#ifdef CONFIG_PROC_FS
> +static int signalfd_show_fdinfo(struct seq_file *m, struct file *f)
> +{
> +	struct signalfd_ctx *ctx = f->private_data;
> +	sigset_t sigmask;
> +
> +	read_lock(&ctx->lock);
> +	sigmask = ctx->sigmask;
> +	read_unlock(&ctx->lock);

Just read ctx->sigmask lockless. Do we really care if show_fdinfo()
reads the value "in between" ?

Oleg.


  reply	other threads:[~2012-11-13 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 14:50 Oleg Nesterov
2012-11-13 15:53 ` Cyrill Gorcunov
2012-11-13 16:20   ` Cyrill Gorcunov
2012-11-13 16:49     ` Oleg Nesterov [this message]
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

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=20121113164951.GA18665@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome