[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180406154343.GK4082@hirez.programming.kicks-ass.net>
Date: Fri, 6 Apr 2018 17:43:43 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc: viro@...iv.linux.org.uk, osandov@...com, dvyukov@...gle.com,
bot+abdba5bc6de135d7622f00756da97998425b6de5@...kaller.appspotmail.com,
axboe@...nel.dk, tom.leiming@...il.com, hare@...e.de, shli@...com,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
mingo@...hat.com, linux-fsdevel@...r.kernel.org, knikanth@...e.de
Subject: Re: INFO: task hung in lo_ioctl
On Fri, Apr 06, 2018 at 10:55:03PM +0900, Tetsuo Handa wrote:
> Peter Zijlstra wrote:
> > 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?
> >
>
> Commit 5b52330bbfe63b33 ("audit: fix auditd/kernel connection state tracking")
> is using __mutex_owner(). ;-)
That got removed and the warning added.
Powered by blists - more mailing lists