Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp618745pxy; Thu, 22 Apr 2021 09:29:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwQrtftowUJQvT0ssRK2lKNflfgFlmt2LGhf9UfUPTm3nVjezcezCSx/bvpCBJi3lFYZdJY X-Received: by 2002:a17:906:f8cd:: with SMTP id lh13mr4296285ejb.387.1619108950073; Thu, 22 Apr 2021 09:29:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619108950; cv=none; d=google.com; s=arc-20160816; b=k9o7aTlKbQyA2BJUuT6n8Fa0/qpjtj+kaIm1yLk3qzINoUp/ugCMHcmI9aYao8bkZE N4QBRqfSzK2yLwmLnOZbCU7St9ncbSl7T/ADSWOJajOfViRfW8LkPB+hhY2BCmMLgqS3 NvxfhST/jMz7ZOCdqjlbUww8U0wvWfyODC4k6sAYln7K/lVdWrg4Ji8u9U65ZsehOxGU mQwOySFDDabbgfUbQYe3hkKh1tBTtTNy3pjRijXyP0PrI4YzQriHr6Zvgh6MkH9xQCrr tA1pjxmjNGQQGztv+6+pIVV8hcyS+PuEjKQ0ww/aXyEFOrEMozh6V01WsWkA+xft1N6p RyQg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:from:date; bh=scsFcmbEnXr7gnnelEgRZErVhHUCoqgeYX0j0Cte0OE=; b=A5wLmtuUoEbq3aP7lvQ2NnugPMN0d3f4wGfyp88ysR6kDMwmkZRexK6azaVHI1Hx0X JuIPtLnHV4XUjPve+HQZiawoVtp2abT2CHuto5Y1M8pZ+SsBTIUchzAVgQyao9rv23T0 VYS0vJVstHnj1YOItc1GLRLDVxW+H+9V07W0cFujRTuQQz75UyEEJLuY67E+LeZhFbIK pjNtqWeljFVeqGD8n86cs/+sVnY1q+l4h18VWWuTkoG4ICZpSbiewCXN6VWRQBRWByxx D/ibj/MamPIa7MsY1RErya0zqwGa2/oVoi6qvIhAagwwtNj4f43g5aERP9amD4d0NpK9 Gl+w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o16si2497492edi.293.2021.04.22.09.28.45; Thu, 22 Apr 2021 09:29:10 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236695AbhDVQ1y (ORCPT + 99 others); Thu, 22 Apr 2021 12:27:54 -0400 Received: from angie.orcam.me.uk ([157.25.102.26]:39470 "EHLO angie.orcam.me.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236648AbhDVQ1x (ORCPT ); Thu, 22 Apr 2021 12:27:53 -0400 Received: by angie.orcam.me.uk (Postfix, from userid 500) id CD53292009C; Thu, 22 Apr 2021 18:27:17 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id C802A92009B; Thu, 22 Apr 2021 18:27:17 +0200 (CEST) Date: Thu, 22 Apr 2021 18:27:17 +0200 (CEST) From: "Maciej W. Rozycki" To: Khalid Aziz cc: Ondrej Zary , "James E.J. Bottomley" , "Martin K. Petersen" , Christoph Hellwig , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/5] Bring the BusLogic host bus adapter driver up to Y2021 In-Reply-To: Message-ID: References: <202104182221.21533.linux@zary.sk> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 21 Apr 2021, Khalid Aziz wrote: > > Verifying actual ISA operations (third-party DMA, etc.) cannot be made > > this way, but as I understand the issue there is merely with passing data > > structures around and that may not require too much attention beyond > > getting things syntactically correct, which I gather someone forgot to do > > with a change made a while ago. So that should be doable as well. > > In theory this sounds reasonable, but without being able to test with a > real hardware I would be concerned about making this change. Sometimes you have little choice really and that would be less disruptive than dropping support altogether. Even if there's a small issue somewhere it's easier to fix by a competent developer who actually gets the hands on a piece of hardware than bringing back old code that has been removed and consequently not updated according to internal API evolution, etc. I had this issue with the defxx driver with which for years I didn't have a specimen of the EISA variant of the hardware handled. I did my best to maintain EISA support however and while indeed I made a few of mistakes on the way, they were easy to straighten out once I finally did get my hands on an EISA piece. > > NB as noted before I only have a BT-958 readily wired for operation. I > > don't expect I have any other BusLogic hardware, but I may yet have to > > double-check a stash of hardware I have accumulated over the years. But > > that is overseas, so I won't be able to get at it before we're at least > > somewhat closer to normality. If all else fails I could possibly buy one. > > > > I have respun the series now as promised. Does your BT-757 adapter avoid > > the issue with trailing allocation somehow? > > Well, my only test machine with a legacy PCI slot died some time back. I > have been working on putting together a replacement and have now been > able to get a working machine with a BT-950 adapter. I have not seen > issue with trailing allocation upto 5.12-rc8. I am going to try the top > of tree as well to make sure I do not run into this issue. I guess you won't see the issue with a FlashPoint adapter as they work in a different manner. I think your EISA MultiMaster device is more likely to have a problem here. And AFAICT most SCSI commands (or at least the older ones which used to be there when development was still active with the MultiMaster devices) return exactly as much data as requested, so I guess the issue may have gone unnoticed. I'll see if I can find some time to investigate this further now that we have proper documentation available, but meanwhile I do hope the workaround I have come up with 18 years ago already is good enough to keep it. Maciej