public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: David Miller <davem@davemloft.net>
Cc: lramos.prof@yahoo.com.br, linux-ide@vger.kernel.org,
	Borislav Petkov <petkovbb@gmail.com>
Subject: Re: [PATCH] Fix interface autodetection in legacy IDE driver (trial #2)
Date: Tue, 27 Dec 2016 17:06:19 +0100	[thread overview]
Message-ID: <6997612.Sd3D1QNmYZ@amdc3058> (raw)
In-Reply-To: <3010789.Juyl7C8p5j@amdc3058>

On Tuesday, December 27, 2016 11:08:24 AM Bartlomiej Zolnierkiewicz wrote:
> 
> Hi,
> 
> On Monday, December 26, 2016 11:47:24 AM David Miller wrote:
> > From: Luiz Carlos Ramos <lramos.prof@yahoo.com.br>
> > Date: Tue, 11 Oct 2016 22:12:45 -0300
> > 
> > > This humble patch was sent one or two months before, and had no actions,
> > > except for a colleague reply which friendly pointed out some formatting
> > > problems (which were solved in a second message).
> > > 
> > > It relates to an old code, the legacy IDE driver, but the bug it
> > > addresses is real. The code, although rarely used, is
> > > still there to be compiled if one chooses to do so (like me).
> > > 
> > > Also, the fix has a very low risk of present collateral effects IMHO.
> > > It is already compiled and tested in some embedded machines.
> > > 
> > > So, again IMHO, it is worth be fixed.
> > > 
> > > This email is a second trial with it. I hope it can help the one or two
> > > guys out there which are still running the legacy IDE driver and
> > > haven't noticed the former email.
> > > 
> > > Best regards,
> > > 
> > > Signed-off-by: Luiz Carlos Ramos <lramos.prof@yahoo.com.br>
> > 
> > This bug was introduced by commit
> > 20df429dd6671804999493baf2952f82582869fa ("ide-generic: handle probing
> > of legacy io-ports v5") which seems poorly tested.
> 
> Please always cc: the original commit author.
> 
> > Applied and queued up for -stable, th anks.
> 
> For some reason I've never got the discussed patch from
> linux-ide ML though I now have found in the patchwork:
> 
> https://patchwork.ozlabs.org/patch/680975/
> 
> The patch is incorrect.  If you have PCI IDE devices (like in
> the case described in the situation being "fixed" by the patch)
> you should use the correct PCI IDE host driver for proper
> operation and not ide-generic host driver (the latter still can
> be used by using kernel parameters).

Moreover this patch introduces a regression.  In the situation
when there are no PCI IDE devices and the probing should be done
automatically (for the first two legacy IDE ports) it will be no
longer done.

Now back to the using correct PCI IDE host drivers - Luiz what
are the systems that you need this patch on?  Could you please
get 'lspci -nn' command output from them?

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics


  reply	other threads:[~2016-12-27 16:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12  1:12 [PATCH] Fix interface autodetection in legacy IDE driver (trial #2) Luiz Carlos Ramos
2016-12-26 16:47 ` David Miller
2016-12-27 10:08   ` Bartlomiej Zolnierkiewicz
2016-12-27 16:06     ` Bartlomiej Zolnierkiewicz [this message]
2016-12-27 16:41       ` David Miller
2016-12-27 17:25         ` Bartlomiej Zolnierkiewicz
2016-12-28  0:33           ` Luiz Carlos Ramos
2016-12-28  0:38             ` David Miller
2016-12-28 11:16               ` Bartlomiej Zolnierkiewicz
2016-12-28 11:10             ` Bartlomiej Zolnierkiewicz
2016-12-30  0:52               ` Luiz Carlos Ramos
2016-12-30 16:05                 ` Bartlomiej Zolnierkiewicz
2017-01-09 20:25                   ` David Miller
2017-02-21 14:22                   ` Luiz Carlos Ramos

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=6997612.Sd3D1QNmYZ@amdc3058 \
    --to=b.zolnierkie@samsung.com \
    --cc=davem@davemloft.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=lramos.prof@yahoo.com.br \
    --cc=petkovbb@gmail.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