All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Paris <eparis@parisplace.org>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	James Morris <jmorris@namei.org>
Subject: Re: suspicious RCU usage in security/selinux/netport.c:127
Date: Mon, 07 Nov 2011 11:29:37 -0500	[thread overview]
Message-ID: <1320683377.10093.3.camel@localhost> (raw)
In-Reply-To: <20111107162531.GA28795@redhat.com>

On Mon, 2011-11-07 at 11:25 -0500, Dave Jones wrote:
> I think I reported this a while ago. Turns out it's still a problem.
> This patch I think made the warning go away, but it might be a bit too 'big hammer' ?

http://patchwork.ozlabs.org/patch/117821/

I thought it was already picked up.  I'll take care of it today.

-Eric


      reply	other threads:[~2011-11-07 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 16:25 suspicious RCU usage in security/selinux/netport.c:127 Dave Jones
2011-11-07 16:29 ` Eric Paris [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=1320683377.10093.3.camel@localhost \
    --to=eparis@parisplace.org \
    --cc=davej@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.