From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Ally Heev <allyheev@gmail.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"Alexander Lobakin" <aleksander.lobakin@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Simon Horman <horms@kernel.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>
Subject: Re: [RFT net-next PATCH RESEND 0/2] ethernet: intel: fix freeing uninitialized pointers with __free
Date: Mon, 1 Dec 2025 13:40:37 -0800 [thread overview]
Message-ID: <81053279-f2da-420c-b7a1-9a81615cd7ca@intel.com> (raw)
In-Reply-To: <20251124-aheev-fix-free-uninitialized-ptrs-ethernet-intel-v1-0-a03fcd1937c0@gmail.com>
On 11/23/2025 11:40 PM, Ally Heev wrote:
> Uninitialized pointers with `__free` attribute can cause undefined
> behavior as the memory assigned randomly to the pointer is freed
> automatically when the pointer goes out of scope.
>
> We could just fix it by initializing the pointer to NULL, but, as usage of
> cleanup attributes is discouraged in net [1], trying to achieve cleanup
> using goto
These two drivers already have multiple other usages of this. All the
other instances initialize to NULL; I'd prefer to see this do the same
over changing this single instance.
Thanks,
Tony
> [1] https://docs.kernel.org/process/maintainer-netdev.html#using-device-managed-and-cleanup-h-constructs
>
> Signed-off-by: Ally Heev <allyheev@gmail.com>
> ---
> Ally Heev (2):
> ice: remove __free usage in ice_flow
> idpf: remove __free usage in idpf_virtchnl
>
> drivers/net/ethernet/intel/ice/ice_flow.c | 6 ++++--
> drivers/net/ethernet/intel/idpf/idpf_virtchnl.c | 28 +++++++++++++++++--------
> 2 files changed, 23 insertions(+), 11 deletions(-)
> ---
> base-commit: 24598358a1b4ca1d596b8e7b34a7bc76f54e630f
> change-id: 20251113-aheev-fix-free-uninitialized-ptrs-ethernet-intel-abc0cc9278d8
>
> Best regards,
> -----BEGIN PGP SIGNATURE-----
>
> iHUEABYKAB0WIQQBFRpOLrIakF7DYvaWPaLUP9d7HAUCaRn0WAAKCRCWPaLUP9d7
> HPCSAP4tu8ld+4Og65tjSYNChRqIR4Gn8C546JFeozyQW6uj3wD/SQEPIidSAYbb
> klXrZrKIBOc/avt55S2+krl241aNJA8=
> =guHM
> -----END PGP SIGNATURE-----
next prev parent reply other threads:[~2025-12-01 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 7:40 Ally Heev
2025-11-24 7:40 ` [PATCH RESEND RFT net-next 1/2] ice: remove __free usage in ice_flow Ally Heev
2025-11-24 10:00 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-24 7:40 ` [PATCH RESEND RFT net-next 2/2] idpf: remove __free usage in idpf_virtchnl Ally Heev
2025-11-24 9:59 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-12-01 21:40 ` Tony Nguyen [this message]
2025-12-02 19:47 ` [RFT net-next PATCH RESEND 0/2] ethernet: intel: fix freeing uninitialized pointers with __free ally heev
2025-12-02 18:17 ` [Intel-wired-lan] " Tony Nguyen
2025-12-03 8:09 ` ally heev
2025-12-03 8:45 ` Przemek Kitszel
2025-12-08 3:07 ` ally heev
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=81053279-f2da-420c-b7a1-9a81615cd7ca@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=allyheev@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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
all inboxes | Powered by JetHome®