[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fdefd516-c469-7874-31cf-bc60596e777c@redhat.com>
Date: Wed, 11 Dec 2019 20:18:55 +0100
From: David Hildenbrand <david@...hat.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Matthew Wilcox <willy@...radead.org>,
"yukuai (C)" <yukuai3@...wei.com>, gregkh@...uxfoundation.org,
rafael@...nel.org, rostedt@...dmis.org, oleg@...hat.com,
mchehab+samsung@...nel.org, corbet@....net, tytso@....edu,
jmorris@...ei.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, zhengbin13@...wei.com,
yi.zhang@...wei.com, chenxiang66@...ilicon.com, xiexiuqi@...wei.com
Subject: Re: [PATCH V2 1/3] dcache: add a new enum type for
'dentry_d_lock_class'
On 11.12.19 19:46, Al Viro wrote:
> On Wed, Dec 11, 2019 at 04:55:56PM +0100, David Hildenbrand wrote:
>
> [snip]
>
>> The patch in linux-next
>>
>> commit 653f0d05be0948e7610bb786e6570bb6c48a4e75 (HEAD, refs/bisect/bad)
>
> ... is no longer there. commit a3d1e7eb5abe3aa1095bc75d1a6760d3809bd672
> is; could you check if it fixes your reproducer?
>
desktop: ~/git/linux memory_holes $ git fetch next
desktop: ~/git/linux memory_holes $ git show
a3d1e7eb5abe3aa1095bc75d1a6760d3809bd672
fatal: bad object a3d1e7eb5abe3aa1095bc75d1a6760d3809bd672
I'll go hunt for that commit :) ... guess it will show up in -next soon.
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists