[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH for-4.19] hotplug: Restore block-tap phy compatibility (again)
- To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>, <oleksii.kurochko@xxxxxxxxx>
- From: Jason Andryuk <jason.andryuk@xxxxxxx>
- Date: Tue, 23 Jul 2024 14:05:45 -0400
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=citrix.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none (0)
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=g+DT8OJiqnlgbG5hYSt88xcANE9o/290vg2yp65LNGM=; b=omlYVKvvbiSUTg74QE0H2qFHoH3C/FPYHyQJtKCEACK1QaUTqzuKbJKM9++PqFnvbsiDyG8PcDdaN2TMLN8WsW9L/ZwGZaiIfSuO6EpKlBroXdcwnM3X4I40ROejg5/rOBXEMlR+W6el5RVv9kL8XQfQgB6Er1zm6BQmlh4V4OSXcVyiHkBkLfskGvNFjI1QkgRjJl5yLJTNF6cT2YW1YAfQcYfPpXypm1U5vFPjvne1nMuNB7l1JhP6UTOiVpBWkEfxCj/yLh1X71+7rZCZt99sL2rmIzno5qa8AKCMdRcCjvArdK+R//SK/YDrS8Xhk8egzAYk2qHqn17WeApgfQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=hus+TonpatTjnTwXA9HoYFSpDBOCXGTCKRR8UbG0x+7LoTNWThOsfUM1kronEfI0sttOm84mlpXX8EmenqMREfTZyZt184R/5Mg/bgI68D9xY5Atr+uiA4wmNBs7ecYB7Aha3zdtCeSad2VDO7t0CCGJTtD6Kuz/uSUP+GPVl2bwNBfBR/HEQ+FY+UvxiEbc1Ewz3rCmaUlqN2E+9wQ4PtMRIOOtUXswajtylPgxS/8B71XawLb01AITCO27pL0iclIJnHeGY9Kf1H+Ku2LK4Ns9a+xpXEUYk71yxXdkmbYgKHDGamqGqcEC5n04eGaO07v3hKtph0B+bQOadKTLwA==
- Delivery-date: Tue, 23 Jul 2024 18:29:09 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 2024-07-23 13:34, Andrew Cooper wrote:
On 23/07/2024 6:31 pm, oleksii.kurochko@xxxxxxxxx wrote:
On Tue, 2024-07-23 at 11:04 -0400, Jason Andryuk wrote:
On 2024-07-23 11:04, Anthony PERARD wrote:
On Mon, Jul 15, 2024 at 07:46:31PM -0400, Jason Andryuk wrote:
"$dev" needs to be set correctly for backendtype=phy as well as
backendtype=tap. Move the setting into the conditional, so it
can be
handled properly for each.
(dev could be captured during tap-ctl allocate for blktap module,
but it
would not be set properly for the find_device case. The
backendtype=tap
case would need to be handled regardless.)
Fixes: 6fcdc84927 ("hotplug: Restore block-tap phy
compatibility")
Do you mean f16ac12bd418 ("hotplug: Restore block-tap phy
compatibility") ?
Yes! Thanks for checking that - I must have grabbed the hash from a
local branch.
Fixes: 76a484193d ("hotplug: Update block-tap")
Signed-off-by: Jason Andryuk <jason.andryuk@xxxxxxx>
With the fixes tag fix:
Reviewed-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
Thanks again.
Oleksii, this is a fix (for an incomplete fix) for 4.19. 76a484193d
broke compatibility for block-tap with the blktap2 kernel model (when
adding support for tapback). This finishes restoring blktap2
support.
I realize it's late in the release if you don't want to take it.
It's pretty late but I just wanted to clarify:
1. Is so critical that we should have this in 4.19?
2. If we won't take it now, then will it be backported anyway?
2) Yes it will get backported. In fact I'm about to commit it to staging.
1) It's a bug in a new feature for 4.19, so if we don't take this bugfix
then we'll have to strip it from the release notes.
It's a bug in the old feature. The new feature - tapback daemon
support, backendtype=tap - works with what's in the 4.19 tree. It's the
old kernel module support - backendtype=phy,script=block-tap - that was
broken when adding tapback support. This patch fixes the old support.
The change is localized in the block-tap script and requires explicit
configuration (script=block-tap) to use. So it seems to me to be a
lower risk to take it even though it is late in the cycle.
Regards,
Jason
|
