mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Rand Deeb <rand.sec96@gmail.com>,
	deeb.rand@confident.ru, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org,
	shda@confident.ru
Subject: Re: [PATCH v2] ata: libata-core: Ignore forced transfer modes the host does not support
Date: Thu, 22 Oct 2026 10:11:13 +0200	[thread overview]
Message-ID: <atnFIf_bZA28HRwk@ryzen> (raw)
In-Reply-To: <fb677bdb-355d-4a46-9e4b-db989a7690d9@kernel.org>

On Thu, Oct 22, 2026 at 09:55:35AM +0200, Damien Le Moal wrote:
> On 2026/10/15 21:49, Rand Deeb wrote:
> > The libata.force parameter can force a transfer mode (pio0-6, mwdma0-4,
> > udma0-7) for a port or device. ata_force_xfermask() applies it in
> > ata_do_set_mode() right after ata_dev_xfermask() has limited the device
> > masks to what the host supports. It replaces those masks with the forced
> > mode without checking the host masks, so a mode the controller does not
> > support is passed to the driver's ->set_piomode() or ->set_dmamode().
> > 
> > Several PATA drivers rely on the host masks to keep the mode number in
> > range when indexing their timing tables. ata_piix, pata_efar,
> > pata_it8213, pata_oldpiix, pata_radisys and pata_rdc declare ATA_PIO4
> > and ATA_MWDMA12_ONLY, index a five-entry PIO timing table with
> > pio_mode - XFER_PIO_0, and index a three-entry needed_pio[] table with
> > dma_mode - XFER_MW_DMA_0. Booting with libata.force=pio5, pio6, mwdma3
> > or mwdma4 makes them read past those tables, use the values read as
> > further indices into the timing table, and write the result to the
> > controller's timing registers.
> > 
> > Make ata_force_xfermask() skip, with a warning, a forced transfer mode
> > that is not in the port's PIO, MWDMA or UDMA mask, and keep looking for
> > an earlier matching libata.force entry, as it already does for entries
> > that do not apply to the device. With libata.force=pio4,1.0:pio5 on a
> > PIO4 host, device 1.0 now gets pio4 instead of pio5. Forcing a mode the
> > host supports still works as before, including a mode that
> > ata_dev_xfermask() removed for the device or cable.
> > 
> > Found by Linux Verification Center (linuxtesting.org) with SVACE.
> > 
> > Fixes: 332673257056 ("libata: implement libata.force module parameter")
> > Signed-off-by: Rand Deeb <rand.sec96@gmail.com>
> 
> Looks good.
> 
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>

Repushed commit to pick up Damien's tag.

Code unchanged.


Kind regards,
Niklas

      reply	other threads:[~2026-10-22  8:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 19:49 Rand Deeb
2026-10-19 12:28 ` Niklas Cassel
2026-10-22  7:55 ` Damien Le Moal
2026-10-22  8:11   ` Niklas Cassel [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=atnFIf_bZA28HRwk@ryzen \
    --to=cassel@kernel.org \
    --cc=deeb.rand@confident.ru \
    --cc=dlemoal@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=rand.sec96@gmail.com \
    --cc=shda@confident.ru \
    /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

all inboxes | Powered by JetHome®