From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Mike Rapoport <rppt@kernel.org>,
syzbot <syzbot+ee7ecfcd0e3f185e835a@syzkaller.appspotmail.com>,
"Denis V. Lunev" <den@openvz.org>,
Vishal Moola <vishal.moola@gmail.com>,
dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
luto@kernel.org, mingo@redhat.com, peterz@infradead.org,
sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com,
tglx@kernel.org, x86@kernel.org
Subject: Re: [syzbot] [kernel?] linux-next test error: WARNING: locking bug in change_page_attr_set_clr
Date: Tue, 21 Jul 2026 16:45:26 +0100 [thread overview]
Message-ID: <al-QA7L9qFcDr-TR@lucifer> (raw)
In-Reply-To: <20260721150547.GCal-Ky_X99ULTLK2Q@fat_crate.local>
On Tue, Jul 21, 2026 at 08:05:47AM -0700, Borislav Petkov wrote:
> On Tue, Jul 21, 2026 at 03:03:41PM +0100, Lorenzo Stoakes (ARM) wrote:
> > You mean the series that changes core mm and has strict dependencies on core mm
> > changes and solves issues elsewhere than x86 CPA, that one should have gone
> > through the x86 tree?
>
> We do immutable branches for things like that. For example.
Coming soon to mm :)
>
> Bottom line is, there needs to be synchronization across trees when they touch
> the same file.
Yeah completely agreed as discussed off list :) comms is key.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
Cheers, Lorenzo
next prev parent reply other threads:[~2026-07-21 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 16:59 [syzbot] [kernel?] linux-next test error: WARNING: locking bug in change_page_attr_set_clr syzbot
2026-07-21 2:24 ` Borislav Petkov
2026-07-21 10:35 ` Mike Rapoport
2026-07-21 12:39 ` Lorenzo Stoakes (ARM)
2026-07-21 13:53 ` Borislav Petkov
2026-07-21 14:03 ` Lorenzo Stoakes (ARM)
2026-07-21 15:05 ` Borislav Petkov
2026-07-21 15:45 ` Lorenzo Stoakes (ARM) [this message]
2026-07-21 14:10 ` Lorenzo Stoakes (ARM)
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=al-QA7L9qFcDr-TR@lucifer \
--to=ljs@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=den@openvz.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+ee7ecfcd0e3f185e835a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@kernel.org \
--cc=vishal.moola@gmail.com \
--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