From: Dan Carpenter <dan.carpenter@linaro.org>
To: F6BVP <f6bvp@free.fr>
Cc: linux-hams@vger.kernel.org, netdev <netdev@vger.kernel.org>,
Dan Cross <crossd@gmail.com>, David Ranch <dranch@trinnet.net>,
Eric Dumazet <edumazet@google.com>,
Folkert van Heusden <folkert@vanheusden.com>
Subject: Re: [ROSE] [AX25] 6.15.10 long term stable kernel oops
Date: Mon, 25 Aug 2025 15:40:43 +0300 [thread overview]
Message-ID: <aKxZy7XVRhYiHu7c@stanley.mountain> (raw)
In-Reply-To: <6a5cf9cf-9984-4e1b-882f-b9b427d3c096@free.fr>
No, this patch doesn't do anything. "p" is never used without being
initialized. Plus, I bet that if you do:
grep CONFIG_INIT_STACK_ALL_ZERO .config
You will find it is set to =y which means the compiler is already
initializing pointers to NULL anyway.
Perhaps you're worried that about this line:
p = kmalloc(struct_size(p, data, 2 * size), GFP_ATOMIC | __GFP_NOWARN);
where it seems to call "struct_size(p" where p is not initialized? On
that line the compiler is just doing a sizeof(*p) and not really using
the value of p at all.
regards,
dan carpenter
next prev parent reply other threads:[~2025-08-25 12:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11c5701d-4bf9-4661-ad8a-06690bbe1c1c@free.fr>
[not found] ` <fff0b3eb-ea42-4475-970d-30622dc25dca@free.fr>
2025-08-16 18:45 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops Bernard Pidoux
2025-08-18 10:00 ` Bernard Pidoux
2025-08-18 10:04 ` Folkert van Heusden
2025-08-18 14:19 ` F6BVP
2025-08-18 16:30 ` Dan Cross
2025-08-18 18:28 ` F6BVP
2025-08-18 22:11 ` Dan Cross
2025-08-18 22:31 ` F6BVP
2025-08-20 8:50 ` F6BVP
2025-08-20 19:33 ` kworker/u16 Not tainted F6BVP
2025-08-21 11:28 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops F6BVP
2025-08-21 22:39 ` F6BVP
2025-08-22 3:10 ` Folkert van Heusden
2025-08-24 14:04 ` F6BVP
2025-08-25 12:40 ` Dan Carpenter [this message]
2025-08-26 13:31 ` F6BVP
2025-08-26 13:36 ` Eric Dumazet
2025-08-27 14:16 ` F6BVP
2025-08-27 17:30 ` Florian Westphal
2025-08-28 16:39 ` F6BVP
2025-08-30 23:37 ` F6BVP
2025-09-01 12:04 ` Eric Dumazet
2025-09-01 12:05 ` Eric Dumazet
[not found] ` <cd0461e0-8136-4f90-df7b-64f1e43e78d4@trinnet.net>
2025-09-01 15:59 ` F6BVP
2025-09-01 16:03 ` Eric Dumazet
2025-09-01 19:10 ` David Ranch
2025-09-01 19:16 ` Eric Dumazet
2025-09-02 7:44 ` F6BVP
2025-09-02 7:55 ` Eric Dumazet
2025-09-03 9:51 ` [BUG] [ROSE] slab-use-after-free in lock_timer_base Bernard Pidoux
2025-09-03 10:01 ` Eric Dumazet
2025-09-03 10:11 ` F6BVP
2025-09-03 11:07 ` Takamitsu Iwai
2025-09-01 19:04 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops David Ranch
2025-09-02 7:54 ` F6BVP
2025-08-19 21:17 ` [OT] " Miroslav Skoric
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=aKxZy7XVRhYiHu7c@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=crossd@gmail.com \
--cc=dranch@trinnet.net \
--cc=edumazet@google.com \
--cc=f6bvp@free.fr \
--cc=folkert@vanheusden.com \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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