[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180406121411.GJ4082@hirez.programming.kicks-ass.net>
Date: Fri, 6 Apr 2018 14:14:11 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
Omar Sandoval <osandov@...com>,
Dmitry Vyukov <dvyukov@...gle.com>,
syzbot
<bot+abdba5bc6de135d7622f00756da97998425b6de5@...kaller.appspotmail.com>,
Jens Axboe <axboe@...nel.dk>, Ming Lei <tom.leiming@...il.com>,
Hannes Reinecke <hare@...e.de>, shli@...com,
LKML <linux-kernel@...r.kernel.org>,
syzkaller-bugs@...glegroups.com, Ingo Molnar <mingo@...hat.com>,
linux-fsdevel@...r.kernel.org,
Nikanth Karthikesan <knikanth@...e.de>
Subject: Re: INFO: task hung in lo_ioctl
On Fri, Apr 06, 2018 at 09:04:18PM +0900, Tetsuo Handa wrote:
> + /* Temporary hack for handling lock imbalance. */
> + if (__mutex_owner(&lo->lo_ctl_mutex) == current)
> + mutex_unlock(&lo->lo_ctl_mutex);
ARGGH.. you didn't read the comment we put on that?
Powered by blists - more mailing lists