Hello, Jan. On Tue, Mar 19, 2013 at 8:46 AM, Jan Kara <[email protected]> wrote: > Well, but what you often get is just output of sysrq-w, or sysrq-t, or > splat from scheduler about stuck task. You often don't have the comfort of > tracing... Can't we somehow change 'comm' of the task when it starts > processing work of some bdi?
You sure can but I'd prefer not to do that. If you wanna do it properly, you have to grab task lock every time a work item starts execution. I'm not sure how beneficial having the block device identifier would be. Backtrace would be there the same. Is identifying the block device that important? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
