[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOi1vP-TjjckKBNAiiTQDpgxVVKU0NFW0OrxADs6dz4p6p0yfQ@mail.gmail.com>
Date: Mon, 14 Aug 2023 15:17:52 +0200
From: Ilya Dryomov <idryomov@...il.com>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Dongsheng Yang <dongsheng.yang@...ystack.cn>, axboe@...nel.dk,
ceph-devel@...r.kernel.org, linux-block@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 5.15 28/31] rbd: make get_lock_owner_info() return
a single locker or NULL
On Sun, Aug 13, 2023 at 6:09 PM Sasha Levin <sashal@...nel.org> wrote:
>
> From: Ilya Dryomov <idryomov@...il.com>
>
> [ Upstream commit f38cb9d9c2045dad16eead4a2e1aedfddd94603b ]
>
> Make the "num_lockers can be only 0 or 1" assumption explicit and
> simplify the API by getting rid of output parameters in preparation
> for calling get_lock_owner_info() twice before blocklisting.
>
> Signed-off-by: Ilya Dryomov <idryomov@...il.com>
> Reviewed-by: Dongsheng Yang <dongsheng.yang@...ystack.cn>
> Signed-off-by: Sasha Levin <sashal@...nel.org>
Hi Sasha,
I think this patch, as well as "rbd: harden get_lock_owner_info()
a bit", have already been applied to 5.15, 6.1 and 6.4 by Greg. The
emails went out on Aug 1.
Thanks,
Ilya
Powered by blists - more mailing lists