From: Greg KH <gregkh@linuxfoundation.org>
To: Tj <tj.iam.tj@proton.me>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] arm64: v6.8: cmdline param >= 146 chars kills kernel
Date: Sat, 27 Jul 2024 07:10:26 +0200 [thread overview]
Message-ID: <2024072722-borrowing-arbitrate-256f@gregkh> (raw)
In-Reply-To: <JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_-PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me>
On Fri, Jul 26, 2024 at 01:48:44PM +0000, Tj wrote:
> This is v6.8 specific; v6.9 is reported as not affected (due to
> extensive code refactoring).
The 6.8.y kernel tree is long end-of-life, there's nothing we can do
about that one anymore, sorry. Also, you really shouldn't be using that
branch for anything at this point in time either.
Always check the front page of kernel.org if you are wondering about the
status of any stable tree.
thanks,
greg k-h
prev parent reply other threads:[~2024-07-27 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 13:48 [PATCH] arm64: v6.8: cmdline param >= 146 chars kills kernel Tj
2024-07-27 5:10 ` Greg KH [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=2024072722-borrowing-arbitrate-256f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=stable@vger.kernel.org \
--cc=tj.iam.tj@proton.me \
--cc=will@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