[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o9j8axyc.fsf@xmission.com>
Date: Wed, 28 Mar 2018 12:53:31 -0500
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Nagarathnam Muthusamy <nagarathnam.muthusamy@...cle.com>
Cc: kernel test robot <fengguang.wu@...el.com>, LKP <lkp@...org>,
linux-kernel@...r.kernel.org, wfg@...ux.intel.com
Subject: Re: 98f929b1bd ("ipc/shm: Fix shmctl(..., IPC_STAT, ...) between .."): Oops: 0000 [#1]
Nagarathnam Muthusamy <nagarathnam.muthusamy@...cle.com> writes:
> Hi Eric,
>
> From
> https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/tree/ipc/shm.c?h=for-next
>
> It looks like if the following condition in Line 616 succeeds
>
> error = PTR_ERR(file);
> if (IS_ERR(file))
> goto no_file;
>
> we get to no_file with garbage value in shm_cprid. An attempt to
> put_pid on this garbage value might be causing panic.
>
> We could initialize shm_cprid to NULL as soon as it was created.
Yes. I misread the kvmalloc as a kvzalloc.
I am planning on placing the pid freeing under the no_id label
instead of the no_file label. Which should also avoid the issue.
It is a rare enough issue an incremental patch should be fine.
Eric
Powered by blists - more mailing lists