From: David Howells <dhowells@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org,
selinux@tycho.nsa.gov, Paul Moore <paul@paul-moore.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH] SELinux: Fix RCU deref check warning in sel_netport_insert()
Date: Fri, 16 Dec 2011 13:13:58 +0000 [thread overview]
Message-ID: <11853.1324041238@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1112141011380.20373@tundra.namei.org>
James Morris <jmorris@namei.org> wrote:
> On Tue, 13 Dec 2011, David Howells wrote:
>
> > Fix the following bug in sel_netport_insert() where rcu_dereference() should
> > be rcu_dereference_protected() as sel_netport_lock is held.
> >
>
> Which kernel should this go to?
I'm applying it to Linus's git head. It probably needs to go to some stable
trees too, I suppose.
David
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2011-12-16 13:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 14:49 [PATCH] SELinux: Fix RCU deref check warning in sel_netport_insert() David Howells
2011-12-13 23:11 ` James Morris
2011-12-16 13:13 ` David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-03 13:58 David Howells
2011-10-03 13:58 ` David Howells
2011-10-03 21:30 ` Paul Moore
2011-10-03 21:30 ` Paul Moore
2011-10-03 23:07 ` David Howells
2011-10-03 23:07 ` David Howells
2011-10-04 0:06 ` Paul Moore
2011-10-04 0:06 ` Paul Moore
2011-10-04 4:22 ` Eric Dumazet
2011-10-05 11:07 ` David Howells
2011-10-05 11:07 ` David Howells
2011-10-05 13:32 ` David Howells
2011-10-05 13:32 ` David Howells
2011-10-06 22:51 ` Paul Moore
2011-10-06 22:51 ` Paul Moore
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=11853.1324041238@redhat.com \
--to=dhowells@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@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.