From: Stephen Boyd <sboyd@codeaurora.org>
To: Michal Marek <mmarek@suse.cz>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
linux-kernel@vger.kernel.org,
Mitchel Humpherys <mitchelh@codeaurora.org>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] coccinelle: Check for missing NULL terminators in of_device_id tables
Date: Mon, 09 Jun 2014 14:50:42 -0700 [thread overview]
Message-ID: <53962C32.2040003@codeaurora.org> (raw)
In-Reply-To: <53962B54.8030909@suse.cz>
On 06/09/14 14:47, Michal Marek wrote:
> Dne 3.6.2014 20:25, Julia Lawall napsal(a):
>> From: Stephen Boyd <sboyd@codeaurora.org>
>>
>> Failure to terminate an of_device_id table can lead to confusing
>> failures depending on where the compiler places the array. Add a
>> check to make sure these tables are terminated. Thanks to Mitchel
>> Humpherys for coming up with the pattern initially.
>>
>> Cc: Mitchel Humpherys <mitchelh@codeaurora.org>
>> Cc: Julia Lawall <Julia.Lawall@lip6.fr>
>> Cc: Gilles Muller <Gilles.Muller@lip6.fr>
>> Cc: Nicolas Palix <nicolas.palix@imag.fr>
>> Cc: Grant Likely <grant.likely@linaro.org>
>> Cc: Rob Herring <robh+dt@kernel.org>
>> Cc: devicetree@vger.kernel.org
>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>> Acked-by: Grant Likely <grant.likely@linaro.org>
>> Signed-off-by: Julia Lawall <julia.lawall@lip6.fr>
>>
>> ---
>>
>> v3: Removed unneeded rule bad_of_table. Placed * in context rule on the
>> closing brace; putting it on the field caused all fields to be marked.
>>
>> v4: corrected authorship
>>
>> scripts/coccinelle/misc/of_table.cocci | 62 +++++++++++++++++++++++++++++++++
>> 1 file changed, 62 insertions(+)
> Applied to kbuild.git#misc, thanks. BTW, what is so special about of
> device drivers? Shouldn't we check for missing sentinels in all kinds of
> device tables?
>
Yes the rule should probably be expanded to cover more tables. I guess
this is just more noticeable because a driver may match some device that
it isn't supposed to match and start writing random bits to registers it
shouldn't be, causing the system to hang.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
prev parent reply other threads:[~2014-06-09 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 18:04 [PATCH v2] coccinelle: Check for missing NULL terminators in of_device_id tables Stephen Boyd
2014-06-03 9:24 ` Grant Likely
2014-06-03 10:15 ` Julia Lawall
[not found] ` <alpine.DEB.2.02.1406031208380.2036-bi+AKbBUZKagILUCTcTcHdKyNwTtLsGr@public.gmane.org>
2014-06-03 17:45 ` Stephen Boyd
[not found] ` <538E09C1.30200-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-06-03 18:14 ` Julia Lawall
[not found] ` <alpine.DEB.2.02.1406032013150.2009-bi+AKbBUZKagILUCTcTcHdKyNwTtLsGr@public.gmane.org>
2014-06-03 18:19 ` Stephen Boyd
[not found] ` <538E119D.8010304-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-06-03 18:25 ` Julia Lawall
2014-06-09 21:47 ` Michal Marek
2014-06-09 21:50 ` Stephen Boyd [this message]
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=53962C32.2040003@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=Gilles.Muller@lip6.fr \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mitchelh@codeaurora.org \
--cc=mmarek@suse.cz \
--cc=nicolas.palix@imag.fr \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).