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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150610172949.GA4668@localhost>
Date:	Wed, 10 Jun 2015 19:29:49 +0200
From:	Johan Hovold <johan@...nel.org>
To:	Bartosz Golaszewski <bgolaszewski@...libre.com>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Alexandre Courbot <gnurou@...il.com>,
	linux-gpio <linux-gpio@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Patrick Titiano <ptitiano@...libre.com>,
	Benoit Cousson <bcousson@...libre.com>
Subject: Re: [PATCH] gpiolib: unexport requested gpios on gpiochip removal

Hi Bartosz,

On Wed, Jun 10, 2015 at 04:34:21PM +0200, Bartosz Golaszewski wrote:
> When a GPIO expander device is removed - e.g. via i2c-adapter
> new_device/delete_device interface - with some GPIOs still requested,
> gpiochip_remove() function will emit a warning but remove the chip
> anyway.
> 
> If we then reinstantiate this device and try to export any of the GPIOs
> still requested on gpiochip deletion the following warning will be
> emitted:

For GPIOs exported through sysfs, this has already been fixed by commit
483d82110879 ("gpio: sysfs: fix memory leaks and device hotplug"), which
has also been backported to stable.

Thanks,
Johan
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ