[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFr9PXnMXPmuaUnfr-VwaZDX1hY8ZDtp1+UxOau6DKpUP9FdzQ@mail.gmail.com>
Date: Tue, 28 Sep 2021 22:31:06 +0900
From: Daniel Palmer <daniel@...f.com>
To: Colin King <colin.king@...onical.com>
Cc: Daniel Palmer <daniel@...ngy.jp>,
Romain Perier <romain.perier@...il.com>,
Alessandro Zummo <a.zummo@...ertech.it>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Nobuhiro Iwamatsu <iwamatsu@...auri.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-rtc@...r.kernel.org, kernel-janitors@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH][next] rtc: msc313: Fix unintentional sign extension issue
on left shift of a u16
Hi Colin,
On Tue, 28 Sept 2021 at 21:39, Colin King <colin.king@...onical.com> wrote:
>Shifting the u16 value returned by readw by 16 bits to the left
>will be promoted to a 32 bit signed int and then sign-extended
>to an unsigned long. If the top bit of the readw is set then
>the shifted value will be sign extended and the top 32 bits of
>the result will be set.
Ah,.. C is fun in all the wrong places. :)
These chips are full of 32bit registers that are split into two 16
registers 4 bytes apart when seen from the ARM CPU so we probably have
this same mistake in a few other places.
A similar pattern is used a bit later on in the same file to read the counter:
seconds = readw(priv->rtc_base + REG_RTC_CNT_VAL_L)
| (readw(priv->rtc_base + REG_RTC_CNT_VAL_H) << 16);
I guess it works at the moment because the top bit won't be set until 2038.
Thanks,
Daniel
Powered by blists - more mailing lists