From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.6 000/533] 6.6.54-rc2 review
Date: Fri, 4 Oct 2024 08:55:04 +0200 [thread overview]
Message-ID: <2024100426-wheat-heavily-68d1@gregkh> (raw)
In-Reply-To: <20241004071723.69AD.409509F4@e16-tech.com>
On Fri, Oct 04, 2024 at 07:17:24AM +0800, Wang Yugui wrote:
> Hi,
>
> > This is the start of the stable review cycle for the 6.6.54 release.
> > There are 533 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Sat, 05 Oct 2024 10:30:30 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.6.54-rc2.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.6.y
> > and the diffstat can be found below.
>
> A new waring is report by 'make bzImage' in 6.6.54-rc2,
> but that is not reported in 6.6.53 and 6.12-rc1.
>
> arch/x86/tools/insn_decoder_test: warning: Found an x86 instruction decoder bug, please report this.
> arch/x86/tools/insn_decoder_test: warning: ffffffff8103c4d5: c4 03 81 48 cf e9 vpermil2ps $0x9,%xmm15,%xmm14,%xmm15,%xmm9
> arch/x86/tools/insn_decoder_test: warning: objdump says 6 bytes, but insn_get_length() says 0
> arch/x86/tools/insn_decoder_test: warning: Decoded and checked 6968668 instructions with 1 failures
>
> the root cause is yet not clear.
I've been seeing this locally for all 6.6.y releases, so for me it isn't
new, and I can't seem to track down the root cause. As it's just now
showing up for you, can you do a 'git bisect' to find out the issue?
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-04 6:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 10:33 [PATCH 6.6 000/533] 6.6.54-rc2 review Greg Kroah-Hartman
2024-10-03 13:44 ` Takeshi Ogasawara
2024-10-03 14:40 ` Jon Hunter
2024-10-03 14:42 ` Naresh Kamboju
2024-10-03 15:05 ` Florian Fainelli
2024-10-03 15:54 ` Mark Brown
2024-10-03 16:21 ` Harshit Mogalapalli
2024-10-03 16:47 ` Peter Schneider
2024-10-03 18:48 ` Pavel Machek
2024-10-03 20:54 ` Shuah Khan
2024-10-03 21:04 ` Allen
2024-10-03 23:17 ` Wang Yugui
2024-10-04 6:55 ` Greg Kroah-Hartman [this message]
2024-10-04 10:57 ` Wang Yugui
2024-10-04 12:37 ` Greg Kroah-Hartman
2024-10-03 23:49 ` Ron Economos
2024-10-04 13:38 ` Kexy Biscuit
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=2024100426-wheat-heavily-68d1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=wangyugui@e16-tech.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