public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Terrell <nickrterrell@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nick Terrell <terrelln@fb.com>,
	linux-kernel@vger.kernel.org,
	Nick Terrell <nickrterrell@gmail.com>,
	Kernel Team <Kernel-team@fb.com>,
	x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>
Subject: [PATCH 0/1] lib: zstd: Backport fix for in place decompression
Date: Wed, 15 Feb 2023 17:39:27 -0800	[thread overview]
Message-ID: <20230216013928.1784731-1-nickrterrell@gmail.com> (raw)

From: Nick Terrell <terrelln@fb.com>

Hi Linus and all,

I've attached a patch for a hot fix for zstd that may cause issues for x86 kernel
decompression, though I haven't recieved any reports of problems as of yet.

I've submitted it to my linux-next branch for testing, and the upstream commit is
well tested, but would also appreciate any testing that folks would be kind
enough to provide.

I'm sending this to you, Linus, to make sure that you're aware of my intent to
send you this hot fix. I intend to let it bake in linux-next for a day or two,
and get some community testing, then send you a pull request with this change.
Please let me know if there is anything else I should do, or if there is a
different process that I should be following.

Best,
Nick Terrell

Nick Terrell (1):
  lib: zstd: Backport fix for in-place decompression

 lib/zstd/decompress/zstd_decompress.c | 25 ++++++++++++++++++++++---
 1 file changed, 22 insertions(+), 3 deletions(-)

--
2.39.0


             reply	other threads:[~2023-02-16  1:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16  1:39 Nick Terrell [this message]
2023-02-16  1:39 ` [PATCH 1/1] lib: zstd: Backport fix for in-place decompression Nick Terrell

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=20230216013928.1784731-1-nickrterrell@gmail.com \
    --to=nickrterrell@gmail.com \
    --cc=Kernel-team@fb.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=terrelln@fb.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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