From: Casey Schaufler <casey@schaufler-ca.com>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ming Lei <ming.lei@canonical.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>,
Shuah Khan <shuahkhan@gmail.com>,
SE Linux <selinux@tycho.nsa.gov>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 4.2-rc1
Date: Wed, 08 Jul 2015 11:45:00 -0700 [thread overview]
Message-ID: <559D6FAC.4000606@schaufler-ca.com> (raw)
In-Reply-To: <CAFftDdr54GLdtZ+biC2hpbyjbHe+SKbLEbz0fbLVrK3sdBD+Vw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2753 bytes --]
On 7/8/2015 11:07 AM, William Roberts wrote:
>
>
> On Wed, Jul 8, 2015 at 10:47 AM, Casey Schaufler
> <casey@schaufler-ca.com <mailto:casey@schaufler-ca.com>> wrote:
>
> On 7/8/2015 10:29 AM, Linus Torvalds wrote:
> > On Wed, Jul 8, 2015 at 10:17 AM, Linus Torvalds
> > <torvalds@linux-foundation.org
> <mailto:torvalds@linux-foundation.org>> wrote:
> >> Decoding the "Code:" line shows that this is the "->fw_id"
> dereference in
> >>
> >> if (add_uevent_var(env, "FIRMWARE=%s",
> fw_priv->buf->fw_id))
> >> return -ENOMEM;
> >>
> >> and that "fw_priv->buf" pointer is NULL.
> >>
> >> However, I don't see anything that looks like it should have
> changed
> >> any of this since 4.1.
> > Looking at the otehr uses of "fw_priv->buf", they all check that
> > pointer for NULL. I see code like
> >
> > fw_buf = fw_priv->buf;
> > if (!fw_buf)
> > goto out;
> >
> > etc.
> >
> > Also, it looks like you need to hold the "fw_lock" to even look at
> > that pointer, since the buffer can get reallocated etc.
> >
> > So that uevent code really looks buggy. It just doesn't look like a
> > *new* bug to me. That code looks old, going back to 2012 and commit
> > 1244691c73b2.
>
> There have been SELinux changes to kernfs for 4.2. William,
> you might want to have a look here.
>
>
> My changes were never merged AFAIK and can tell. I was still working
> on this
> but we had some changes internally to SELinux that let us handle this,
> although
> we should correct this on kernfs at some point, its low priority for
> me now. Also
> commit fb029 makes kernfs_get_inode() public, so I need to rethink
> some things.
OK, false alarm. Not an SELinux issue. It might be useful
to see if the problem occurs with AppArmor off.
>
>
>
> >
> > Ming Lei?
> >
> > Linus
> > --
> > To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov <mailto:Selinux@tycho.nsa.gov>
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov
> <mailto:Selinux-leave@tycho.nsa.gov>.
> To get help, send an email containing "help" to
> Selinux-request@tycho.nsa.gov <mailto:Selinux-request@tycho.nsa.gov>.
>
>
>
>
> --
> Respectfully,
>
> William C Roberts
>
[-- Attachment #2: Type: text/html, Size: 5856 bytes --]
next prev parent reply other threads:[~2015-07-08 18:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 20:22 Linux 4.2-rc1 Linus Torvalds
2015-07-05 23:01 ` Guenter Roeck
2015-07-07 5:50 ` linux-next: stats (Was: Linux 4.2-rc1) Stephen Rothwell
2015-07-07 5:50 ` Stephen Rothwell
2015-07-07 12:56 ` Build failure on ARM64 for Linux 4.2-rc1 was: Linux 4.2-rc1 Mark Langsdorf
2015-07-09 16:46 ` Mark Langsdorf
2015-07-09 16:46 ` Mark Langsdorf
2015-07-09 16:59 ` Peter Zijlstra
2015-07-09 16:59 ` Peter Zijlstra
2015-07-13 16:55 ` Mark Langsdorf
2015-07-13 16:55 ` Mark Langsdorf
2015-07-08 16:32 ` Shuah Khan
2015-07-08 17:05 ` Casey Schaufler
2015-07-08 17:33 ` Shuah Khan
2015-07-08 17:55 ` Casey Schaufler
2015-07-08 17:55 ` Casey Schaufler
2015-07-08 17:17 ` Linus Torvalds
2015-07-08 17:29 ` Linus Torvalds
2015-07-08 17:47 ` Casey Schaufler
2015-07-08 18:03 ` Stephen Smalley
2015-07-08 18:07 ` William Roberts
2015-07-08 18:45 ` Casey Schaufler [this message]
2015-07-09 0:58 ` Ming Lei
2015-07-09 3:17 ` Linus Torvalds
2015-07-09 5:00 ` Ming Lei
2015-07-09 13:10 ` Shuah Khan
2015-07-09 13:44 ` Shuah Khan
2015-07-09 13:47 ` Shuah Khan
2015-07-09 14:45 ` Greg Kroah-Hartman
2015-07-09 17:40 ` Shuah Khan
2015-07-10 16:58 ` Shuah Khan
2015-07-10 17:11 ` Linus Torvalds
[not found] ` <55A03A33.8060405@osg.samsung.com>
[not found] ` <CA+55aFzDu9acMKHJFkxzg+1jeHNpGRhmM=pu2z-so5QYTMbvcA@mail.gmail.com>
2015-07-10 21:57 ` Shuah Khan
2015-07-10 22:36 ` Ming Lei
2015-07-08 19:00 ` Ingo Molnar
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=559D6FAC.4000606@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=bill.c.roberts@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=selinux@tycho.nsa.gov \
--cc=shuahkh@osg.samsung.com \
--cc=shuahkhan@gmail.com \
--cc=torvalds@linux-foundation.org \
/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.