RE: [PATCH 0/3] HWPOISON: improve memory error handling for multithread process
> I'm not sure that "[PATCH 3/3] mm/memory-failure.c: support dedicated > thread to handle SIGBUS(BUS_MCEERR_AO)" is a -stable thing? That's a > feature addition more than a bugfix? No - the old behavior was crazy - someone with a multithreaded process might well expect that if they call prctl(PF_MCE_EARLY) in just one thread, then that thread would see the SIGBUS with si_code = BUS_MCEERR_A0 - even if that thread wasn't the main thread for the process. Perhaps the description for the commit should better reflect that? -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/3] HWPOISON: improve memory error handling for multithread process
On Fri, 30 May 2014 14:24:52 -0400 Naoya Horiguchi wrote: > On Fri, May 30, 2014 at 05:25:39PM +, Luck, Tony wrote: > > > This patchset is the summary of recent discussion about memory error > > > handling > > > on multithread application. Patch 1 and 2 is for action required errors, > > > and > > > patch 3 is for action optional errors. > > > > Naoya, > > > > You suggested early in the discussion (when there were just two patches) > > that > > they deserved a "Cc: sta...@vger.kernel.org". I agreed, and still think > > the same > > way. > > Correct. AR error handling was added in v3.2-rc5, so adding > "Cc: sta...@vger.kernel.org # v3.2+" is fine. I'm not sure that "[PATCH 3/3] mm/memory-failure.c: support dedicated thread to handle SIGBUS(BUS_MCEERR_AO)" is a -stable thing? That's a feature addition more than a bugfix? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [PATCH 0/3] HWPOISON: improve memory error handling for multithread process
> This patchset is the summary of recent discussion about memory error handling > on multithread application. Patch 1 and 2 is for action required errors, and > patch 3 is for action optional errors. Naoya, You suggested early in the discussion (when there were just two patches) that they deserved a "Cc: sta...@vger.kernel.org". I agreed, and still think the same way. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/3] HWPOISON: improve memory error handling for multithread process
This patchset is the summary of recent discussion about memory error handling on multithread application. Patch 1 and 2 is for action required errors, and patch 3 is for action optional errors. This patchset is based on mmotm-2014-05-21-16-57. Patches are also available on the following tree/branch. g...@github.com:Naoya-Horiguchi/linux.git hwpoison/master Thanks, Naoya Horiguchi --- Summary: Naoya Horiguchi (1): mm/memory-failure.c: support dedicated thread to handle SIGBUS(BUS_MCEERR_AO) Tony Luck (2): memory-failure: Send right signal code to correct thread memory-failure: Don't let collect_procs() skip over processes for MF_ACTION_REQUIRED Documentation/vm/hwpoison.txt | 5 +++ mm/memory-failure.c | 75 ++- 2 files changed, 58 insertions(+), 22 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
