From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Kent Gibson <warthog618@gmail.com>, 4fqr <4fqr@proton.me>,
Vincent Fazio <vfazio@xes-inc.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [PATCH libgpiod 00/14] libgpiod: assortment of fixes
Date: Thu, 9 Apr 2026 09:32:53 +0200 [thread overview]
Message-ID: <177571997161.4055.11075492714806891807.b4-ty@oss.qualcomm.com> (raw)
In-Reply-To: <20260407-treewide-fixes-v1-0-66c9744a56a3@oss.qualcomm.com>
On Tue, 07 Apr 2026 14:49:51 +0200, Bartosz Golaszewski wrote:
> This series fixes a number of bugs reported to my by a person going by
> 4fqr <4fqr@proton.me>. The report seems to have been generated at least
> in part with the help from some kind of an AI agent, however the person
> behind it is almost certainly a human (these are indeed weird times if
> I need to say things like that...).
>
> This includes some urgent security fixes in python bindings and a slew of
> changes addressing less severe bugs.
>
> [...]
Applied, thanks!
[01/14] bindings: python: fix heap-buffer overflow bugs on setting/getting values
https://git.kernel.org/brgl/c/c6a76be56ce61f9267a84c2534634b435a7641ff
[02/14] bindings: python: remove duplicated edge detection setting
https://git.kernel.org/brgl/c/a2c92c9ece231c03d15a7b4846779a8fd554ec0b
[03/14] core: fix 1-byte buffer over-read bugs in gpiod_chip_info_from_uapi()
https://git.kernel.org/brgl/c/c040d4e15e5d4190895da5427db0a52b7457c12e
[04/14] core: fix parameter type in gpiod_line_mask_test_bit()
https://git.kernel.org/brgl/c/27081075f3e28582d250fb38f361183ce6bf097c
[05/14] core: store debounce_period_us with correct type
https://git.kernel.org/brgl/c/d1c60753e15106d1c34f5f5c12683e8db715c42e
[06/14] core: check the value of num_lines returned by the kernel
https://git.kernel.org/brgl/c/641f54aa55c4337fca31414827e14511e6ac91f5
[07/14] tools: reject "u" as period unit specifier
https://git.kernel.org/brgl/c/39f6239848f604996fd52f542300564e764fc157
[08/14] tools: fix an integer overflow bug in parse_period()
https://git.kernel.org/brgl/c/6702eed1a5f2cec5b8df66151c438ed657963064
[09/14] tools: gpionotify: fix memory leak on every event read
https://git.kernel.org/brgl/c/42697e4c6c79e376f895e7222af94b7010cb1d1f
[10/14] tools: gpionotify: add the missing return value check for calloc()
https://git.kernel.org/brgl/c/ee0efc09f1b0000b57d681cd8a0e9def9f62f5b4
[11/14] tools: gpionotify: free pollfds on exit()
https://git.kernel.org/brgl/c/da68c01be016b3225a9319045ec017d7eb0d7c71
[12/14] tools: gpionotify: don't leak info returned by gpiod_chip_watch_line_info()
https://git.kernel.org/brgl/c/0de77e2abf124f3027b05d7c0ed8bfcab8e6a41c
[13/14] tools: gpioinfo: use correct function to free the resolver
https://git.kernel.org/brgl/c/6e228ace2acbf161c57a0034f865472dc5993ef5
[14/14] dbus: manager: use the correct loop counter in error path
https://git.kernel.org/brgl/c/aff7a6143bea49e26208986aaa21bc4081146942
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
prev parent reply other threads:[~2026-04-09 7:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 12:49 [PATCH libgpiod 00/14] libgpiod: assortment of fixes Bartosz Golaszewski
2026-04-07 12:49 ` [PATCH libgpiod 01/14] bindings: python: fix heap-buffer overflow bugs on setting/getting values Bartosz Golaszewski
2026-04-07 12:49 ` [PATCH libgpiod 02/14] bindings: python: remove duplicated edge detection setting Bartosz Golaszewski
2026-04-07 12:49 ` [PATCH libgpiod 03/14] core: fix 1-byte buffer over-read bugs in gpiod_chip_info_from_uapi() Bartosz Golaszewski
2026-04-07 12:49 ` [PATCH libgpiod 04/14] core: fix parameter type in gpiod_line_mask_test_bit() Bartosz Golaszewski
2026-04-07 12:49 ` [PATCH libgpiod 05/14] core: store debounce_period_us with correct type Bartosz Golaszewski
2026-04-07 12:49 ` [PATCH libgpiod 06/14] core: check the value of num_lines returned by the kernel Bartosz Golaszewski
2026-04-07 12:49 ` [PATCH libgpiod 07/14] tools: reject "u" as period unit specifier Bartosz Golaszewski
2026-04-07 12:49 ` [PATCH libgpiod 08/14] tools: fix an integer overflow bug in parse_period() Bartosz Golaszewski
2026-04-07 12:50 ` [PATCH libgpiod 09/14] tools: gpionotify: fix memory leak on every event read Bartosz Golaszewski
2026-04-07 12:50 ` [PATCH libgpiod 10/14] tools: gpionotify: add the missing return value check for calloc() Bartosz Golaszewski
2026-04-07 12:50 ` [PATCH libgpiod 11/14] tools: gpionotify: free pollfds on exit() Bartosz Golaszewski
2026-04-07 12:50 ` [PATCH libgpiod 12/14] tools: gpionotify: don't leak info returned by gpiod_chip_watch_line_info() Bartosz Golaszewski
2026-04-07 12:50 ` [PATCH libgpiod 13/14] tools: gpioinfo: use correct function to free the resolver Bartosz Golaszewski
2026-04-07 12:50 ` [PATCH libgpiod 14/14] dbus: manager: use the correct loop counter in error path Bartosz Golaszewski
2026-04-08 11:45 ` [PATCH libgpiod 00/14] libgpiod: assortment of fixes Vincent Fazio
2026-04-08 16:03 ` Vincent Fazio
2026-04-08 16:20 ` 4fqr
2026-04-09 7:32 ` Bartosz Golaszewski [this message]
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=177571997161.4055.11075492714806891807.b4-ty@oss.qualcomm.com \
--to=bartosz.golaszewski@oss.qualcomm.com \
--cc=4fqr@proton.me \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=vfazio@xes-inc.com \
--cc=warthog618@gmail.com \
/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).