From: Greg KH <gregkh@linuxfoundation.org>
To: Lucas Faria Mendes <lucas.fariamo08@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] vme_user: tighten slave window bounds and validate offsets
Date: Thu, 28 May 2026 07:33:56 +0200 [thread overview]
Message-ID: <2026052810-gracious-timid-b936@gregkh> (raw)
In-Reply-To: <20260527211425.569038-1-lucas.fariamo08@gmail.com>
On Wed, May 27, 2026 at 06:14:24PM -0300, Lucas Faria Mendes wrote:
> Limit slave read/write operations to the allocated buffer size to
> prevent out-of-bounds access when a slave window is
> configured larger than its buffer.
> Treat zero-sized windows and invalid file positions as errors,
> and reject VME_SET_SLAVE requests that exceed the slave buffer.
> This makes the user access driver more robust and avoids
> silent EOF on invalid offsets.
Odd line-wrapping :(
How did you find this issue? How was it tested?
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-28 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 21:14 [PATCH] vme_user: tighten slave window bounds and validate offsets Lucas Faria Mendes
2026-05-28 5:33 ` Greg KH [this message]
2026-05-28 7:00 ` Dan Carpenter
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=2026052810-gracious-timid-b936@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lucas.fariamo08@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.