From: Luka Gejak <luka.gejak@linux.dev>
To: Fernando Fernandez Mancera <fmancera@suse.de>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: netdev@vger.kernel.org, fmaurer@redhat.com, horms@kernel.org,
luka.gejak@linux.dev
Subject: Re: [PATCH net-next v4 1/2] net: hsr: require valid EOT supervision TLV
Date: Thu, 02 Apr 2026 08:34:47 +0200 [thread overview]
Message-ID: <811E5B8F-85E7-47E2-BEA1-25E62C68929C@linux.dev> (raw)
In-Reply-To: <78c9c953-1aaa-4d44-9c1d-b4e52a5cead3@suse.de>
On April 2, 2026 1:30:57 AM GMT+02:00, Fernando Fernandez Mancera <fmancera@suse.de> wrote:
>On 4/1/26 7:05 PM, Luka Gejak wrote:
>> On Wed Apr 1, 2026 at 11:52 AM CEST, Fernando Fernandez Mancera wrote:
>>> On 4/1/26 11:23 AM, luka.gejak@linux.dev wrote:
>>>> From: Luka Gejak <luka.gejak@linux.dev>
>>>>
>>>> Supervision frames are only valid if terminated with a zero-length EOT
>>>> TLV. The current check fails to reject non-EOT entries as the terminal
>>>> TLV, potentially allowing malformed supervision traffic.
>>>>
>>>> Fix this by strictly requiring the terminal TLV to be HSR_TLV_EOT
>>>> with a length of zero.
>>>>
>>>> Reviewed-by: Felix Maurer <fmaurer@redhat.com>
>>>> Signed-off-by: Luka Gejak <luka.gejak@linux.dev>
>>>> ---
>>>
>>> Hi,
>>>
>>> This has not been reviewed by Felix. Felix provided his Reviewed-by tag
>>> for the v1 which was completely different than this.
>>>
>>> Revisions of this patch:
>>>
>>> v3: https://lore.kernel.org/all/20260329112313.17164-4-luka.gejak@linux.dev/
>>>
>>> v2: https://lore.kernel.org/all/20260326154715.38405-4-luka.gejak@linux.dev/
>>>
>>> v1:
>>> https://lore.kernel.org/all/20260324143503.187642-4-luka.gejak@linux.dev/
>>>
>>> Are these contributions LLM/AI generated? I believe so based on the
>>> email history.
>>>
>>> AI generated review on rtl8723bs:
>>> https://lore.kernel.org/all/B2394A3C-25FD-4CEA-8557-3E68F1F60357@linux.dev/
>>>
>>> Another AI generated review on rtl8723bs:
>>> https://lore.kernel.org/all/3831D599-655E-40B2-9E5D-9DF956013088@linux.dev/
>>>
>>> Likely an AI generated review on a 1 year old HSR patch:
>>> https://lore.kernel.org/all/DHFG26KI6L23.1YCOVQ5SSYMO5@linux.dev/
>>>
>>> If these are indeed, AI generated contributions or reviews they should
>>> be disclosed beforehand. Also there is the Assisted-by: tag. Also note
>>> that developer must take full responsibility for the contribution which
>>> means understanding it completely.
>>>
>>> https://docs.kernel.org/process/coding-assistants.html#signed-off-by-and-developer-certificate-of-origin
>>>
>>> Thanks,
>>> Fernando.
>>
>> HI Fernando,
>> One more question, should I include Assisted-by tag in v5 if AI was not
>> used for writing code but only for formating and translation of the
>> emails to English as I previously mentioned.
>>
>
>I think yes, you should. I also think that AI was actually used for the generated code and also for spotting the valid and invalid issues. If you don't have a real environment for HSR, why would you look into it?
>
>Sorry, it is not my intention to be harsh but there are some things that don't add up for me. Maybe I am being too careful here and you just coincidentally found these problems.
>
>> Best regards,
>> Luka Gejak
>>
>
Hi Fernando,
I understand the concern. To clarify, I am a student, and I discovered
these issues while reading the HSR source to learn about network
redundancy. Since I lack industrial hardware, I verified the logic
using network namespaces and veth pairs on my Arch laptop. The code
and logic are entirely my. As previously mentioned, I only use AI for
English translation and formatting to ensure my communication is
clear. As requested, I will wait for Felix's review before proceeding
with any changes for v5.
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-04-02 6:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 9:23 [PATCH net-next v4 0/2] net: hsr: strict supervision TLV validation luka.gejak
2026-04-01 9:23 ` [PATCH net-next v4 1/2] net: hsr: require valid EOT supervision TLV luka.gejak
2026-04-01 9:52 ` Fernando Fernandez Mancera
2026-04-01 11:06 ` Luka Gejak
2026-04-01 12:05 ` Fernando Fernandez Mancera
2026-04-01 13:31 ` Luka Gejak
2026-04-01 13:44 ` Fernando Fernandez Mancera
2026-04-01 14:19 ` Luka Gejak
2026-04-01 17:05 ` Luka Gejak
2026-04-01 23:30 ` Fernando Fernandez Mancera
2026-04-02 6:34 ` Luka Gejak [this message]
2026-04-01 14:47 ` Fernando Fernandez Mancera
2026-04-01 16:59 ` Luka Gejak
2026-04-01 23:53 ` Fernando Fernandez Mancera
2026-04-01 9:23 ` [PATCH net-next v4 2/2] net: hsr: reject unresolved interlink ifindex luka.gejak
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=811E5B8F-85E7-47E2-BEA1-25E62C68929C@linux.dev \
--to=luka.gejak@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=fmaurer@redhat.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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