From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jari Ruusu <jariruusu@protonmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Zizhi Wo <wozizhi@huaweicloud.com>
Subject: Re: [PATCH 6.12 000/565] 6.12.58-rc1 review
Date: Fri, 21 Nov 2025 10:36:54 +0100 [thread overview]
Message-ID: <2025112145-cobbler-reattach-8fb2@gregkh> (raw)
In-Reply-To: <zuLBWV-yhJXc0iM4l5T-O63M-kKmI2FlUSVgZl6B3WubvFEHRbBYQyhKsRcK4YyKk_iePF4STJihe7hx5H3KCU2KblG32oXwsxn9tzpTm5w=@protonmail.com>
On Tue, Nov 11, 2025 at 06:38:21AM +0000, Jari Ruusu wrote:
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > This is the start of the stable review cycle for the 6.12.58 release.
> > There are 565 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.
> [SNIP]
> > Zizhi Wo <wozizhi@huaweicloud.com>
> > tty/vt: Add missing return value for VT_RESIZE in vt_ioctl()
>
> Locking seems to be messed up in backport of above mentioned patch.
>
> That patch is viewable here:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=queue/6.12&id=884e9ac7361b2a3c3a7a90ffaf541ffc2ded6738
>
> Upstream uses guard() locking:
> | case VT_RESIZE:
> | {
> | ....
> | guard(console_lock)();
> | ^^^^^^^^^^^^^^^^^^^^^-------this generates auto-unlock code
> | ....
> | ret = __vc_resize(vc_cons[i].d, cc, ll, true);
> | if (ret)
> | return ret;
> | ^^^^^^^^^^----------this releases console lock
> | ....
> | break;
> | }
>
> Older stable branches use old-school locking:
> | case VT_RESIZE:
> | {
> | ....
> | console_lock();
> | ....
> | ret = __vc_resize(vc_cons[i].d, cc, ll, true);
> | if (ret)
> | return ret;
> | ^^^^^^^^^^----------this does not release console lock
> | ....
> | console_unlock();
> | break;
> | }
>
> Backporting upstream fixes that use guard() locking to older stable
> branches that use old-school locking need "extra sports".
>
> Please consider dropping or fixing above mentioned patch.
Can you provide a fixed up patch?
thanks,
greg k-h
next prev parent reply other threads:[~2025-11-21 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 6:38 Jari Ruusu
2025-11-21 9:36 ` Greg Kroah-Hartman [this message]
2025-11-22 7:28 ` Jari Ruusu
-- strict thread matches above, loose matches on Subject: below --
2025-11-26 12:21 Jari Ruusu
2025-11-11 0:37 Greg Kroah-Hartman
2025-11-11 18:00 ` Shuah Khan
2025-11-11 19:47 ` Slade Watkins
2025-11-11 20:41 ` Shuah Khan
2025-11-25 12:47 ` Pavel Machek
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=2025112145-cobbler-reattach-8fb2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jariruusu@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wozizhi@huaweicloud.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
all inboxes | Powered by JetHome®