public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>, cassel@kernel.org
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, hch@lst.de, linux-ppc@kolla.no,
	vidra@ufal.mff.cuni.cz
Subject: Re: [RFC PATCH] ata: pata_macio: Use WARN instead of BUG
Date: Mon, 19 Aug 2024 20:01:53 +0900	[thread overview]
Message-ID: <737ad178-1198-4103-b1ee-46a67ecf12e4@kernel.org> (raw)
In-Reply-To: <20240819101913.489513-1-mpe@ellerman.id.au>

On 8/19/24 19:19, Michael Ellerman wrote:
> The overflow/underflow conditions in pata_macio_qc_prep() should never
> happen. But if they do there's no need to kill the system entirely, a
> WARN and failing the IO request should be sufficient and might allow the
> system to keep running.
> 
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
>  drivers/ata/pata_macio.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> Not sure if AC_ERR_OTHER is the right error code to use?

Given that this would trigger if the command split has is buggy, I think that
AC_ERR_SYSTEM would be better. Can you resend with the change and no "RFC" ?

> 
> diff --git a/drivers/ata/pata_macio.c b/drivers/ata/pata_macio.c
> index eaffa510de49..552e3ac0d391 100644
> --- a/drivers/ata/pata_macio.c
> +++ b/drivers/ata/pata_macio.c
> @@ -554,7 +554,8 @@ static enum ata_completion_errors pata_macio_qc_prep(struct ata_queued_cmd *qc)
>  
>  		while (sg_len) {
>  			/* table overflow should never happen */
> -			BUG_ON (pi++ >= MAX_DCMDS);
> +			if (WARN_ON_ONCE(pi >= MAX_DCMDS))
> +				return AC_ERR_OTHER;
>  
>  			len = (sg_len < MAX_DBDMA_SEG) ? sg_len : MAX_DBDMA_SEG;
>  			table->command = cpu_to_le16(write ? OUTPUT_MORE: INPUT_MORE);
> @@ -566,11 +567,13 @@ static enum ata_completion_errors pata_macio_qc_prep(struct ata_queued_cmd *qc)
>  			addr += len;
>  			sg_len -= len;
>  			++table;
> +			++pi;
>  		}
>  	}
>  
>  	/* Should never happen according to Tejun */
> -	BUG_ON(!pi);
> +	if (WARN_ON_ONCE(!pi))
> +		return AC_ERR_OTHER;
>  
>  	/* Convert the last command to an input/output */
>  	table--;

-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2024-08-19 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19 10:19 [RFC PATCH] ata: pata_macio: Use WARN instead of BUG Michael Ellerman
2024-08-19 11:01 ` Damien Le Moal [this message]
2024-08-20  2:29   ` Michael Ellerman

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=737ad178-1198-4103-b1ee-46a67ecf12e4@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=cassel@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ppc@kolla.no \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=vidra@ufal.mff.cuni.cz \
    /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