From: Jiri Slaby <jirislaby@kernel.org>
To: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Cc: stable-commits@vger.kernel.org
Subject: Re: Patch "ata: sata_mv, avoid trigerrable BUG_ON" has been added to the 4.4-stable tree
Date: Tue, 29 Sep 2020 08:33:24 +0200 [thread overview]
Message-ID: <167f8a53-6b68-05b8-a632-34df046a0376@kernel.org> (raw)
In-Reply-To: <20200928123057.GA1116804@kroah.com>
On 28. 09. 20, 14:30, Greg KH wrote:
>> commit 4b308d858a1a34dae1e38948f2c0497161d9ddd8
>> Author: Jiri Slaby <jslaby@suse.cz>
>> Date: Thu Oct 31 10:59:46 2019 +0100
>>
>> ata: sata_mv, avoid trigerrable BUG_ON
>>
>> [ Upstream commit e9f691d899188679746eeb96e6cb520459eda9b4 ]
>>
>> There are several reports that the BUG_ON on unsupported command in
>> mv_qc_prep can be triggered under some circumstances:
>> https://bugzilla.suse.com/show_bug.cgi?id=1110252
>> https://serverfault.com/questions/888897/raid-problems-after-power-outage
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652185
>> https://bugs.centos.org/view.php?id=14998
>>
>> Let sata_mv handle the failure gracefully: warn about that incl. the
>> failed command number and return an AC_ERR_INVALID error. We can do that
>> now thanks to the previous patch.
>>
>> Remove also the long-standing FIXME.
>>
>> [v2] use %.2x as commands are defined as hexa.
>>
>> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
>> Cc: Jens Axboe <axboe@kernel.dk>
>> Cc: linux-ide@vger.kernel.org
>> Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Signed-off-by: Jens Axboe <axboe@kernel.dk>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>>
>> diff --git a/drivers/ata/sata_mv.c b/drivers/ata/sata_mv.c
>> index 729f26322095e..c24bbdb3f76c8 100644
>> --- a/drivers/ata/sata_mv.c
>> +++ b/drivers/ata/sata_mv.c
>> @@ -2113,12 +2113,10 @@ static void mv_qc_prep(struct ata_queued_cmd *qc)
>> * non-NCQ mode are: [RW] STREAM DMA and W DMA FUA EXT, none
>> * of which are defined/used by Linux. If we get here, this
>> * driver needs work.
>> - *
>> - * FIXME: modify libata to give qc_prep a return value and
>> - * return error here.
>> */
>> - BUG_ON(tf->command);
>> - break;
>> + ata_port_err(ap, "%s: unsupported command: %.2x\n", __func__,
>> + tf->command);
>> + return AC_ERR_INVALID;
>> }
>> mv_crqb_pack_cmd(cw++, tf->nsect, ATA_REG_NSECT, 0);
>> mv_crqb_pack_cmd(cw++, tf->hob_lbal, ATA_REG_LBAL, 0);
>
> This causes a build warning as you can not return a value for a void
> function :(
Sure, you need the patch before, i.e. e9f691d899^:
commit 95364f36701e62dd50eee91e1303187fd1a9f567
Author: Jiri Slaby <jirislaby@kernel.org>
Date: Thu Oct 31 10:59:45 2019 +0100
ata: make qc_prep return ata_completion_errors
And that needs one more patch e9f691d899^^:
commit 25937580a5065d6fbd92d9c8ebd47145ad80052e
Author: Jiri Slaby <jirislaby@kernel.org>
Date: Thu Oct 31 10:59:44 2019 +0100
ata: define AC_ERR_OK
thanks,
--
js
suse labs
next prev parent reply other threads:[~2020-09-29 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200927181119.5ACB623A33@mail.kernel.org>
2020-09-28 12:30 ` Greg KH
2020-09-28 12:33 ` Greg KH
2020-09-29 6:33 ` Jiri Slaby [this message]
2020-09-29 7:15 ` Greg KH
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=167f8a53-6b68-05b8-a632-34df046a0376@kernel.org \
--to=jirislaby@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-commits@vger.kernel.org \
/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®