| 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: Mon, 5 Sep 2011 08:13:13 -0700 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Jonathan Cameron <jic23@....ac.uk> Cc: LKML <linux-kernel@...r.kernel.org> Subject: Re: Current state of regmap. On Mon, Sep 05, 2011 at 03:14:14PM +0100, Jonathan Cameron wrote: > As my previous email said I've been messing around with regmap today. > I've run into a couple of bugs and was wondering if I'm running > behind the current version. I've pulled what is up on kernel.org > for linux-next at the moment. That's the current state, I'm running development systems here where all the I2C and SPI devices on the system go through regmap and anyone running ASoC will be using it. Though there's a few patches floating around now and I'm just testing the module_put() fix so it'll not be the current state soonish. kernel.org is closed for updates right now, if I do much i'll probably show up on opensource.wolfsonmicro.com in the short term. > As I'm emailing anyway. Everywhere other than regmap-debugfs max_register > is treated as the max valid. In there we have a loop that is > for (i = 0; i < map->max_register; i++) so that treats it as one > larger than the max valid register index. That's an off by one in the debugfs code, will fix. You can check this sort of stuff out by looking at the users. -- 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