All of lore.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Shuah Khan <shuahkh@osg.samsung.com>,
	Shuah Khan <shuahkhan@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SELinux <Selinux@tycho.nsa.gov>
Subject: Re: Linux 4.2-rc1
Date: Wed, 08 Jul 2015 10:55:05 -0700	[thread overview]
Message-ID: <559D63F9.2060109@schaufler-ca.com> (raw)
In-Reply-To: <559D5ED9.4040904@osg.samsung.com>

On 7/8/2015 10:33 AM, Shuah Khan wrote:
> On 07/08/2015 11:05 AM, Casey Schaufler wrote:
>> On 7/8/2015 9:32 AM, Shuah Khan wrote:
>>> On Sun, Jul 5, 2015 at 2:22 PM, Linus Torvalds
>>> <torvalds@linux-foundation.org> wrote:
>>>> It's Sunday, two weeks have passed, and the merge window is closed. I
>>>> just pushed out the tag to the git trees, and tar-balls and patches
>>>> should be mirroring out too.
>>>>
>>>> I thought this release would be one of the biggest ones ever, but it
>>>> turns out that it will depend on how you count. Just counting pure
>>>> commits, it is indeed one of the bigger rc1's in recent history, but
>>>> 3.10-rc1 was almost as big, and then the final 3.10 grew from that
>>>> more than most. I doubt we'll match the 3.10 release, since we have
>>>> been getting progressively better at *not* merging tons of stuff after
>>>> -rc1.
>>>>
>>>>
>>> I am seeing the following NULL pointer dereference on my test system:
>> Can I get your config file, please? I am particularly interested
>> in seeing your security settings.
>>
> Please see the attached config file.

SELinux is not configured, AppArmor is. It's possible that
the recent kernfs changes for SELinux affect this case, although
I couldn't say how from what I see.

>
> thanks,
> -- Shuah
>
>

WARNING: multiple messages have this Message-ID (diff)
From: Casey Schaufler <casey@schaufler-ca.com>
To: Shuah Khan <shuahkh@osg.samsung.com>,
	Shuah Khan <shuahkhan@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	william.c.roberts@intel.com, SELinux <Selinux@tycho.nsa.gov>
Subject: Re: Linux 4.2-rc1
Date: Wed, 08 Jul 2015 10:55:05 -0700	[thread overview]
Message-ID: <559D63F9.2060109@schaufler-ca.com> (raw)
In-Reply-To: <559D5ED9.4040904@osg.samsung.com>

On 7/8/2015 10:33 AM, Shuah Khan wrote:
> On 07/08/2015 11:05 AM, Casey Schaufler wrote:
>> On 7/8/2015 9:32 AM, Shuah Khan wrote:
>>> On Sun, Jul 5, 2015 at 2:22 PM, Linus Torvalds
>>> <torvalds@linux-foundation.org> wrote:
>>>> It's Sunday, two weeks have passed, and the merge window is closed. I
>>>> just pushed out the tag to the git trees, and tar-balls and patches
>>>> should be mirroring out too.
>>>>
>>>> I thought this release would be one of the biggest ones ever, but it
>>>> turns out that it will depend on how you count. Just counting pure
>>>> commits, it is indeed one of the bigger rc1's in recent history, but
>>>> 3.10-rc1 was almost as big, and then the final 3.10 grew from that
>>>> more than most. I doubt we'll match the 3.10 release, since we have
>>>> been getting progressively better at *not* merging tons of stuff after
>>>> -rc1.
>>>>
>>>>
>>> I am seeing the following NULL pointer dereference on my test system:
>> Can I get your config file, please? I am particularly interested
>> in seeing your security settings.
>>
> Please see the attached config file.

SELinux is not configured, AppArmor is. It's possible that
the recent kernfs changes for SELinux affect this case, although
I couldn't say how from what I see.

>
> thanks,
> -- Shuah
>
>


  reply	other threads:[~2015-07-08 17:55 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 [this message]
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
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=559D63F9.2060109@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=Selinux@tycho.nsa.gov \
    --cc=linux-kernel@vger.kernel.org \
    --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.