Messages in this thread | | | Date | Sun, 24 Nov 2013 10:31:43 +0100 | From | Jan Kara <> | Subject | Re: recursive locking (coredump/vfs_write) |
| |
On Fri 22-11-13 23:52:18, Al Viro wrote: > On Fri, Nov 22, 2013 at 10:11:56PM +0100, Jan Kara wrote: > > Hi, > > > > On Wed 13-11-13 16:11:47, Dave Jones wrote: > > > here's another one.. > > > > > > > > > ============================================= > > > [ INFO: possible recursive locking detected ] > > > 3.12.0+ #2 Not tainted > > > --------------------------------------------- > > > trinity-child3/13302 is trying to acquire lock: > > > (sb_writers#5){.+.+.+}, at: [<ffffffff811b7013>] vfs_write+0x173/0x1f0 > > > > > > but task is already holding lock: > > > (sb_writers#5){.+.+.+}, at: [<ffffffff8122006d>] do_coredump+0xf1d/0x1070 > > Thanks for report. Attached patch should fix this. Al, can you please > > merge it? > > No. It's already fixed in mainline by commit 52da40. Ah, right. After pull I can see that change. Sorry for the noise.
Honza -- Jan Kara <jack@suse.cz> SUSE Labs, CR
| |