From: Guenter Roeck <linux@roeck-us.net>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/mm: Fix pti_clone_entry_text() for i386
Date: Mon, 5 Aug 2024 21:52:06 -0700 [thread overview]
Message-ID: <e541b49b-9cc2-47bb-b283-2de70ae3a359@roeck-us.net> (raw)
In-Reply-To: <172250973153.2215.13116668336106656424.tip-bot2@tip-bot2>
Hi Peter,
On Thu, Aug 01, 2024 at 10:55:31AM -0000, tip-bot2 for Peter Zijlstra wrote:
> The following commit has been merged into the x86/urgent branch of tip:
>
> Commit-ID: 49947e7aedfea2573bada0c95b85f6c2363bef9f
> Gitweb: https://git.kernel.org/tip/49947e7aedfea2573bada0c95b85f6c2363bef9f
> Author: Peter Zijlstra <peterz@infradead.org>
> AuthorDate: Thu, 01 Aug 2024 12:42:25 +02:00
> Committer: Peter Zijlstra <peterz@infradead.org>
> CommitterDate: Thu, 01 Aug 2024 12:48:23 +02:00
>
> x86/mm: Fix pti_clone_entry_text() for i386
>
> While x86_64 has PMD aligned text sections, i386 does not have this
> luxery. Notably ALIGN_ENTRY_TEXT_END is empty and _etext has PAGE
> alignment.
>
> This means that text on i386 can be page granular at the tail end,
> which in turn means that the PTI text clones should consistently
> account for this.
>
> Make pti_clone_entry_text() consistent with pti_clone_kernel_text().
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
With this patch in the tree, some of my qemu tests (those with PAE enabled)
report several WARNING backtraces.
WARNING: CPU: 0 PID: 1 at arch/x86/mm/pti.c:256 pti_clone_pgtable+0x298/0x2dc
WARNING: CPU: 0 PID: 1 at arch/x86/mm/pti.c:394 pti_clone_pgtable+0x29a/0x2dc
The backtraces are repeated multiple times.
Please see
https://kerneltests.org/builders/qemu-x86-master/builds/253/steps/qemubuildcommand/logs/stdio
for complete logs.
Bisect log is attached. Reverting this patch fixes the problem.
Thanks,
Guenter
---
# bad: [de9c2c66ad8e787abec7c9d7eff4f8c3cdd28aed] Linux 6.11-rc2
# good: [defaf1a2113a22b00dfa1abc0fd2014820eaf065] Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
git bisect start 'v6.11-rc2' 'defaf1a2113a'
# good: [953f776459a83f00ac940dd67c96d226d7041550] Merge tag 'irq-urgent-2024-08-04' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
git bisect good 953f776459a83f00ac940dd67c96d226d7041550
# good: [61ca6c78295e242d4b681003112bfcdc54597489] Merge tag 'timers-urgent-2024-08-04' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
git bisect good 61ca6c78295e242d4b681003112bfcdc54597489
# good: [41e71dbb0e0a0fe214545fe64af031303a08524c] x86/mm: Fix pti_clone_pgtable() alignment assumption
git bisect good 41e71dbb0e0a0fe214545fe64af031303a08524c
# bad: [dd35a0933269c636635b6af89dc6fa1782791e56] x86/uaccess: Zero the 8-byte get_range case on failure on 32-bit
git bisect bad dd35a0933269c636635b6af89dc6fa1782791e56
# bad: [3db03fb4995ef85fc41e86262ead7b4852f4bcf0] x86/mm: Fix pti_clone_entry_text() for i386
git bisect bad 3db03fb4995ef85fc41e86262ead7b4852f4bcf0
# first bad commit: [3db03fb4995ef85fc41e86262ead7b4852f4bcf0] x86/mm: Fix pti_clone_entry_text() for i386
next prev parent reply other threads:[~2024-08-06 4:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 10:55 tip-bot2 for Peter Zijlstra
2024-08-06 4:52 ` Guenter Roeck [this message]
2024-08-06 8:50 ` Peter Zijlstra
2024-08-06 14:25 ` Guenter Roeck
2024-08-06 14:56 ` Peter Zijlstra
2024-08-06 15:05 ` Peter Zijlstra
2024-08-06 15:46 ` Peter Zijlstra
2024-08-06 15:59 ` Peter Zijlstra
2024-08-06 16:42 ` Guenter Roeck
2024-08-06 18:48 ` Peter Zijlstra
2024-08-06 19:12 ` Guenter Roeck
2024-08-06 20:16 ` Guenter Roeck
2024-08-07 13:51 ` [tip: x86/urgent] x86/mm: Fix PTI for i386 some more tip-bot2 for Thomas Gleixner
2024-08-01 13:03 [tip: x86/urgent] x86/mm: Fix pti_clone_entry_text() for i386 tip-bot2 for Peter Zijlstra
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=e541b49b-9cc2-47bb-b283-2de70ae3a359@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®