RE: [PATCH] Validate pointer when copying mount namespace.

> Details, please. How do you reproduce that behaviour? > > I don't like that loop in its current form (it relies upon _not_ encountering > the > same ->mnt_root in the parts of tree we hadn't copied), but your change > doesn't make it any better. Seeing a reproducer would be useful in sorting

RE: [PATCH] move exit_task_work() before exit_fs().

> On 12/28/2014 07:58 PM, Ma, Xindong wrote: > >> > >> On 12/26, Leon Ma wrote: > >>> > >>> We encountered following panic. The scenario is the process is > >>> exiting and executing its task work. When closing dev node, the > >

RE: [PATCH] move exit_task_work() before exit_fs().

> On Fri, Dec 26, 2014 at 03:45:25PM +0800, Leon Ma wrote: > > We encountered following panic. The scenario is the process is exiting > > and executing its task work. When closing dev node, the driver > > triggers a firmware reload according to device status. Because task->fs is > set to NULL in ex

RE: [PATCH] move exit_task_work() before exit_fs().

> > On 12/26, Leon Ma wrote: > > > > We encountered following panic. The scenario is the process is exiting > > and executing its task work. When closing dev node, the driver > > triggers a firmware reload according to device status. Because task->fs is > set to NULL in exit_fs(), panic happens. >

RE: [PATCH] rmap: validate pointer in anon_vma_clone

Sorry, my fault. It's already validated in unlock_anon_vma_root(). BR Leon -Original Message- From: Ma, Xindong Sent: Wednesday, May 07, 2014 10:32 AM To: a...@linux-foundation.org; iamjoonsoo@lge.com; n-horigu...@ah.jp.nec.com; kirill.shute...@linux.intel.com; gorcu...@gmai

RE: [PATCH] hrtimer:do not start hrtimer on other cpu if it is the leftmost timer.

> -Original Message- > From: viresh.li...@gmail.com [mailto:viresh.li...@gmail.com] On Behalf Of > Viresh Kumar > Sent: Wednesday, April 30, 2014 6:36 PM > To: Ma, Xindong > Cc: Thomas Gleixner; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] hrtimer:do not start

RE: [PATCH] Fix race between oom kill and task exit

> From: Oleg Nesterov [mailto:o...@redhat.com] > Sent: Friday, November 29, 2013 2:39 AM > To: Michal Hocko > Cc: William Dauchy; Johannes Weiner; Ma, Xindong; > a...@linux-foundation.org; rient...@google.com; ru...@rustcorp.com.au; > linux...@kvack.org; linux-kernel@vger

[PATCH] Fix race between oom kill and task exit

From: Leon Ma Date: Thu, 28 Nov 2013 12:46:09 +0800 Subject: [PATCH] Fix race between oom kill and task exit There is a race between oom kill and task exit. Scenario is: TASK A TASK B TASK B is selected to oom kill in oom_kill_process() check PF_EXITING of TASK B

RE: Add memory barrier when waiting on futex

> -Original Message- > From: Peter Zijlstra [mailto:pet...@infradead.org] > Sent: Tuesday, November 26, 2013 4:26 PM > To: Ma, Xindong > Cc: sta...@vger.kernel.org; stable-comm...@vger.kernel.org; Wysocki, Rafael > J; ccr...@google.com; t...@linutronix.de; dvh...@lin

RE: Add memory barrier when waiting on futex

> -Original Message- > From: Peter Zijlstra [mailto:pet...@infradead.org] > Sent: Monday, November 25, 2013 10:40 PM > To: Ma, Xindong > Cc: sta...@vger.kernel.org; stable-comm...@vger.kernel.org; Wysocki, Rafael J; > ccr...@google.com; t...@linutronix.de; dvh...@lin

Add memory barrier when waiting on futex

We encountered following panic several times: [ 74.671982] BUG: unable to handle kernel NULL pointer dereference at 0008 [ 74.672101] IP: [] wake_futex+0x47/0x80 [ 74.672185] *pdpt = 10108001 *pde = [ 74.672278] Oops: 0002 [#1] PREEMPT SMP [ 74.672403] Modul

RE: [PATCH] LMK: Optimize lowmem_shrink

> -Original Message- > From: Dan Carpenter [mailto:dan.carpen...@oracle.com] > Sent: Tuesday, August 20, 2013 4:30 PM > To: Ma, Xindong > Cc: gre...@linuxfoundation.org; ccr...@android.com; > de...@driverdev.osuosl.org; linux-kernel@vger.kernel.org > Subject: Re: