Re: [PATCH v1 1/1] aoe: avoid potential deadlock at set_capacity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Maksim Kiselev <bigunclemax@xxxxxxxxx>
Subject: Re: [PATCH v1 1/1] aoe: avoid potential deadlock at set_capacity
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 24 Jan 2024 01:18:13 -0800
Cc: Justin Sanders <justin@xxxxxxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, linux-block@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20240124072436.3745720-2-bigunclemax@gmail.com>
References: <20240124072436.3745720-1-bigunclemax@gmail.com> <20240124072436.3745720-2-bigunclemax@gmail.com>

Looks good:

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

Just curious: what is your rason for using aeo over nbd?

Follow-Ups:
- Re: [PATCH v1 1/1] aoe: avoid potential deadlock at set_capacity
  - From: Maxim Kiselev

References:
- [PATCH v1 0/1] aoe: possible interrupt unsafe locking scenario
  - From: Maksim Kiselev
- [PATCH v1 1/1] aoe: avoid potential deadlock at set_capacity
  - From: Maksim Kiselev

Prev by Date: Re: [PATCH v6 1/4] block: Make fair tag sharing configurable
Next by Date: Re: [PATCHv2 1/1] block: introduce content activity based ioprio
Previous by thread: [PATCH v1 1/1] aoe: avoid potential deadlock at set_capacity
Next by thread: Re: [PATCH v1 1/1] aoe: avoid potential deadlock at set_capacity
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux