From: Paul Moore <paul@paul-moore.com>
To: mthode@mthode.org
Cc: Richard Yao <ryao@gentoo.org>,
selinux@tycho.nsa.gov, behlendorf@llnl.gov,
Brian Behlendorf <behlendorf1@llnl.gov>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: file access causes a kernel bug
Date: Thu, 30 Jan 2014 14:19:47 -0500 [thread overview]
Message-ID: <1897429.yoaRn36u2g@sifl> (raw)
In-Reply-To: <52EA8D4D.5080707@mthode.org>
On Thursday, January 30, 2014 11:35:09 AM Matthew Thode wrote:
> On 01/30/2014 11:19 AM, Paul Moore wrote:
> > On Thursday, January 30, 2014 11:07:30 AM Matthew Thode wrote:
> >> On 01/30/2014 10:41 AM, Stephen Smalley wrote:
> >>> Try the attached patch.
> >>
> >> Confirmed that this fixes it :D thanks a ton for this.
> >
> > Queued up in my stable branch, I'll send a pull request to James once -rc1
> > is released.
> >
> > Thanks guys.
>
> Any chance for backport to 3.13?
It will go off to the stable list and ultimately it will be up to the stable
kernel maintainers. However, considering the size and nature of the patch I
see no reason why it would not be applied to a 3.13.X release in the future.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2014-01-30 19:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 8:04 file access causes a kernel bug Matthew Thode
2014-01-29 8:11 ` Matthew Thode
2014-01-29 13:55 ` Paul Moore
2014-01-29 14:07 ` Stephen Smalley
2014-01-29 14:17 ` Stephen Smalley
2014-01-29 16:58 ` Matthew Thode
2014-01-29 21:36 ` Stephen Smalley
2014-01-29 22:35 ` Brian Behlendorf
2014-01-29 22:39 ` Richard Yao
2014-01-30 8:20 ` Matthew Thode
2014-01-30 13:43 ` Stephen Smalley
2014-01-30 15:38 ` Matthew Thode
2014-01-30 15:45 ` Stephen Smalley
2014-01-30 15:51 ` Matthew Thode
2014-01-30 16:41 ` Stephen Smalley
2014-01-30 17:07 ` Matthew Thode
2014-01-30 17:19 ` Paul Moore
2014-01-30 17:35 ` Matthew Thode
2014-01-30 19:19 ` Paul Moore [this message]
2014-02-04 3:41 ` Per Nystrom
2014-02-05 17:15 ` Matthew Thode
2014-02-05 17:18 ` Paul Moore
2014-01-30 17:27 ` Richard Yao
2014-01-30 18:10 ` Stephen Smalley
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=1897429.yoaRn36u2g@sifl \
--to=paul@paul-moore.com \
--cc=behlendorf1@llnl.gov \
--cc=behlendorf@llnl.gov \
--cc=mthode@mthode.org \
--cc=ryao@gentoo.org \
--cc=sds@tycho.nsa.gov \
--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.