From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [GIT PULL] gpio: fixes for v6.9
Date: Fri, 10 May 2024 20:26:40 +0200 [thread overview]
Message-ID: <20240510182640.44486-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Here are some last-minute fixes for this release from the GPIO subsystem.
The first two address a regression in performance reported to me after the
conversion to using SRCU in GPIOLIB that was merged during the v6.9 merge
window. The second patch is not technically a fix but since after the
first one we no longer need to use a per-descriptor SRCU struct, I think
it's worth to simplify the code before it gets released on Sunday.
The next two commits fix two memory issues: one use-after-free bug and
one instance of possibly leaking kernel stack memory to user-space.
Please pull,
Bartosz
The following changes since commit e67572cd2204894179d89bd7b984072f19313b03:
Linux 6.9-rc6 (2024-04-28 13:47:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v6.9
for you to fetch changes up to ee0166b637a5e376118e9659e5b4148080f1d27e:
gpiolib: cdev: fix uninitialised kfifo (2024-05-10 16:38:27 +0200)
----------------------------------------------------------------
gpio fixes for v6.9
- fix a performance regression in GPIO requesting and releasing after
the conversion to SRCU
- fix a use-after-free bug due to a race-condition
- fix leaking stack memory to user-space in a GPIO uABI corner case
----------------------------------------------------------------
Bartosz Golaszewski (2):
gpiolib: fix the speed of descriptor label setting with SRCU
gpiolib: use a single SRCU struct for all GPIO descriptors
Kent Gibson (1):
gpiolib: cdev: fix uninitialised kfifo
Zhongqiu Han (1):
gpiolib: cdev: Fix use after free in lineinfo_changed_notify
drivers/gpio/gpiolib-cdev.c | 18 ++++++++++++--
drivers/gpio/gpiolib.c | 58 ++++++++++++++++++++++++++++-----------------
drivers/gpio/gpiolib.h | 17 ++++++++-----
3 files changed, 63 insertions(+), 30 deletions(-)
next reply other threads:[~2024-05-10 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 18:26 Bartosz Golaszewski [this message]
2024-05-10 21:39 ` [GIT PULL] gpio: fixes for v6.9 pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240510182640.44486-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bartosz.golaszewski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).