From: Greg KH <gregkh@linuxfoundation.org>
To: Xinghui Li <korantwork@gmail.com>
Cc: peterz@infradead.org, jpoimboe@redhat.com, tglx@linutronix.de,
stable@vger.kernel.org, x86@kernel.org, alexs@kernel.org
Subject: Re: [bug report]warning about entry_64.S from objtool in v5.4 LTS
Date: Mon, 13 Feb 2023 13:31:49 +0100 [thread overview]
Message-ID: <Y+ottclebGlehBWU@kroah.com> (raw)
In-Reply-To: <CAEm4hYX3q=zRFYO68UXYmtnA-ZcVXX_rsnka-eR0--wYdNgHzw@mail.gmail.com>
On Mon, Feb 13, 2023 at 08:20:03PM +0800, Xinghui Li wrote:
> However, for conservative reasons, parts of our customers are opposed
> to making significant upgrades to the products.
Your customers are not concervative at all if they are consuming the
RETBLEED and other Spectre-like fixes into your kernels. Those are
major changes as you can see (affecting every single file you build), so
the "do not change anything" argument does not make any sense here,
right?
> Meanwhile, for commercial purposes, we are committed to maintaining
> the products we sell over a period of time.
> For the above reasons, we also maintain older versions of the product,
> so we will fix/report the issues in older kernels just like this time.
That's great, but some help in fixing this reported issue would also be
most appreciated, as you are the best one to test and verify the fix.
thanks,
greg k-h
prev parent reply other threads:[~2023-02-13 12:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 3:09 [bug report]warning about entry_64.S from objtool in v5.4 LTS Xinghui Li
2023-02-06 5:40 ` Greg KH
2023-02-06 9:22 ` Xinghui Li
2023-02-06 9:39 ` Greg KH
2023-02-07 0:18 ` Kuniyuki Iwashima
2023-02-07 6:43 ` Xinghui Li
2023-02-07 6:52 ` Greg KH
2023-02-07 7:19 ` Xinghui Li
2023-02-07 7:30 ` Greg KH
2023-02-13 12:20 ` Xinghui Li
2023-02-13 12:31 ` 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=Y+ottclebGlehBWU@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexs@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=korantwork@gmail.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).