| 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
| ||
|
Message-Id: <cover.1467772840.git.viresh.kumar@linaro.org> Date: Tue, 5 Jul 2016 19:57:05 -0700 From: Viresh Kumar <viresh.kumar@...aro.org> To: Wolfram Sang <wsa@...-dreams.de>, Jean Delvare <jdelvare@...e.com> Cc: linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org, Johan Hovold <johan@...nel.org>, Alex Elder <elder@...aro.org>, Viresh Kumar <viresh.kumar@...aro.org> Subject: [PATCH 0/2] i2c-dev: Don't let userspace block adapter Hi Wolfram/Jean, I am part of the kernel team for Google's projectara [1], where we are building a module smart phone. This series tries to fix one of the problems we hit on our system as we are required to hotplug pretty much every thing on the phone and so this fixes hotplug issues with i2c-dev. As described in the second patch, the current implementation of i2c-dev file operations doesn't let the modules (hardware attached to the phone) eject from the phone as the cleanup path for the module hasn't finished yet (i2c adapter not removed). We can't let the userspace block the kernel devices forever in such cases. I was able to test them on the ARA phone with kernel 3.10 only and not mainline. -- viresh [1] https://atap.google.com/ara/ Viresh Kumar (2): i2c-dev: don't get i2c adapter via i2c_dev i2c-dev: Don't block the adapter from unregistering drivers/i2c/i2c-dev.c | 79 ++++++++++++++++++++++++++++++++++++++++++--------- include/linux/i2c.h | 1 + 2 files changed, 67 insertions(+), 13 deletions(-) -- 2.7.4
Powered by blists - more mailing lists