Re: INFO: task hung in lo_ioctl

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: INFO: task hung in lo_ioctl
From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Date: Fri, 6 Apr 2018 14:14:11 +0200
Cc: Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>, Omar Sandoval <osandov@xxxxxx>, Dmitry Vyukov <dvyukov@xxxxxxxxxx>, syzbot <bot+abdba5bc6de135d7622f00756da97998425b6de5@xxxxxxxxxxxxxxxxxxxxxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, Ming Lei <tom.leiming@xxxxxxxxx>, Hannes Reinecke <hare@xxxxxxx>, shli@xxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx>, syzkaller-bugs@xxxxxxxxxxxxxxxx, Ingo Molnar <mingo@xxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, Nikanth Karthikesan <knikanth@xxxxxxx>
In-reply-to: <468f7418-a02d-79cc-3d94-91bbe146567e@I-love.SAKURA.ne.jp>
User-agent: Mutt/1.9.3 (2018-01-21)

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?

Follow-Ups:
- Re: INFO: task hung in lo_ioctl
  - From: Tetsuo Handa

References:
- Re: INFO: task hung in lo_ioctl
  - From: Tetsuo Handa
- Re: INFO: task hung in lo_ioctl
  - From: Tetsuo Handa

Prev by Date: Re: INFO: task hung in lo_ioctl
Next by Date: Re: [PATCH 3/6] aio: refactor read/write iocb setup
Previous by thread: Re: INFO: task hung in lo_ioctl
Next by thread: Re: INFO: task hung in lo_ioctl
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux