linux-kernel - Re: [RESEND PATCH 0/2] pinctrl: zynq: fix two bugs of zynq pinmux function

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

Message-ID: <20150520142358.GS31550@xsjsorenbubuntu>
Date:	Wed, 20 May 2015 07:23:58 -0700
From:	Sören Brinkmann <soren.brinkmann@...inx.com>
To:	Masahiro Yamada <yamada.masahiro@...ionext.com>
CC:	<linux-gpio@...r.kernel.org>,
	Michal Simek <michal.simek@...inx.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	<linux-kernel@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RESEND PATCH 0/2] pinctrl: zynq: fix two bugs of zynq pinmux
 function

Hi Masahiro,

On Wed, 2015-05-20 at 05:42PM +0900, Masahiro Yamada wrote:
> 
> I sent the previous one to linux-serial by mistake.
> I am resending to linux-gpio, dropping linux-serial.
> Sorry for noise.
> 
> 
> 
> Masahiro Yamada (2):
>   pinctrl: zynq: fix DEFINE_ZYNQ_PINMUX_FUNCTION_MUX macro
>   pinctrl: zynq: fix offset address for {SD0,SD1}_WP_CD_SEL

For the series:
Reviewed-by: Sören Brinkmann <soren.brinkmann@...inx.com>

I'm not sure how severe the impact of these bugs is. It looks like the
the current driver could corrupt the register for MIO pin0, am I right?
It may be a good ides to add
  Fixes: add958cee967 "pinctrl: Add driver for Zynq"
(I suspect that bug is there from the beginning) and ask Linus to
consider this for stable.

	Thanks,
	Sören
--
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/