Netdev List
 help / color / mirror / Atom feed
From: Jijie Shao <shaojijie@huawei.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <shaojijie@huawei.com>, <davem@davemloft.net>,
	<edumazet@google.com>, <pabeni@redhat.com>,
	<andrew+netdev@lunn.ch>, <horms@kernel.org>,
	<shenjian15@huawei.com>, <liuyonglong@huawei.com>,
	<chenhao418@huawei.com>, <huangdonghua3@h-partners.com>,
	<yangshuaisong@h-partners.com>, <shiyongbang@huawei.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] net: hibmcge: fix incorrect packets in the RX path issue
Date: Fri, 15 May 2026 09:45:27 +0800	[thread overview]
Message-ID: <c61ee5db-2578-401f-a4fb-f2fb697af731@huawei.com> (raw)
In-Reply-To: <20260514171621.02b2ffb1@kernel.org>


on 2026/5/15 8:16, Jakub Kicinski wrote:
> On Tue, 12 May 2026 20:34:56 +0800 Jijie Shao wrote:
>> Therefore, this patch disables the Relaxed Ordering to ensure the
>> strict order of packets and descriptors.
>>
>> Additionally, during the process of analyzing the issue,
>> it was discovered that the position of dma_rmb() was incorrect.
>> It should first execute dma_sync_single_for_cpu(), and then dma_rmb().
>> This patch has also made the corresponding modifications.
> Should be a separate patch.

ok

>
>> Fixes: f72e25594061 ("net: hibmcge: Implement rx_poll function to receive packets")
>> Signed-off-by: Jijie Shao <shaojijie@huawei.com>
>> ---
>>   drivers/net/ethernet/hisilicon/hibmcge/hbg_main.c | 4 +++-
>>   drivers/net/ethernet/hisilicon/hibmcge/hbg_txrx.c | 6 +++---
>>   2 files changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/hisilicon/hibmcge/hbg_main.c b/drivers/net/ethernet/hisilicon/hibmcge/hbg_main.c
>> index 068da2fd1fea..5b91b596349c 100644
>> --- a/drivers/net/ethernet/hisilicon/hibmcge/hbg_main.c
>> +++ b/drivers/net/ethernet/hisilicon/hibmcge/hbg_main.c
>> @@ -420,6 +420,8 @@ static int hbg_pci_init(struct pci_dev *pdev)
>>   		return -ENOMEM;
>>   
>>   	pci_set_master(pdev);
>> +	pcie_capability_clear_word(pdev, PCI_EXP_DEVCTL,
>> +				   PCI_EXP_DEVCTL_RELAX_EN);
>>   	return 0;
>>   }
>>   
>> @@ -525,4 +527,4 @@ module_exit(hbg_module_exit);
>>   MODULE_LICENSE("GPL");
>>   MODULE_AUTHOR("Huawei Tech. Co., Ltd.");
>>   MODULE_DESCRIPTION("hibmcge driver");
>> -MODULE_VERSION("1.0");
>> +MODULE_VERSION("2.0");
> Please don't change MODULE_VERSIONs they are meaningless for in-tree
> modules.

Our users typically compile the driver as a separate ko (CONFIG_HIBMCGE=M).
I want to use the version to quickly determine whether the user's driver code has this patch.

Thanks,
Jijie Shao


      reply	other threads:[~2026-05-15  1:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 12:34 [PATCH net] net: hibmcge: fix incorrect packets in the RX path issue Jijie Shao
2026-05-15  0:16 ` Jakub Kicinski
2026-05-15  1:45   ` Jijie Shao [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=c61ee5db-2578-401f-a4fb-f2fb697af731@huawei.com \
    --to=shaojijie@huawei.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=chenhao418@huawei.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=huangdonghua3@h-partners.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuyonglong@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shenjian15@huawei.com \
    --cc=shiyongbang@huawei.com \
    --cc=yangshuaisong@h-partners.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