From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Benjamin Marzinski <bmarzins@redhat.com>, Martin Wilck <mwilck@suse.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
device-mapper development <dm-devel@lists.linux.dev>
Subject: Re: Obsolete features (was Re: [PATCH 0/4] minio cleanup patches.)
Date: Tue, 21 Jul 2026 13:18:01 +0200 [thread overview]
Message-ID: <49c8f713-77fb-4e86-ba02-e98c25319c22@gmail.com> (raw)
In-Reply-To: <al4_1Ad2useO9bNR@redhat.com>
On 7/20/26 5:33 PM, Benjamin Marzinski wrote:
> On Sun, Jul 19, 2026 at 04:57:00PM +0200, Xose Vazquez Perez wrote:
>> Another candidate to drop is the retain_attached_hw_handler infrastructure:
>> ( grep -Eir "hwhandler|hw_handler" )
>> Since Linux 4.3, the kernel always enforces "retain_attached_hw_handler yes".
>> Because this option is completely obsolete, could it be dropped from multipath-tools?
> I'm never sure how far back we need to support kernels. I could easily
> be convinced that we don't need to worry about kernels before 4.3 with
> the latest upstream code. If we still do care about 4.2, I would also be
> open to deprecating the option, and just always having it set to yes.
Only enterprise distributions with extended/long-term support use kernels
older than 4.3:
* SLES 11-SP4: 3.0
* RHEL 7: 3.10
* Ubuntu 14.04 LTS: 3.13
(Note that even CIP long-term kernel starts at 4.4)
Furthermore, the code handling older kernel behavior for hw_handler is
still properly maintained in the respective stable branches of
multipath-tools: stable-0.10.y through stable-0.15.y
Regards.
prev parent reply other threads:[~2026-07-21 11:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 19:07 [PATCH 0/4] minio cleanup patches Benjamin Marzinski
2026-06-15 19:07 ` [PATCH 1/4] libmultipath: deprecate rr_weight, and make it do nothing Benjamin Marzinski
2026-06-15 19:07 ` [PATCH 2/4] libmultipath: deprecate rr_min_io_rq, " Benjamin Marzinski
2026-06-15 19:07 ` [PATCH 3/4] libmultipath: deprecate rr_min_io Benjamin Marzinski
2026-06-15 19:07 ` [PATCH 4/4] libmultipath: don't set hwhander for bio based devices Benjamin Marzinski
2026-06-15 21:00 ` [PATCH 0/4] minio cleanup patches Xose Vazquez Perez
2026-06-15 22:56 ` Benjamin Marzinski
2026-06-16 7:47 ` Xose Vazquez Perez
2026-07-19 14:57 ` Obsolete features (was Re: [PATCH 0/4] minio cleanup patches.) Xose Vazquez Perez
2026-07-20 15:33 ` Benjamin Marzinski
2026-07-20 19:29 ` Martin Wilck
2026-07-21 11:18 ` Xose Vazquez Perez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49c8f713-77fb-4e86-ba02-e98c25319c22@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=mwilck@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox