From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org, "YunQiang Su" <syq@debian.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] MIPS: process: Remove lazy context flags for new kernel thread
Date: Tue, 21 Nov 2023 12:27:11 +0000 [thread overview]
Message-ID: <c9e2daa2-65a8-445e-bace-ab750f04411a@app.fastmail.com> (raw)
In-Reply-To: <ZVuuqAUJ7f2ELIYW@alpha.franken.de>
在2023年11月20日十一月 下午7:08,Thomas Bogendoerfer写道:
> On Sat, Nov 18, 2023 at 04:36:45PM +0100, Aurelien Jarno wrote:
>> > Anyway, I have been able to test a backport of the patch onto the 5.10
>> > kernel (with minor adjustments) and I confirm it fixes the reported
>> > issue.
>> >
>> > Tested-by: Aurelien Jarno <aurel32@debian.org>
>>
>> It seems that this patch hasn't been merged yet, either in Linus' tree
>> or in the MIPS tree. Is there anything blocking?
>
> sorry, took some time to get really back from vacation...
>
> I don't like the patch doing too much code restructing. I can't
> reproduce on my loongson machine, so I can't test below patch...
I intentionally do code shuffle to match with other arches :-)
To reproduce, you can just install Debian sid and build kitinerary with
sbuild. However, it seems like loongson3_defconfig won't expose this
problem, you'll have to build kernel with Debian's config.
I'll test this patch later today.
Thanks
- Jiaxun
>
> What cmake version do I need and what would be a package to
> reproduce the bug ?
>
> Thomas.
>
[...]
next prev parent reply other threads:[~2023-11-21 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 11:17 Jiaxun Yang
2023-10-26 11:36 ` Philippe Mathieu-Daudé
[not found] ` <ZTvQGs/lEpizUFLh@aurel32.net>
2023-10-27 18:47 ` Aurelien Jarno
2023-11-18 15:36 ` Aurelien Jarno
2023-11-20 19:08 ` Thomas Bogendoerfer
2023-11-21 12:27 ` Jiaxun Yang [this message]
2023-11-21 12:38 ` Thomas Bogendoerfer
2023-11-21 12:44 ` Jiaxun Yang
2023-11-21 12:45 ` Jiaxun Yang
2023-11-21 12:46 ` Thomas Bogendoerfer
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=c9e2daa2-65a8-445e-bace-ab750f04411a@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syq@debian.org \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®