From: Jiri Slaby <jirislaby@kernel.org>
To: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org
Cc: Steffen Dirkwinkel <lists@steffen.cc>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
Pedro Falcato <pfalcato@suse.de>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Atish Patra <atishp@meta.com>, Nikunj A Dadhania <nikunj@amd.com>,
stable@vger.kernel.org, x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/alternative: Exclude text poking against change_page_attr()
Date: Tue, 1 Sep 2026 08:16:28 +0200 [thread overview]
Message-ID: <4201eac9-297b-4672-8e7f-62e99dd13eb8@kernel.org> (raw)
In-Reply-To: <178821524520.3717435.12731475498671524229.tip-bot2@tip-bot2>
On 01. 09. 26, 0:27, tip-bot2 for Pedro Falcato wrote:
> The following commit has been merged into the x86/urgent branch of tip:
>
> Commit-ID: 1c4d1c070d734b241728378c0f79950c23a10883
> Gitweb: https://git.kernel.org/tip/1c4d1c070d734b241728378c0f79950c23a10883
Was it dropped in the meantime? Gitweb says:
Object 1c4d1c070d734b241728378c0f79950c23a10883 is not reachable from
any reference in this repository
$ git rev-parse tip/x86/urgent
477cf5cd1f698053df7426b7b8d9339e85e00946
$ git branch -r --contains 1c4d1c070d734b241728378c0f79950c23a10883
$
Despite I managed to download it at some point though:
$ git show --oneline -s 1c4d1c070d734b241728378c0f79950c23a10883
1c4d1c070d73 x86/alternative: Exclude text poking against change_page_attr()
What's going on with tip today?
> Author: Pedro Falcato <pfalcato@suse.de>
> AuthorDate: Thu, 13 Aug 2026 12:01:26 +03:00
> Committer: Dave Hansen <dave.hansen@linux.intel.com>
> CommitterDate: Mon, 31 Aug 2026 15:17:35 -07:00
>
> x86/alternative: Exclude text poking against change_page_attr()
thanks,
--
js
suse labs
next prev parent reply other threads:[~2026-09-01 6:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 9:01 [PATCH v2 0/5] x86/mm/pat: CPA fixes Mike Rapoport
2026-08-13 9:01 ` [PATCH v2 1/5] x86/mm/pat: acquire init_mm write lock on collapse to avoid UAF Mike Rapoport
2026-08-31 22:27 ` [tip: x86/urgent] x86/mm/pat: Acquire " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-01 6:03 ` Jiri Slaby
2026-09-01 7:10 ` Lorenzo Stoakes (ARM)
2026-09-01 23:36 ` Dave Hansen
2026-09-02 6:53 ` Lorenzo Stoakes (ARM)
2026-09-02 18:33 ` tip-bot2 for Lorenzo Stoakes (ARM)
2026-08-13 9:01 ` [PATCH v2 2/5] x86/mm/pat: acquire init_mm read lock on attribute change " Mike Rapoport
2026-08-31 22:27 ` [tip: x86/urgent] x86/mm/pat: Acquire " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-01 6:05 ` Jiri Slaby
2026-09-01 7:20 ` Lorenzo Stoakes (ARM)
2026-09-01 13:46 ` Dave Hansen
2026-09-02 18:33 ` tip-bot2 for Lorenzo Stoakes (ARM)
2026-08-13 9:01 ` [PATCH v2 3/5] x86/alternative: exclude text poking against change_page_attr() Mike Rapoport
2026-08-25 9:37 ` Jiri Slaby
2026-08-31 22:27 ` [tip: x86/urgent] x86/alternative: Exclude " tip-bot2 for Pedro Falcato
2026-09-01 6:16 ` Jiri Slaby [this message]
2026-09-01 7:18 ` Lorenzo Stoakes (ARM)
2026-09-01 7:22 ` Jiri Slaby
2026-09-01 7:24 ` Lorenzo Stoakes (ARM)
2026-09-02 18:33 ` tip-bot2 for Pedro Falcato
2026-08-13 9:01 ` [PATCH v2 4/5] x86/mm/pat: allocate split page tables as kernel page tables Mike Rapoport
2026-08-31 22:27 ` [tip: x86/urgent] x86/mm/pat: Allocate " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-02 18:33 ` tip-bot2 for Lorenzo Stoakes (ARM)
2026-08-13 9:01 ` [PATCH v2 5/5] x86/mm/pat: fix effective RW computation in lookup_address_in_pgd_attr() Mike Rapoport (Microsoft)
2026-08-13 9:45 ` Lorenzo Stoakes (ARM)
2026-08-31 22:27 ` [tip: x86/urgent] x86/mm/pat: Fix " tip-bot2 for Mike Rapoport (Microsoft)
2026-09-02 18:33 ` tip-bot2 for Mike Rapoport (Microsoft)
2026-09-05 4:42 ` Nathan Chancellor
2026-08-13 15:05 ` [PATCH v2 0/5] x86/mm/pat: CPA fixes Nikunj A. Dadhania
2026-08-13 15:07 ` Lorenzo Stoakes (ARM)
2026-08-13 15:23 ` Pedro Falcato
2026-08-13 17:13 ` Andrew Morton
2026-08-25 7:12 ` Atish Patra
2026-08-25 7:31 ` Lorenzo Stoakes (ARM)
2026-08-25 20:05 ` Atish Patra
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=4201eac9-297b-4672-8e7f-62e99dd13eb8@kernel.org \
--to=jirislaby@kernel.org \
--cc=atishp@meta.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lists@steffen.cc \
--cc=ljs@kernel.org \
--cc=nikunj@amd.com \
--cc=pfalcato@suse.de \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.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®