From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: David Miller <davem@davemloft.net>,
Realtek linux nic maintainers <nic_swsd@realtek.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Erhard F.\"" <erhard_f@mailbox.org>
Subject: Re: [PATCH net] r8169: fix accessing unset transport header
Date: Tue, 5 Jul 2022 21:18:43 +0200 [thread overview]
Message-ID: <1ca36910-31c0-ead6-d19e-c200eff752b4@gmail.com> (raw)
In-Reply-To: <20220705121230.69a4e0e8@kernel.org>
On 05.07.2022 21:12, Jakub Kicinski wrote:
> On Tue, 05 Jul 2022 14:46:14 +0200 Paolo Abeni wrote:
>> On Mon, 2022-07-04 at 00:12 +0200, Heiner Kallweit wrote:
>>> 66e4c8d95008 ("net: warn if transport header was not set") added
>>> a check that triggers a warning in r8169, see [0].
>>>
>>> [0] https://bugzilla.kernel.org/show_bug.cgi?id=216157
>>>
>>> Fixes: 8d520b4de3ed ("r8169: work around RTL8125 UDP hw bug")
>>> Reported-by: Erhard F. <erhard_f@mailbox.org>
>>> Tested-by: Erhard F. <erhard_f@mailbox.org>
>>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>>
>> The patch LGTM, but I think you could mention in the commit message
>> that the bug was [likely] introduced with commit bdfa4ed68187 ("r8169:
>> use Giant Send"), but this change applies only on top of the commit
>> specified by the fixes tag - just to help stable teams.
>
> How about we put Eric's patch under Fixes? The patch is not really
> needed unless the warning is there.
This would also be an option. It just seemed a little illogical to me
to leave the impression a new (useful) warning needs to be fixed.
Just a few seconds ago I sent a v2 following Paolo's proposal.
next prev parent reply other threads:[~2022-07-05 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 22:12 [PATCH net] r8169: fix accessing unset transport header Heiner Kallweit
2022-07-04 0:55 ` Francois Romieu
2022-07-04 9:15 ` Heiner Kallweit
2022-07-04 15:40 ` Francois Romieu
2022-07-04 19:10 ` Heiner Kallweit
2022-07-05 12:46 ` Paolo Abeni
2022-07-05 19:11 ` Heiner Kallweit
[not found] ` <20220705121230.69a4e0e8@kernel.org>
2022-07-05 19:18 ` Heiner Kallweit [this message]
2022-07-05 19:23 ` Jakub Kicinski
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=1ca36910-31c0-ead6-d19e-c200eff752b4@gmail.com \
--to=hkallweit1@gmail.com \
--cc=davem@davemloft.net \
--cc=erhard_f@mailbox.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).