[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0390c62d-11d9-5d89-ad88-db38526b74e6@kernel.dk>
Date: Mon, 28 Nov 2022 12:08:47 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Bart Van Assche <bvanassche@....org>,
Waiman Long <longman@...hat.com>, Tejun Heo <tj@...nel.org>,
cgroups@...r.kernel.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, Ming Lei <ming.lei@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Michal Koutný <mkoutny@...e.com>,
Hillf Danton <hdanton@...a.com>, Yi Zhang <yi.zhang@...hat.com>
Subject: Re: [PATCH-block] blk-cgroup: Use css_tryget() in
blkcg_destroy_blkgs()
On 11/28/22 12:07 PM, Andy Shevchenko wrote:
> On Mon, Nov 28, 2022 at 12:00:55PM -0700, Jens Axboe wrote:
>> On 11/28/22 11:56 AM, Bart Van Assche wrote:
>>> On 11/27/22 19:30, Waiman Long wrote:
>>>> Fixes: 951d1e94801f ("blk-cgroup: Flush stats at blkgs destruction path")
>>>
>>> Has Jens' for-next branch perhaps been rebased? I see the following commit ID for that patch:
>>>
>>> dae590a6c96c ("blk-cgroup: Flush stats at blkgs destruction path")
>>
>> I don't know that sha is from, not from me. for-6.2/block has not been
>> rebased, for-next gets rebased whenever I need to do so as linux-next is
>> continually rebased anyway. But the sha for that commit would not change
>> as a result.
>>
>> I don't even have that sha in my tree, so...
>
> $ git tag --contains dae590a6c96c
> next-20221117
> next-20221118
> next-20221121
> next-20221122
> next-20221123
> next-20221124
> next-20221125
> next-20221128
That is the right sha, I'm talking about the fixes line in the
patch you're replying to:
Fixes: 951d1e94801f ("blk-cgroup: Flush stats at blkgs destruction path")
which is certainly not from my tree.
--
Jens Axboe
Powered by blists - more mailing lists