From: Dave Marquardt <davemarq@linux.ibm.com>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH net-next] ibmveth: Use WARN_ON with error handling rather than BUG_ON
Date: Mon, 14 Apr 2025 08:17:49 -0500 [thread overview]
Message-ID: <87o6wyhog2.fsf@linux.ibm.com> (raw)
In-Reply-To: <Z/iwd8qonlrfOkO5@mev-dev.igk.intel.com> (Michal Swiatkowski's message of "Fri, 11 Apr 2025 08:02:31 +0200")
Michal Swiatkowski <michal.swiatkowski@linux.intel.com> writes:
> On Thu, Apr 10, 2025 at 01:39:18PM -0500, Dave Marquardt wrote:
>> - Replaced BUG_ON calls with WARN_ON calls with error handling,
>> with calls to a new ibmveth_reset routine, which resets the device.
>> - Added KUnit tests for ibmveth_remove_buffer_from_pool and
>> ibmveth_rxq_get_buffer under new IBMVETH_KUNIT_TEST config option.
>> - Removed unneeded forward declaration of ibmveth_rxq_harvest_buffer.
>
> It will be great if you split this patch into 3 patches according to
> your description.
Thanks. I debated the right approach here. Thanks for the guidance.
>> static struct kobj_type ktype_veth_pool;
>> @@ -231,7 +230,10 @@ static void ibmveth_replenish_buffer_pool(struct ibmveth_adapter *adapter,
>> index = pool->free_map[free_index];
>> skb = NULL;
>>
>> - BUG_ON(index == IBM_VETH_INVALID_MAP);
>> + if (WARN_ON(index == IBM_VETH_INVALID_MAP)) {
>> + (void)schedule_work(&adapter->work);
>
> What is the purpose of void casting here (and in other places in this
> patch)?
I'm indicating that I'm ignoring the bool returned by schedule_work().
Since this seemed odd to you, I take it the convention in Linux code is
not doing this.
>> + goto failure2;
>
> Maybe increment_buffer_failure, or sth that is telling what happen after
> goto.
Okay, I can change that.
>> + }
>>
>> /* are we allocating a new buffer or recycling an old one */
>> if (pool->skbuff[index])
>> @@ -300,6 +302,7 @@ static void ibmveth_replenish_buffer_pool(struct ibmveth_adapter *adapter,
>> DMA_FROM_DEVICE);
>> dev_kfree_skb_any(pool->skbuff[index]);
>> pool->skbuff[index] = NULL;
>> +failure2:
>> adapter->replenish_add_buff_failure++;
>>
>> mb();
>> @@ -370,20 +373,36 @@ static void ibmveth_free_buffer_pool(struct ibmveth_adapter *adapter,
>> }
>> }
>>
>
> [...]
Thanks for your review!
-Dave
prev parent reply other threads:[~2025-04-14 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 18:39 [PATCH net-next] ibmveth: Use WARN_ON with error handling rather than BUG_ON Dave Marquardt
2025-04-11 6:02 ` Michal Swiatkowski
2025-04-14 13:17 ` Dave Marquardt [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=87o6wyhog2.fsf@linux.ibm.com \
--to=davemarq@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michal.swiatkowski@linux.intel.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 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.