From: Jacob Keller <jacob.e.keller@intel.com>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Agalakov Daniil <ade@amicon.ru>, <lvc-project@linuxtesting.org>,
Roman Razov <rrv@amicon.ru>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
<linux-kernel@vger.kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Daniil Iskhakov <dish@amicon.ru>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net 2/3] e1000: fix endianness conversion of uninitialized words
Date: Mon, 30 Mar 2026 07:46:17 -0700 [thread overview]
Message-ID: <ddf2b078-5f0d-41a2-8b1f-091215034d1d@intel.com> (raw)
In-Reply-To: <20260329181905-cf917b74fe3e24dd60228601-pchelkin@ispras>
On 3/29/2026 9:02 AM, Fedor Pchelkin wrote:
> On Wed, 25. Mar 16:01, Jacob Keller wrote:
>> On 3/25/2026 8:19 AM, Fedor Pchelkin wrote:
>>> Hi,
>>>
>>> On Tue, 24. Mar 16:26, Tony Nguyen wrote:
> Thanks for the feedback. I see Daniil has already sent some newer
> versions targeting -next. The problem in question is rather obscure about
> severity of its consequences but spending some time on investigating this
> now I'm more inclined to think there should be no opportunity for UB here
> and it's okay to process the patch like Tony suggested..
Makes sense. Thanks for the careful review either way!
Regards,
Jake
next prev parent reply other threads:[~2026-03-30 14:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 12:05 [PATCH net 0/3] e1000/e1000e: fix uninitialized memory access in EEPROM write Agalakov Daniil
2026-03-18 12:05 ` [PATCH net 1/3] e1000: check return value of e1000_read_eeprom Agalakov Daniil
2026-03-18 15:38 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-18 12:05 ` [PATCH net 2/3] e1000: fix endianness conversion of uninitialized words Agalakov Daniil
2026-03-18 15:38 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-24 23:26 ` Tony Nguyen
2026-03-25 15:19 ` Fedor Pchelkin
2026-03-25 23:01 ` Jacob Keller
2026-03-29 16:02 ` Fedor Pchelkin
2026-03-30 14:46 ` Jacob Keller [this message]
2026-03-18 12:05 ` [PATCH net 3/3] e1000e: " Agalakov Daniil
2026-03-18 15:39 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-24 23:27 ` Tony Nguyen
2026-03-25 15:02 ` [PATCH net v2] e1000: check return value of e1000_read_eeprom Agalakov Daniil
2026-03-25 15:42 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-25 15:16 ` [PATCH net-next v2 0/2] e1000/e1000e: limit endianness conversion to boundary words Agalakov Daniil
2026-03-25 15:16 ` [PATCH net-next v2 1/2] e1000: " Agalakov Daniil
2026-03-26 7:29 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-25 15:16 ` [PATCH net-next v2 2/2] e1000e: " Agalakov Daniil
2026-03-26 7:28 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-31 20:57 ` Tony Nguyen
2026-04-01 12:08 ` [PATCH net-next v3 0/2] e1000/e1000e: " Agalakov Daniil
2026-04-01 12:08 ` [PATCH net-next v3 1/2] e1000: " Agalakov Daniil
2026-04-01 12:08 ` [PATCH net-next v3 2/2] e1000e: " Agalakov Daniil
2026-04-01 12:25 ` [PATCH net-next v3 0/2] e1000/e1000e: " Fedor Pchelkin
2026-03-25 16:00 ` [PATCH net v3] e1000: check return value of e1000_read_eeprom Agalakov Daniil
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=ddf2b078-5f0d-41a2-8b1f-091215034d1d@intel.com \
--to=jacob.e.keller@intel.com \
--cc=ade@amicon.ru \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dish@amicon.ru \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pchelkin@ispras.ru \
--cc=przemyslaw.kitszel@intel.com \
--cc=rrv@amicon.ru \
/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