From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Yang Yingliang <yangyingliang@huawei.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH v2 4/4] ata: libata-transport: fix error handling in ata_tdev_add()
Date: Tue, 8 Nov 2022 17:03:45 +0900 [thread overview]
Message-ID: <ad7f4ad1-cded-8a09-6a7e-da6b91ee04b2@opensource.wdc.com> (raw)
In-Reply-To: <20221108075209.2434888-5-yangyingliang@huawei.com>
On 11/8/22 16:52, Yang Yingliang wrote:
> In ata_tdev_add(), the return value of transport_add_device() is not
> checked. As a result, another error after that function call leads to
> a kernel crash (null-ptr-deref) because transport_remove_device() is
> called to remove a device that was not added.
This was the error pattern for the previous 2 cases, but not for this
one. For this case, transport_configure_device() would be called for a
device that was not added, no ? so where does the backtrace below come
from ? It does not correspond to the code this patch is changing.
>
> Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0
> CPU: 61 PID: 13969 Comm: rmmod Kdump: loaded Tainted: G W 6.1.0-rc3+ #13
> pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> pc : device_del+0x48/0x39c
> lr : device_del+0x44/0x39c
> Call trace:
> device_del+0x48/0x39c
> attribute_container_class_device_del+0x28/0x40
> transport_remove_classdev+0x60/0x7c
> attribute_container_device_trigger+0x118/0x120
> transport_remove_device+0x20/0x30
> ata_tlink_delete+0x4c/0xb0 [libata]
> ata_tport_delete+0x2c/0x60 [libata]
> ata_port_detach+0x148/0x1b0 [libata]
> ata_pci_remove_one+0x50/0x80 [libata]
> ahci_remove_one+0x4c/0x8c [ahci]
>
> Fix this by checking and handling return value of transport_add_device()
> in ata_tdev_add().
>
> Fixes: d9027470b886 ("[libata] Add ATA transport class")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
> drivers/ata/libata-transport.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/ata/libata-transport.c b/drivers/ata/libata-transport.c
> index aac9336e8153..e4fb9d1b9b39 100644
> --- a/drivers/ata/libata-transport.c
> +++ b/drivers/ata/libata-transport.c
> @@ -713,7 +713,13 @@ static int ata_tdev_add(struct ata_device *ata_dev)
> return error;
> }
>
> - transport_add_device(dev);
> + error = transport_add_device(dev);
> + if (error) {
> + device_del(dev);
> + ata_tdev_free(ata_dev);
> + return error;
> + }
> +
> transport_configure_device(dev);
> return 0;
> }
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-11-08 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 7:52 [PATCH v2 0/4] ata: libata-transport: fix some error handing Yang Yingliang
2022-11-08 7:52 ` [PATCH v2 1/4] ata: libata-transport: fix double ata_host_put() in ata_tport_add() Yang Yingliang
2022-11-08 7:52 ` [PATCH v2 2/4] ata: libata-transport: fix error handling " Yang Yingliang
2022-11-08 7:52 ` [PATCH v2 3/4] ata: libata-transport: fix error handling in ata_tlink_add() Yang Yingliang
2022-11-08 7:52 ` [PATCH v2 4/4] ata: libata-transport: fix error handling in ata_tdev_add() Yang Yingliang
2022-11-08 8:03 ` Damien Le Moal [this message]
2022-11-08 9:27 ` Yang Yingliang
2022-11-08 9:33 ` Damien Le Moal
2022-11-08 10:49 ` Yang Yingliang
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=ad7f4ad1-cded-8a09-6a7e-da6b91ee04b2@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=yangyingliang@huawei.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