Re: [PATCH] mm,hwpoison: non-current task should be checked early_kill for force_early

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 15 Jan 2021 09:49:24 +0100
Oscar Salvador <osalvador@xxxxxxx> wrote:

> I am having a hard time trying to grasp what are you trying to achieve here.
> Could you elaborate some more? Ideally stating what is the problem you are
> fixing here.
> 
Sorry for confusion, example: there are four process A,B,C,D,which map the same file into
there process space, which set there PF_MCE_KILL_EARLY flag to TRUE, if process A trigger one
UE with  MF_ACTION_REQUIRED set, in current code, only process A will be killed, B,C,D remain
alive, but for the PF_MCE_KILL_EARLY we set, we want B,C,D also be killed.
this is what I want to fix.

> If it is not set by the caller of memory_failure, we still want to check the
> task/threads' MCE policy to check whether PF_MCE_KILL_EARLY it was set with
> prctl, right?
>
Yes, right! 

> That makes sense to me.
> 
> So, back to your change, if force_early was set, but the main task does not
> match, you still want to check whether any thread belonging to the main task
> has the policy set?
> 
Yes.

-- 
Best Regards!

Aili Yao




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux