From: Michael Ellerman <mpe@ellerman.id.au>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>, cassel@kernel.org
Cc: dlemoal@kernel.org, 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: [PATCH v2] ata: pata_macio: Use WARN instead of BUG
Date: Tue, 27 Aug 2024 16:11:54 +1000 [thread overview]
Message-ID: <87a5gyfqad.fsf@mail.lhotse> (raw)
In-Reply-To: <6b2208d1-c18f-14d5-e6d0-acd5c82b4db1@gmail.com>
Sergei Shtylyov <sergei.shtylyov@gmail.com> writes:
> On 8/20/24 6:04 AM, 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.
>
> WARN*() can kill your system with panic_on_warn -- Android is particularly
> fond of this kernel parameter but I guess it's not your case... :-)
> Greg KH usually advices against using these macros. :-)
Yeah, but in this case it's replacing BUG with WARN, so I figure it's
clearly an improvement.
Also if someone is running with panic_on_warn then they *want* their
system to panic if anything strange happens, which is the case here.
>> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> [...]
>
> Please do CC me on the PATA driver patches! This one circumvented my review
> (again)... :-/
Oops sorry, I think I just grabbed the Cc's from the report. I'll use
get_maintainer.pl in future.
cheers
prev parent reply other threads:[~2024-08-27 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 3:04 [PATCH v2] ata: pata_macio: Use WARN instead of BUG Michael Ellerman
2024-08-21 5:36 ` Damien Le Moal
2024-08-21 21:13 ` Sergei Shtylyov
2024-08-22 2:59 ` Christoph Hellwig
2024-08-22 20:39 ` Sergei Shtylyov
2024-08-27 6:11 ` Michael Ellerman [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=87a5gyfqad.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=cassel@kernel.org \
--cc=dlemoal@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=sergei.shtylyov@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.