All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iker Pedrosa <ikerpedrosam@gmail.com>
To: brgl@bgdev.pl
Cc: Iker Pedrosa <ikerpedrosam@gmail.com>,
	ipedrosa@redhat.com, javierm@redhat.com, perobins@redhat.com,
	linux-gpio@vger.kernel.org, warthog618@gmail.com
Subject: [PATCH libgpiod v2 0/4] Fix issues detected by static analyzer
Date: Mon, 29 Jul 2024 12:57:15 +0200	[thread overview]
Message-ID: <cover.1722250385.git.ikerpedrosam@gmail.com> (raw)

This patch series contain a set of fixes for several issues detected by a
static analyzer tool. They are related to wrong pointers management and
string termination.

v2 includes a number of fixes to issues highlighted by Kent Gibson
<warthog618@gmail.com>. 

Iker Pedrosa (4):
  bindings: python: gpiod: avoid use after free
  lib: line-info strings termination
  lib: chip-info strings termination
  tools: free to avoid leak

 bindings/python/gpiod/ext/chip.c | 6 ++++--
 lib/chip-info.c                  | 4 ++--
 lib/line-info.c                  | 4 ++--
 tools/gpioinfo.c                 | 4 +++-
 4 files changed, 11 insertions(+), 7 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-07-29 10:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 10:57 Iker Pedrosa [this message]
2024-07-29 10:57 ` [PATCH libgpiod v2 1/4] bindings: python: gpiod: avoid use after free Iker Pedrosa
2024-07-29 10:57 ` [PATCH libgpiod v2 2/4] lib: line-info strings termination Iker Pedrosa
2024-07-29 10:57 ` [PATCH libgpiod v2 3/4] lib: chip-info " Iker Pedrosa
2024-07-29 10:57 ` [PATCH libgpiod v2 4/4] tools: free to avoid leak Iker Pedrosa
2024-07-31  9:21 ` [PATCH libgpiod v2 0/4] Fix issues detected by static analyzer Bartosz Golaszewski

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=cover.1722250385.git.ikerpedrosam@gmail.com \
    --to=ikerpedrosam@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=ipedrosa@redhat.com \
    --cc=javierm@redhat.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=perobins@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.