Re: [PATCH 1/2] locktorture: Fix deboosting nil ptr dereferencing

2016-03-09 Thread Paul E. McKenney
On Wed, Mar 09, 2016 at 11:05:01AM -0800, Davidlohr Bueso wrote: > On Wed, 09 Mar 2016, Paul E. McKenney wrote: > >Queued for 4.7, thank you!!! > > > >(If you need it earlier, please let me know.) > > Thanks, Paul. Could we have them for 4.6 at least? Both are small and > rather trivial but fix

Re: [PATCH 1/2] locktorture: Fix deboosting nil ptr dereferencing

2016-03-09 Thread Paul E. McKenney
On Wed, Mar 09, 2016 at 11:05:01AM -0800, Davidlohr Bueso wrote: > On Wed, 09 Mar 2016, Paul E. McKenney wrote: > >Queued for 4.7, thank you!!! > > > >(If you need it earlier, please let me know.) > > Thanks, Paul. Could we have them for 4.6 at least? Both are small and > rather trivial but fix

Re: [PATCH 1/2] locktorture: Fix deboosting nil ptr dereferencing

2016-03-09 Thread Davidlohr Bueso
On Wed, 09 Mar 2016, Paul E. McKenney wrote: Queued for 4.7, thank you!!! (If you need it earlier, please let me know.) Thanks, Paul. Could we have them for 4.6 at least? Both are small and rather trivial but fix really annoying problems. ie, I've now come to see that the rtmutex torturing is

Re: [PATCH 1/2] locktorture: Fix deboosting nil ptr dereferencing

2016-03-09 Thread Davidlohr Bueso
On Wed, 09 Mar 2016, Paul E. McKenney wrote: Queued for 4.7, thank you!!! (If you need it earlier, please let me know.) Thanks, Paul. Could we have them for 4.6 at least? Both are small and rather trivial but fix really annoying problems. ie, I've now come to see that the rtmutex torturing is

Re: [PATCH 1/2] locktorture: Fix deboosting nil ptr dereferencing

2016-03-09 Thread Paul E. McKenney
On Tue, Mar 08, 2016 at 11:08:05PM -0800, Davidlohr Bueso wrote: > For the case of rtmutex torturing we will randomly call into the > boost() handler, including upon module exiting when the tasks are > deboosted before stopping. In such cases the task may or may not have > already been boosted,

Re: [PATCH 1/2] locktorture: Fix deboosting nil ptr dereferencing

2016-03-09 Thread Paul E. McKenney
On Tue, Mar 08, 2016 at 11:08:05PM -0800, Davidlohr Bueso wrote: > For the case of rtmutex torturing we will randomly call into the > boost() handler, including upon module exiting when the tasks are > deboosted before stopping. In such cases the task may or may not have > already been boosted,

[PATCH 1/2] locktorture: Fix deboosting nil ptr dereferencing

2016-03-08 Thread Davidlohr Bueso
For the case of rtmutex torturing we will randomly call into the boost() handler, including upon module exiting when the tasks are deboosted before stopping. In such cases the task may or may not have already been boosted, and therefore the NULL being explicitly passed can occur anywhere.

[PATCH 1/2] locktorture: Fix deboosting nil ptr dereferencing

2016-03-08 Thread Davidlohr Bueso
For the case of rtmutex torturing we will randomly call into the boost() handler, including upon module exiting when the tasks are deboosted before stopping. In such cases the task may or may not have already been boosted, and therefore the NULL being explicitly passed can occur anywhere.