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
| ||
|
Date: Sun, 30 Nov 2014 01:00:01 +0400 From: Alexander Kochetkov <al.kochet@...il.com> To: Kevin Hilman <khilman@...nel.org>, Tony Lindgren <tony@...mide.com>, Felipe Balbi <balbi@...com>, Wolfram Sang <wsa@...-dreams.de>, Alexander Kochetkov <al.kochet@...il.com> Cc: linux-omap@...r.kernel.org, linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org Subject: [RFC 0/2] i2c: omap: new fixes for driver The first patch fix i2c-omap driver for omap2420, found by code review and later reported by Tony Lindgren <tony@...mide.com> here[1]. Candidate for stable? The second patch unhide the reson of system lockup. The patch is rebased on branch 'i2c/for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux (6e79807443cba7397cd855ed29d6faba51d4c893) Tony, could you check, what the patches fix the problem reported[1]? Kevin, could you run tests for patches on all omap boards? Regards, Alexander. [1] http://www.spinics.net/lists/linux-i2c/msg17811.html Alexander Kochetkov (2): i2c: omap: fix buffer overruns during RX/TX data processing i2c: omap: show that the reason of system lockup is an unhandled ISR event drivers/i2c/busses/i2c-omap.c | 64 ++++++++++++++++++++++++++++++++--------- 1 file changed, 50 insertions(+), 14 deletions(-) -- 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 More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists