Re: [PATCH] kref: oops on zero or negative refcount

2014-02-21 Thread Rafael Aquini
On Thu, Feb 20, 2014 at 01:17:44PM -0500, Rik van Riel wrote: > On 02/20/2014 01:14 PM, Dave Jones wrote: > > On Thu, Feb 20, 2014 at 06:44:59PM +0100, Mateusz Guzik wrote: > > > In use after free situations, it is possible for one thread to write to > > > memory that has just been reallocated

Re: [PATCH] kref: oops on zero or negative refcount

2014-02-21 Thread Mateusz Guzik
On Thu, Feb 20, 2014 at 01:14:40PM -0500, Dave Jones wrote: > On Thu, Feb 20, 2014 at 06:44:59PM +0100, Mateusz Guzik wrote: > > In use after free situations, it is possible for one thread to write to > > memory that has just been reallocated to a new user. This could open up > > potential

Re: [PATCH] kref: oops on zero or negative refcount

2014-02-21 Thread Mateusz Guzik
On Thu, Feb 20, 2014 at 01:14:40PM -0500, Dave Jones wrote: On Thu, Feb 20, 2014 at 06:44:59PM +0100, Mateusz Guzik wrote: In use after free situations, it is possible for one thread to write to memory that has just been reallocated to a new user. This could open up potential security

Re: [PATCH] kref: oops on zero or negative refcount

2014-02-21 Thread Rafael Aquini
On Thu, Feb 20, 2014 at 01:17:44PM -0500, Rik van Riel wrote: On 02/20/2014 01:14 PM, Dave Jones wrote: On Thu, Feb 20, 2014 at 06:44:59PM +0100, Mateusz Guzik wrote: In use after free situations, it is possible for one thread to write to memory that has just been reallocated to a new

Re: [PATCH] kref: oops on zero or negative refcount

2014-02-20 Thread Rik van Riel
On 02/20/2014 01:14 PM, Dave Jones wrote: > On Thu, Feb 20, 2014 at 06:44:59PM +0100, Mateusz Guzik wrote: > > In use after free situations, it is possible for one thread to write to > > memory that has just been reallocated to a new user. This could open up > > potential security issues. > >

Re: [PATCH] kref: oops on zero or negative refcount

2014-02-20 Thread Dave Jones
On Thu, Feb 20, 2014 at 06:44:59PM +0100, Mateusz Guzik wrote: > In use after free situations, it is possible for one thread to write to > memory that has just been reallocated to a new user. This could open up > potential security issues. > > diff --git a/include/linux/kref.h

[PATCH] kref: oops on zero or negative refcount

2014-02-20 Thread Mateusz Guzik
In use after free situations, it is possible for one thread to write to memory that has just been reallocated to a new user. This could open up potential security issues. Close off those potential security holes by terminating the current thread when kref encounters such a race condition or

[PATCH] kref: oops on zero or negative refcount

2014-02-20 Thread Mateusz Guzik
In use after free situations, it is possible for one thread to write to memory that has just been reallocated to a new user. This could open up potential security issues. Close off those potential security holes by terminating the current thread when kref encounters such a race condition or

Re: [PATCH] kref: oops on zero or negative refcount

2014-02-20 Thread Dave Jones
On Thu, Feb 20, 2014 at 06:44:59PM +0100, Mateusz Guzik wrote: In use after free situations, it is possible for one thread to write to memory that has just been reallocated to a new user. This could open up potential security issues. diff --git a/include/linux/kref.h

Re: [PATCH] kref: oops on zero or negative refcount

2014-02-20 Thread Rik van Riel
On 02/20/2014 01:14 PM, Dave Jones wrote: On Thu, Feb 20, 2014 at 06:44:59PM +0100, Mateusz Guzik wrote: In use after free situations, it is possible for one thread to write to memory that has just been reallocated to a new user. This could open up potential security issues. diff