[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a6243882-e289-4a08-9119-3c73933d6458@web.de>
Date: Wed, 5 Mar 2025 10:20:50 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Dan Carpenter <dan.carpenter@...aro.org>,
kernel-janitors@...r.kernel.org, freedreno@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org, linux-arm-msm@...r.kernel.org
Cc: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Abhinav Kumar <quic_abhinavk@...cinc.com>,
Archit Taneja <architt@...eaurora.org>, Daniel Vetter <daniel@...ll.ch>,
David Airlie <airlied@...il.com>, Jeykumar Sankaran <jsanka@...eaurora.org>,
Jordan Crouse <jordan@...micpenguin.net>,
Marijn Suijten <marijn.suijten@...ainline.org>,
Rob Clark <robdclark@...il.com>, Sean Paul <sean@...rly.run>,
Simona Vetter <simona@...ll.ch>, Vinod Koul <vkoul@...nel.org>,
cocci@...ia.fr, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] Clarification for “undefined behaviour”?
>> Dereferences of null pointers are treated in special ways.
>
> This not a dereference. It's just pointer math.
Do you prefer the wording “member access through pointer” occasionally?
https://en.cppreference.com/w/c/language/operator_member_access
How do you tend to describe (and detect) null pointer dereferences so far?
https://wiki.sei.cmu.edu/confluence/display/c/EXP34-C.+Do+not+dereference+null+pointers#EXP34C.Donotdereferencenullpointers-AutomatedDetection
Regards,
Markus
Powered by blists - more mailing lists