[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+aTQ1j-oPG2_2gAOLCasMqT95qWOYTR1Yx4nr05M-ZnMA@mail.gmail.com>
Date: Tue, 7 Nov 2017 09:31:30 +0100
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Byungchul Park <byungchul.park@....com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Al Viro <viro@...iv.linux.org.uk>, Jan Kara <jack@...e.cz>,
syzbot
<bot+f99f3a0db9007f4f4e32db54229a240c4fe57c15@...kaller.appspotmail.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>, jlayton@...hat.com,
LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
npiggin@...il.com, rgoldwyn@...e.com, ross.zwisler@...ux.intel.com,
syzkaller-bugs@...glegroups.com, Ingo Molnar <mingo@...hat.com>,
kernel-team@....com
Subject: Re: possible deadlock in generic_file_write_iter
On Tue, Nov 7, 2017 at 9:30 AM, Byungchul Park <byungchul.park@....com> wrote:
> 11/7/2017 5:11 PM에 Peter Zijlstra 이(가) 쓴 글:
>
>> On Tue, Nov 07, 2017 at 09:54:42AM +0900, Byungchul Park wrote:
>>>>
>>>> The best I could come up with is something like the below; its not
>>>> at all pretty and I could see people objecting; least of all myself for
>>>> the __complete() thing, but I ran out of creative naming juice.
>>>
>>>
>>> Patches assigning a lock_class per gendisk were already applied in tip.
>>> I believe that solves this.
>>>
>>> e319e1fbd9d42420ab6eec0bfd75eb9ad7ca63b1
>>> block, locking/lockdep: Assign a lock_class per gendisk used for
>>> wait_for_completion()
>>>
>>> I think the following proposal makes kernel too hacky.
>>
>>
>> Ah, I tough this was with those included...
>
>
> Please CC me for issues wrt. crossrelease.
Hi Byungchul,
Whom are you asking? And what is crossrelease?
Powered by blists - more mailing lists