linux-kernel - Re: [PATCH] clocksource: exynos4: Fix wrong bit operation in exynos4_mct

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-id: <52F18CE4.1070700@samsung.com>
Date:	Wed, 05 Feb 2014 09:59:16 +0900
From:	jonghwa3.lee@...sung.com
To:	Kyungmin Park <kmpark@...radead.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"thomas.abraham@...aro.org" <thomas.abraham@...aro.org>,
	"daniel.lezcano@...aro.org" <daniel.lezcano@...aro.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	MyungJoo Ham <myungjoo.ham@...sung.com>,
	최찬우 <cw00.choi@...sung.com>
Subject: Re: [PATCH] clocksource: exynos4: Fix wrong bit operation in
 exynos4_mct_write()

On 2014년 02월 04일 22:01, Kyungmin Park wrote:

> 
> 
> On Tuesday, February 4, 2014, Jonghwa Lee <jonghwa3.lee@...sung.com
> <mailto:jonghwa3.lee@...sung.com>> wrote:
> 
>     There was a faulty bit operation during checking offset in exynos4_mct_write().
>     This patch fixes it correctly.
> 
> What's the issue? What's happened with current code? 


Whether it would be applied or not, current code looks working fine. Because
those things are just needed to confirm writing to certain register. The
technical reference manual recommends users to check write status register for
some specified registers, e.g. control register. However current code always
skip checking write status even we access the registers required. It will just
executed writing operation only and leave write status uncleared.

Thanks,
Jonghwa

> 
> Thank you,
> Kyungmin Park
> 
> 
>     Signed-off-by: Jonghwa Lee <jonghwa3.lee@...sung.com <javascript:;>>
>     Signed-off-by: MyungJoo Ham <myungjoo.ham@...sung.com <javascript:;>>
>     ---
>      drivers/clocksource/exynos_mct.c |    4 ++--
>      1 file changed, 2 insertions(+), 2 deletions(-)
> 
>     diff --git a/drivers/clocksource/exynos_mct.c b/drivers/clocksource/exynos_mct.c
>     index 62b0de6..e60b019 100644
>     --- a/drivers/clocksource/exynos_mct.c
>     +++ b/drivers/clocksource/exynos_mct.c
>     @@ -94,8 +94,8 @@ static void exynos4_mct_write(unsigned int value, unsigned
>     long offset)
>             __raw_writel(value, reg_base + offset);
> 
>             if (likely(offset >= EXYNOS4_MCT_L_BASE(0))) {
>     -               stat_addr = (offset & ~EXYNOS4_MCT_L_MASK) + MCT_L_WSTAT_OFFSET;
>     -               switch (offset & EXYNOS4_MCT_L_MASK) {
>     +               stat_addr = (offset & EXYNOS4_MCT_L_MASK) + MCT_L_WSTAT_OFFSET;
>     +               switch (offset & ~EXYNOS4_MCT_L_MASK) {
>                     case MCT_L_TCON_OFFSET:
>                             mask = 1 << 3;          /* L_TCON write status */
>                             break;
>     --
>     1.7.9.5
> 
>     --
>     To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>     the body of a message to majordomo@...r.kernel.org <javascript:;>
>     More majordomo info at  http://vger.kernel.org/majordomo-info.html
>     Please read the FAQ at  http://www.tux.org/lkml/
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/