diff options
author | Boerge Struempfel <boerge.struempfel@gmail.com> | 2023-11-29 16:23:07 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-12-13 18:45:30 +0100 |
commit | 6df51c525a2d4f8cce843ced0da00452dc6f30a7 (patch) | |
tree | 5134e49446410a43b373c59052790c1feb9a6f20 /mm | |
parent | 73bbca1298645b995ce105d0290f05cbe37fc35a (diff) | |
download | linux-starfive-6df51c525a2d4f8cce843ced0da00452dc6f30a7.tar.gz linux-starfive-6df51c525a2d4f8cce843ced0da00452dc6f30a7.tar.bz2 linux-starfive-6df51c525a2d4f8cce843ced0da00452dc6f30a7.zip |
gpiolib: sysfs: Fix error handling on failed export
[ Upstream commit 95dd1e34ff5bbee93a28ff3947eceaf6de811b1a ]
If gpio_set_transitory() fails, we should free the GPIO again. Most
notably, the flag FLAG_REQUESTED has previously been set in
gpiod_request_commit(), and should be reset on failure.
To my knowledge, this does not affect any current users, since the
gpio_set_transitory() mainly returns 0 and -ENOTSUPP, which is converted
to 0. However the gpio_set_transitory() function calles the .set_config()
function of the corresponding GPIO chip and there are some GPIO drivers in
which some (unlikely) branches return other values like -EPROBE_DEFER,
and -EINVAL. In these cases, the above mentioned FLAG_REQUESTED would not
be reset, which results in the pin being blocked until the next reboot.
Fixes: e10f72bf4b3e ("gpio: gpiolib: Generalise state persistence beyond sleep")
Signed-off-by: Boerge Struempfel <boerge.struempfel@gmail.com>
Reviewed-by: Andy Shevchenko <andy@kernel.org>
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions