Re: [PATCH] mm/memory-failure.c: send action optional signal to an arbitrary thread

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

 



On Wed, Dec 18, 2013 at 07:45:15AM +0100, Andi Kleen wrote:
> Date: Wed, 18 Dec 2013 07:45:15 +0100
> From: Andi Kleen <andi@xxxxxxxxxxxxxx>
> To: Kamil Iskra <iskra@xxxxxxxxxxx>
> Cc: Naoya Horiguchi <n-horiguchi@xxxxxxxxxxxxx>, linux-mm@xxxxxxxxx, Andi
>  Kleen <andi@xxxxxxxxxxxxxx>
> Subject: Re: [PATCH] mm/memory-failure.c: send action optional signal to an
>  arbitrary thread
> User-Agent: Mutt/1.5.20 (2009-06-14)
> 
> > I'm not sure if I understand.  "letting the main thread create a dedicated
> > thread for error handling" is exactly what I was trying to do -- the
> > problem is that SIGBUS(BUS_MCEERR_AO) signals are never sent to that
> > thread, which is contrary to common expectations.  
> 
Please add this section in your patch commit.

> 
> Yes handling AO errors like this was the intended way 
> 
> I thought I had tested it at some point and intentionally changed the 
> signal checking for this case (because normally SIGBUS cannot be
> blocked). Anyways if it doesn't work it's definitely a bug.
> 
> If you fix it please make sure to add the test case to mce-test.
> 

Yes, I think you can update your test case and add it in mce-test.
If you can't find latest mce-test git tree, here it is:
git://git.kernel.org/pub/scm/linux/kernel/git/gong.chen/mce-test.git

Attachment: signature.asc
Description: Digital signature


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