From: Fan Gong <gongfan1@huawei.com>
To: <csh0052@gmail.com>
Cc: <gongfan1@huawei.com>, <lcy8047@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net] hinic3: handle auxiliary device ID allocation failure
Date: Wed, 23 Sep 2026 16:05:56 +0800 [thread overview]
Message-ID: <20260923080557.1752-1-gongfan1@huawei.com> (raw)
In-Reply-To: <179001656835.91284.3719235813225229273.idr-bug-81@gmail.com>
> hinic3_init_hwdev() stores the result of hinic3_adev_idx_alloc() in
> hwdev->dev_id without checking for an error. If ID allocation fails but
> the remaining initialization succeeds, hinic3_add_one_adev() uses the
> negative error code as the auxiliary device ID instead of a reserved ID.
>
> Return the allocation error before initializing the hardware. Add an
> unwind label that clears pci_adapter->hwdev and frees the allocation
> without attempting to release an ID that was never allocated.
>
> Fixes: 8133788d023f ("hinic3: Nic_io initialization")
> Reported-by: Changyul Lee <lcy8047@gmail.com>
> Assisted-by: LLM
> Signed-off-by: Sang-Hoon Choi <csh0052@gmail.com>
> ---
> Found during source review at mainline
> 5dd1818b15d98d4a20806cd00b1b40320b06004f. The affected source is unchanged
> at f0100363d8c374bd8e9ea7c9ba02744f0b802ca4.
>
> The modified hinic3_hwdev.o compiled with x86 allmodconfig and W=1.
> I have not tested this on hinic3 hardware or injected ID allocation
> failures.
Thank you for your contribution! We will test this patch later.
next prev parent reply other threads:[~2026-09-23 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 18:49 [PATCH net] hinic3: handle auxiliary device ID allocation failure Sang-Hoon Choi
2026-09-23 8:05 ` Fan Gong [this message]
2026-09-28 23:30 ` patchwork-bot+netdevbpf
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=20260923080557.1752-1-gongfan1@huawei.com \
--to=gongfan1@huawei.com \
--cc=csh0052@gmail.com \
--cc=lcy8047@gmail.com \
--cc=netdev@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