From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Hao-Qun Huang <alvinhuang0603@gmail.com>,
Johan Hovold <johan@kernel.org>, Kees Cook <kees@kernel.org>,
Nadzeya Hutsko <nadzya.info@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Martyn Welch <martyn@welchs.me.uk>
Subject: Re: [PATCH 1/2] staging: vme_user: fix location monitor leak in fake bridge
Date: Thu, 9 Jul 2026 13:03:01 +0200 [thread overview]
Message-ID: <2026070945-tropics-shredder-bad7@gregkh> (raw)
In-Reply-To: <ak986K54RhRDMpfn@stanley.mountain>
On Thu, Jul 09, 2026 at 01:50:16PM +0300, Dan Carpenter wrote:
> Hi Greg, I'm back from travel. Should we just delete staging/vme_user/?
> I don't know really if it's used but there are some pretty severe
> security issues with this code.
There are probably lots of issues with this code, but from what I
recall, the systems that use this do not have "untrusted" userspace
processes on it, so it shouldn't be an issue. If that's not the case,
then yes, it should be deleted, but really, no one cares about security
issues with code that adds TAINT_CRAP to the system when loaded :)
Martyn, any thoughts?
thanks,
greg k-h
prev parent reply other threads:[~2026-07-09 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 6:58 [PATCH 1/2] staging: vme_user: fix location monitor leak in fake bridge Hao-Qun Huang
2026-07-04 6:58 ` [PATCH 2/2] staging: vme_user: fix location monitor leak in tsi148 bridge Hao-Qun Huang
2026-07-09 10:50 ` [PATCH 1/2] staging: vme_user: fix location monitor leak in fake bridge Dan Carpenter
2026-07-09 11:03 ` Greg Kroah-Hartman [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=2026070945-tropics-shredder-bad7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alvinhuang0603@gmail.com \
--cc=error27@gmail.com \
--cc=johan@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martyn@welchs.me.uk \
--cc=nadzya.info@gmail.com \
--cc=stable@vger.kernel.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