From: Jerin Jacob <jerinjacobk@gmail.com>
To: Tomasz Duszynski <tduszynski@marvell.com>
Cc: dev@dpdk.org, Jakub Palider <jpalider@marvell.com>
Subject: Re: [PATCH] raw/cnxk_gpio: fix out of bound access
Date: Thu, 26 Jun 2025 23:36:56 +0530 [thread overview]
Message-ID: <CALBAE1OgF8cqSsp=gz=oYtMggUsCgG6xAGW0T=m7=-cienrdLw@mail.gmail.com> (raw)
In-Reply-To: <20250625112209.2469589-1-tduszynski@marvell.com>
On Wed, Jun 25, 2025 at 4:52 PM Tomasz Duszynski <tduszynski@marvell.com> wrote:
>
> In rare circumstances such as when underlying gpio device is being
> removed while userspace access is still ongoing flags returned from
> ioctl() may be invalid.
>
> Coverity issue: 469060
> Coverity issue: 469061
> Coverity issue: 469067
> Coverity issue: 469068
> Fixes: 9a5ce79325da ("raw/cnxk_gpio: switch to character-based GPIO interface")
>
> Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
Applied to dpdk-next-net-mrvl/for-main. Thanks
prev parent reply other threads:[~2025-06-26 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 11:22 Tomasz Duszynski
2025-06-26 18:06 ` Jerin Jacob [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='CALBAE1OgF8cqSsp=gz=oYtMggUsCgG6xAGW0T=m7=-cienrdLw@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jpalider@marvell.com \
--cc=tduszynski@marvell.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 NNTP newsgroup(s).