lkml.org 
[lkml]   [2015]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH v3] fs: record task name which froze superblock
From
On Mon, Mar 2, 2015 at 7:38 AM, Mateusz Guzik <mguzik@redhat.com> wrote:

> As explained below, this one task name is already very useful and likely
> covers majority of real life use cases.
>
> While working in support we were getting a lot of vmcores where hung task
> detector panicked the kernel because a lot of tasks were blocked
> in UN state trying to write to frozen filesystems. I presume OP has
> similar story.

Yes, the intended "use" case is 1 freezer which hopefully covers
majority of bug reports.

> Some back on forth commuication almost always revealed one process e.g.
> freezing stuff and then blocking itself trying to access it. While we
> could see it blocked, we had no presumptive evidence to pin freezing on
> it. A matching name, while still not 100% conclusive, would be ok enough
> to push the case forward and avoid a rountrip of systemap scripts
> showing freezer process tree.


\
 
 \ /
  Last update: 2015-03-04 16:21    [W:0.580 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site