linux-kernel - Re: [PATCH] drivers/rtc/rtc-max77686.c: Fix wrong register

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>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20130814132139.82b8c40e460845535190e1d0@linux-foundation.org>
Date:	Wed, 14 Aug 2013 13:21:39 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Sangjung Woo <sangjung.woo@...sung.com>
Cc:	Jonghwa Lee <jonghwa3.lee@...sung.com>,
	linux-kernel@...r.kernel.org,
	Myugnjoo Ham <myungjoo.ham@...sung.com>
Subject: Re: [PATCH] drivers/rtc/rtc-max77686.c: Fix wrong register

On Wed, 14 Aug 2013 10:21:41 +0900 Sangjung Woo <sangjung.woo@...sung.com> wrote:

> Fix to read the wrong register when checking whether the RTC timer has
> reached or not.
> 
> ...
>
> --- a/drivers/rtc/rtc-max77686.c
> +++ b/drivers/rtc/rtc-max77686.c
> @@ -240,9 +240,9 @@ static int max77686_rtc_read_alarm(struct device *dev, struct rtc_wkalrm *alrm)
>  	}
>  
>  	alrm->pending = 0;
> -	ret = regmap_read(info->max77686->regmap, MAX77686_REG_STATUS1, &val);
> +	ret = regmap_read(info->max77686->regmap, MAX77686_REG_STATUS2, &val);
>  	if (ret < 0) {
> -		dev_err(info->dev, "%s:%d fail to read status1 reg(%d)\n",
> +		dev_err(info->dev, "%s:%d fail to read status2 reg(%d)\n",
>  				__func__, __LINE__, ret);
>  		goto out;
>  	}

The changelog didn't describe the end-user visible effects of the bug,
so I am unable to determine which kernel version(s) need patching. 
Please always include this information.

--
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/