Davidlohr,
I read your commit 53dad6d3a8e5ac1af8bacc6ac2134ae1a8b085f1,
ipc: fix race with LSMs
The issue we hit without the above patch, the race may happen when
process call semctl with IPC_RMID just as Manfred Spraul mentioned:
Thread A:
IPC_RMID
-> freeary()
Davidlohr,
I read your commit 53dad6d3a8e5ac1af8bacc6ac2134ae1a8b085f1,
ipc: fix race with LSMs
The issue we hit without the above patch, the race may happen when
process call semctl with IPC_RMID just as Manfred Spraul mentioned:
Thread A:
IPC_RMID
- freeary()
On Fri, 2015-01-23 at 10:19 +0800, ethan zhao wrote:
> > If not, what kernel
> > version were you running when you triggered the bug?
> To be honest, a kernel from distro, but not released, but before we
> get it clear, we wouldn't public more.
Sheesh, could Oracle be any more (ridiculously)
Davidlohr,
On 2015/1/23 4:48, Davidlohr Bueso wrote:
On Thu, 2015-01-22 at 14:05 -0500, Stephen Smalley wrote:
On Wed, Jan 21, 2015 at 9:44 PM, Ethan Zhao wrote:
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
wrote:
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10
Stephen,
On 2015/1/23 3:05, Stephen Smalley wrote:
On Wed, Jan 21, 2015 at 9:44 PM, Ethan Zhao wrote:
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
wrote:
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley
wrote:
On 01/20/2015 04:18 AM, Ethan
Manfred,
On 2015/1/23 2:15, Manfred Spraul wrote:
On 01/22/2015 03:44 AM, Ethan Zhao wrote:
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
wrote:
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley
wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
On Thu, 2015-01-22 at 14:05 -0500, Stephen Smalley wrote:
> On Wed, Jan 21, 2015 at 9:44 PM, Ethan Zhao wrote:
> > On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
> > wrote:
> >> On 01/21/2015 04:53 AM, Ethan Zhao wrote:
> >>>
> >>> On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley
> >>> wrote:
On Wed, Jan 21, 2015 at 9:44 PM, Ethan Zhao wrote:
> On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
> wrote:
>> On 01/21/2015 04:53 AM, Ethan Zhao wrote:
>>>
>>> On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley
>>> wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
>
>
On 01/22/2015 03:44 AM, Ethan Zhao wrote:
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
wrote:
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley
wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
sys_semget()
->newary()
Manfred,
On 2015/1/23 2:15, Manfred Spraul wrote:
On 01/22/2015 03:44 AM, Ethan Zhao wrote:
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
manf...@colorfullife.com wrote:
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley s...@tycho.nsa.gov
wrote:
Stephen,
On 2015/1/23 3:05, Stephen Smalley wrote:
On Wed, Jan 21, 2015 at 9:44 PM, Ethan Zhao ethan.ker...@gmail.com wrote:
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
manf...@colorfullife.com wrote:
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM, Stephen
Davidlohr,
On 2015/1/23 4:48, Davidlohr Bueso wrote:
On Thu, 2015-01-22 at 14:05 -0500, Stephen Smalley wrote:
On Wed, Jan 21, 2015 at 9:44 PM, Ethan Zhao ethan.ker...@gmail.com wrote:
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
manf...@colorfullife.com wrote:
On 01/21/2015 04:53 AM,
On Fri, 2015-01-23 at 10:19 +0800, ethan zhao wrote:
If not, what kernel
version were you running when you triggered the bug?
To be honest, a kernel from distro, but not released, but before we
get it clear, we wouldn't public more.
Sheesh, could Oracle be any more (ridiculously)
On Wed, Jan 21, 2015 at 9:44 PM, Ethan Zhao ethan.ker...@gmail.com wrote:
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
manf...@colorfullife.com wrote:
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley s...@tycho.nsa.gov
wrote:
On 01/20/2015
On 01/22/2015 03:44 AM, Ethan Zhao wrote:
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
manf...@colorfullife.com wrote:
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley s...@tycho.nsa.gov
wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
On Thu, 2015-01-22 at 14:05 -0500, Stephen Smalley wrote:
On Wed, Jan 21, 2015 at 9:44 PM, Ethan Zhao ethan.ker...@gmail.com wrote:
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
manf...@colorfullife.com wrote:
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM,
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
wrote:
> On 01/21/2015 04:53 AM, Ethan Zhao wrote:
>>
>> On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley
>> wrote:
>>>
>>> On 01/20/2015 04:18 AM, Ethan Zhao wrote:
sys_semget()
->newary()
On Wed, Jan 21, 2015 at 1:30 PM, Manfred Spraul
manf...@colorfullife.com wrote:
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley s...@tycho.nsa.gov
wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
sys_semget()
-newary()
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
sys_semget()
->newary()
->security_sem_alloc()
->sem_alloc_security()
selinux_sem_alloc_security()
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley wrote:
> On 01/20/2015 04:18 AM, Ethan Zhao wrote:
>> A NULL pointer dereference was observed as following panic:
>>
>> BUG: unable to handle kernel NULL pointer dereference at (null)
>> IP: [] ipc_has_perm+0x4b/0x60
>> ...
>> Process opcmon (pid:
Stephen,
On 2015/1/21 2:49, Manfred Spraul wrote:
Hi,
On 01/20/2015 03:10 PM, Stephen Smalley wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
A NULL pointer dereference was observed as following panic:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: []
On 01/20/2015 04:06 PM, Eric Paris wrote:
> What kernel version was this? Didn't we have this problem and solve it
> upstream some time ago? IPC could be allocated with a valid security
> context, the ipc would be freed. the isec was free'd syncronously, but
> then the ipc could stick around
What kernel version was this? Didn't we have this problem and solve it
upstream some time ago? IPC could be allocated with a valid security
context, the ipc would be freed. the isec was free'd syncronously, but
then the ipc could stick around until some rcu period or some usage flag
got to 0,
On 01/20/2015 01:49 PM, Manfred Spraul wrote:
> Hi,
>
> On 01/20/2015 03:10 PM, Stephen Smalley wrote:
>> On 01/20/2015 04:18 AM, Ethan Zhao wrote:
>>> A NULL pointer dereference was observed as following panic:
>>>
>>> BUG: unable to handle kernel NULL pointer dereference at (null)
>>> IP: []
Hi,
On 01/20/2015 03:10 PM, Stephen Smalley wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
A NULL pointer dereference was observed as following panic:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [] ipc_has_perm+0x4b/0x60
...
Process opcmon (pid: 30712, threadinfo
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
> A NULL pointer dereference was observed as following panic:
>
> BUG: unable to handle kernel NULL pointer dereference at (null)
> IP: [] ipc_has_perm+0x4b/0x60
> ...
> Process opcmon (pid: 30712, threadinfo 880237f2a000,
> task 88022ac70e40)
>
A NULL pointer dereference was observed as following panic:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [] ipc_has_perm+0x4b/0x60
...
Process opcmon (pid: 30712, threadinfo 880237f2a000,
task 88022ac70e40)
Stack:
880237f2bc04 01020953 880237f2bce8
A NULL pointer dereference was observed as following panic:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [812735eb] ipc_has_perm+0x4b/0x60
...
Process opcmon (pid: 30712, threadinfo 880237f2a000,
task 88022ac70e40)
Stack:
880237f2bc04 01020953
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
A NULL pointer dereference was observed as following panic:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [812735eb] ipc_has_perm+0x4b/0x60
...
Process opcmon (pid: 30712, threadinfo 880237f2a000,
task
Hi,
On 01/20/2015 03:10 PM, Stephen Smalley wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
A NULL pointer dereference was observed as following panic:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [812735eb] ipc_has_perm+0x4b/0x60
...
Process opcmon (pid:
What kernel version was this? Didn't we have this problem and solve it
upstream some time ago? IPC could be allocated with a valid security
context, the ipc would be freed. the isec was free'd syncronously, but
then the ipc could stick around until some rcu period or some usage flag
got to 0,
On 01/20/2015 01:49 PM, Manfred Spraul wrote:
Hi,
On 01/20/2015 03:10 PM, Stephen Smalley wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
A NULL pointer dereference was observed as following panic:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [812735eb]
Stephen,
On 2015/1/21 2:49, Manfred Spraul wrote:
Hi,
On 01/20/2015 03:10 PM, Stephen Smalley wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
A NULL pointer dereference was observed as following panic:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [812735eb]
On 01/21/2015 04:53 AM, Ethan Zhao wrote:
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley s...@tycho.nsa.gov wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
sys_semget()
-newary()
-security_sem_alloc()
-sem_alloc_security()
On 01/20/2015 04:06 PM, Eric Paris wrote:
What kernel version was this? Didn't we have this problem and solve it
upstream some time ago? IPC could be allocated with a valid security
context, the ipc would be freed. the isec was free'd syncronously, but
then the ipc could stick around until
On Tue, Jan 20, 2015 at 10:10 PM, Stephen Smalley s...@tycho.nsa.gov wrote:
On 01/20/2015 04:18 AM, Ethan Zhao wrote:
A NULL pointer dereference was observed as following panic:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [812735eb] ipc_has_perm+0x4b/0x60
...
36 matches
Mail list logo