mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Huang Ying <ying.huang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [userns] BUG: unable to handle kernel NULL pointer dereference at (null)
Date: Mon, 15 Dec 2014 11:31:10 -0600	[thread overview]
Message-ID: <87iohcx1k1.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <1418613661.5745.164.camel@intel.com> (Huang Ying's message of "Mon, 15 Dec 2014 11:21:01 +0800")

Huang Ying <ying.huang@intel.com> writes:

> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-testing
> commit bbea5f5532501fdd67f46442ba7b1122d7ff3123 
> ("userns: Add a knob to disable setgroups on a per user namespace basis")

Thank you.

I am quite puzzled by this failure.  There was an similar failure when
/proc/[pid]/setgroups was read (if I recall correctly).  I don't see how
that change could result at failures during open or failures during
boot.  I added a new file to proc which any reasonable system should
leave alone.  Are you by chance running trinity during boot?

If the reproducer gave me any clue about which file that was opened or
which code path this happened on I would be bery interested.  If for no
other reason that to confirm that I have fixed the issue.

I have rewritten the implementation of /proc/[pid]/setgroups so it is
simpler and more robust and does not have any errors I can detect.

Thank you very much for picking up my for-testing branch and beating up
on it.

Eric

  reply	other threads:[~2014-12-15 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15  3:21 Huang Ying
2014-12-15 17:31 ` Eric W. Biederman [this message]
2014-12-16  1:47   ` Huang Ying
2014-12-16  6:29     ` Fengguang Wu

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=87iohcx1k1.fsf@x220.int.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=ying.huang@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®