Re: new warning on sysrq kernel crash trigger

2015-12-14 Thread Anirban Sinha
On Mon, 14 Dec 2015, Rik van Riel wrote: > On 12/14/2015 11:24 AM, Ani Sinha wrote: > > Rik, any comments? > > Another good option is to simply ignore this warning, or drop > the rcu_read_lock before doing the alt-syrsq-c action. > > After all, alt-sysrq-c is "crash the system, take a crash

Re: [PATCH 1/1] Fix 'sleeping function called from invalid context' warning in sysrq generated crash.

2015-12-20 Thread Anirban Sinha
On Fri, 18 Dec 2015, Paul E. McKenney wrote: > On Thu, Dec 17, 2015 at 05:15:10PM -0800, Ani Sinha wrote: > > Commit 984d74a72076a1 ("sysrq: rcu-ify __handle_sysrq") > > replaced spin_lock_irqsave() calls with > > rcu_read_lock() calls in sysrq. Since rcu_read_lock() does not > > disable

Re: new warning on sysrq kernel crash trigger

2015-12-14 Thread Anirban Sinha
On Mon, 14 Dec 2015, Rik van Riel wrote: > On 12/14/2015 11:24 AM, Ani Sinha wrote: > > Rik, any comments? > > Another good option is to simply ignore this warning, or drop > the rcu_read_lock before doing the alt-syrsq-c action. > > After all, alt-sysrq-c is "crash the system, take a crash

Re: [PATCH 1/1] Fix 'sleeping function called from invalid context' warning in sysrq generated crash.

2015-12-20 Thread Anirban Sinha
On Fri, 18 Dec 2015, Paul E. McKenney wrote: > On Thu, Dec 17, 2015 at 05:15:10PM -0800, Ani Sinha wrote: > > Commit 984d74a72076a1 ("sysrq: rcu-ify __handle_sysrq") > > replaced spin_lock_irqsave() calls with > > rcu_read_lock() calls in sysrq. Since rcu_read_lock() does not > > disable