From: Jack Wang <jinpu.wang@ionos.com>
To: pchelkin@ispras.ru,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Cc: bp@alien8.de, dave.hansen@linux.intel.com,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org,
mark.rutland@arm.com, mhiramat@kernel.org, mingo@redhat.com,
peterz@infradead.org, rostedt@goodmis.org, rppt@kernel.org,
tglx@linutronix.de, x86@kernel.org
Subject: [PATCH 6.1 1/1] x86/modules: Set VM_FLUSH_RESET_PERMS in module_alloc()
Date: Thu, 22 May 2025 14:17:06 +0200 [thread overview]
Message-ID: <682f15c4.170a0220.3893a.e498@mx.google.com> (raw)
In-Reply-To: <20250521165909.834545-1-pchelkin@ispras.ru>
From: Fedor Pchelkin <pchelkin@ispras.ru>
From: Thomas Gleixner <tglx@linutronix.de>
commit 4c4eb3ecc91f4fee6d6bf7cfbc1e21f2e38d19ff upstream.
Instead of resetting permissions all over the place when freeing module
memory tell the vmalloc code to do so. Avoids the exercise for the next
upcoming user.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/r/20220915111143.406703869@infradead.org
Signed-off-by: Fedor Pchelkin <pchelkin@ispras.ru>
I confirm this patch fixed the random crashing ontop of 6.1.139 I've experienced
on our Icelake and Cascadelake servers, servers are working fine after appling
the fix, thx!
Tested-by: Jack Wang <jinpu.wang@ionos.com>
prev parent reply other threads:[~2025-05-22 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 16:59 [PATCH 6.1 0/1] Oopses on module unload seen on 6.1.y Fedor Pchelkin
2025-05-21 16:59 ` [PATCH 6.1 1/1] x86/modules: Set VM_FLUSH_RESET_PERMS in module_alloc() Fedor Pchelkin
2025-05-22 12:17 ` Jack Wang [this message]
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=682f15c4.170a0220.3893a.e498@mx.google.com \
--to=jinpu.wang@ionos.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pchelkin@ispras.ru \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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