From: Dimitri Sivanich <sivanich@hpe.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Muhammad Usama Anjum <usama.anjum@arm.com>,
Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] misc: sgi-gru: Remove broken page-table walks
Date: Fri, 31 Jul 2026 08:29:57 -0500 [thread overview]
Message-ID: <amyjVdtAzdbiGDfn@hpe.com> (raw)
In-Reply-To: <2026073117-rounding-professed-1c2b@gregkh>
On Fri, Jul 31, 2026 at 01:32:48PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Jul 30, 2026 at 07:22:18AM -0500, Dimitri Sivanich wrote:
> > Muhammad,
> >
> > I should let you know that we're currently and actively working on a
> > forthcoming patch to remove the sgi-gru driver, due to security concerns. We
> > hope to submit this patch soon.
>
> A patch to "delete the driver" should be quite simple.
>
> But until that shows up, I'll queue these up as they fix the obvious
> problems in the code today.
>
Greg,
The patchset will involve two drivers. The sgi-xp driver makes heavy use of
sgi-gru. The decision has been made to remove both.
next prev parent reply other threads:[~2026-07-31 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 11:12 Muhammad Usama Anjum
2026-07-30 11:12 ` [PATCH 1/3] misc: sgi-gru: remove interrupt-context " Muhammad Usama Anjum
2026-07-30 11:12 ` [PATCH 2/3] misc: sgi-gru: remove obsolete atomic fault-handling state Muhammad Usama Anjum
2026-07-30 11:12 ` [PATCH 3/3] misc: sgi-gru: inline the user CBR status update Muhammad Usama Anjum
2026-07-30 12:22 ` [PATCH 0/3] misc: sgi-gru: Remove broken page-table walks Dimitri Sivanich
2026-07-30 12:53 ` Muhammad Usama Anjum
2026-07-30 14:08 ` Arnd Bergmann
2026-07-31 11:32 ` Greg Kroah-Hartman
2026-07-31 13:29 ` Dimitri Sivanich [this message]
2026-07-31 13:34 ` Muhammad Usama Anjum
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=amyjVdtAzdbiGDfn@hpe.com \
--to=sivanich@hpe.com \
--cc=arnd@arndb.de \
--cc=dimitri.sivanich@hpe.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=usama.anjum@arm.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
Powered by JetHome