From: Khalid Aziz <khalid@gonehiking.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Jakub Kicinski <kuba@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux-foundation.org, linux-scsi@vger.kernel.org,
Manohar Vanga <manohar.vanga@gmail.com>,
Martyn Welch <martyn@welchs.me.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.org,
linux-alpha@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-parisc@vger.kernel.org, Denis Efremov <efremov@linux.com>,
"Maciej W . Rozycki" <macro@orcam.me.uk>,
Matt Wang <wwentao@vmware.com>
Subject: Re: [PATCH 5/6] scsi: remove stale BusLogic driver
Date: Mon, 6 Jun 2022 10:35:28 -0600 [thread overview]
Message-ID: <d39fc9bb-07c1-ad74-1e89-d2aa80578cd4@gonehiking.org> (raw)
In-Reply-To: <20220606084109.4108188-6-arnd@kernel.org>
On 6/6/22 02:41, Arnd Bergmann wrote:
> From: Arnd Bergmann<arnd@arndb.de>
>
> The BusLogic driver is the last remaining driver that relies on the
> deprecated bus_to_virt() function, which in turn only works on a few
> architectures, and is incompatible with both swiotlb and iommu support.
>
> Before commit 391e2f25601e ("[SCSI] BusLogic: Port driver to 64-bit."),
> the driver had a dependency on x86-32, presumably because of this
> problem. However, the change introduced another bug that made it still
> impossible to use the driver on any 64-bit machine.
>
> This was in turn fixed in commit 56f396146af2 ("scsi: BusLogic: Fix
> 64-bit system enumeration error for Buslogic"), 8 years later.
>
> The fact that this was found at all is an indication that there are
> users, and it seems that Maciej, Matt and Khalid all have access to
> this hardware, but if it took eight years to find the problem,
> it's likely that nobody actually relies on it.
>
> Remove it as part of the global virt_to_bus()/bus_to_virt() removal.
> If anyone is still interested in keeping this driver, the alternative
> is to stop it from using bus_to_virt(), possibly along the lines of
> how dpt_i2o gets around the same issue.
>
> Cc: Maciej W. Rozycki<macro@orcam.me.uk>
> Cc: Matt Wang<wwentao@vmware.com>
> Cc: Khalid Aziz<khalid@gonehiking.org>
> Signed-off-by: Arnd Bergmann<arnd@arndb.de>
> ---
> Documentation/scsi/BusLogic.rst | 581 ---
> Documentation/scsi/FlashPoint.rst | 176 -
> MAINTAINERS | 7 -
> drivers/scsi/BusLogic.c | 3727 --------------
> drivers/scsi/BusLogic.h | 1284 -----
> drivers/scsi/FlashPoint.c | 7560 -----------------------------
> drivers/scsi/Kconfig | 24 -
> 7 files changed, 13359 deletions(-)
> delete mode 100644 Documentation/scsi/BusLogic.rst
> delete mode 100644 Documentation/scsi/FlashPoint.rst
> delete mode 100644 drivers/scsi/BusLogic.c
> delete mode 100644 drivers/scsi/BusLogic.h
> delete mode 100644 drivers/scsi/FlashPoint.c
I would say no to removing BusLogic driver. Virtualbox is another
consumer of this driver. This driver is very old but I would rather fix
the issues than remove it until we do not have any users.
Thanks,
Khalid
next prev parent reply other threads:[~2022-06-06 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 8:41 [PATCH 0/6] phase out CONFIG_VIRT_TO_BUS Arnd Bergmann
2022-06-06 8:41 ` [PATCH 1/6] vme: remove ca91cx42 Universe-II support Arnd Bergmann
2022-06-06 8:41 ` [PATCH 2/6] vme: move back to staging Arnd Bergmann
2022-06-06 8:41 ` [PATCH 3/6] media: sta2x11: remove VIRT_TO_BUS dependency Arnd Bergmann
2022-06-06 8:41 ` [PATCH 4/6] scsi: dpt_i2o: drop stale " Arnd Bergmann
2022-06-06 8:41 ` [PATCH 6/6] arch/*/: remove CONFIG_VIRT_TO_BUS Arnd Bergmann
2022-06-07 7:29 ` Geert Uytterhoeven
2022-06-07 12:33 ` Michael Ellerman
2022-06-06 9:25 ` [PATCH 0/6] phase out CONFIG_VIRT_TO_BUS Greg Kroah-Hartman
2022-06-06 15:01 ` Arnd Bergmann
2022-06-07 9:09 ` Martyn Welch
[not found] ` <20220606084109.4108188-6-arnd@kernel.org>
2022-06-06 10:40 ` [PATCH 5/6] scsi: remove stale BusLogic driver Maciej W. Rozycki
2022-06-06 15:00 ` Arnd Bergmann
2022-06-06 16:35 ` Khalid Aziz [this message]
2022-06-08 8:19 ` Arnd Bergmann
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=d39fc9bb-07c1-ad74-1e89-d2aa80578cd4@gonehiking.org \
--to=khalid@gonehiking.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=efremov@linux.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kuba@kernel.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=macro@orcam.me.uk \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
--cc=robin.murphy@arm.com \
--cc=wwentao@vmware.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