[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c432c9b0-cef1-123e-1fcd-0549b24e381e@huawei.com>
Date: Mon, 10 May 2021 09:29:08 +0800
From: Zhang Yi <yi.zhang@...wei.com>
To: Jens Axboe <axboe@...nel.dk>, <linux-fsdevel@...r.kernel.org>,
<linux-ext4@...r.kernel.org>, <linux-block@...r.kernel.org>,
<jack@...e.cz>
CC: <tytso@....edu>, <viro@...iv.linux.org.uk>, <hch@...radead.org>,
<mcgrof@...nel.org>, <keescook@...omium.org>, <yzaikin@...gle.com>
Subject: Re: [RFC PATCH 0/3] block_dump: remove block dump
On 2021/3/13 11:37, Jens Axboe wrote:
> On 3/12/21 8:01 PM, zhangyi (F) wrote:
>> Hi,
>>
>> block_dump is an old debugging interface and can be replaced by
>> tracepoints, and we also found a deadlock issue relate to it[1]. As Jan
>> suggested, this patch set delete the whole block_dump feature, we can
>> use tracepoints to get the similar information. If someone still using
>> this feature cannot switch to use tracepoints or any other suggestions,
>> please let us know.
>
> Totally agree, that's long overdue. The feature is no longer useful
> and has been deprecated by much better methods. Unless anyone objects,
> I'll queue this up for 5.13.
>
Hi, Jens. Could you please send these patches upstream ?
Thanks,
Yi.
Powered by blists - more mailing lists