From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] [RFC] linux6.8: disable CONFIG_BLK_DEV_WRITE_MOUNTED
Date: Tue, 30 Apr 2024 01:55:14 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50124@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
There is a new pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages no-write-for-you
https://github.com/void-linux/void-packages/pull/50124
[RFC] linux6.8: disable CONFIG_BLK_DEV_WRITE_MOUNTED
protects against writing directly to block device nodes while they are mounted
A patch file from https://github.com/void-linux/void-packages/pull/50124.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-no-write-for-you-50124.patch --]
[-- Type: text/x-diff, Size: 2026 bytes --]
From 63313ee3f34f76fb1877972a9c57d99010a44f01 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 29 Apr 2024 19:50:20 -0400
Subject: [PATCH] linux6.8: disable CONFIG_BLK_DEV_WRITE_MOUNTED
protects against writing directly to block device nodes while they are mounted
---
srcpkgs/linux6.8/files/arm64-dotconfig | 2 +-
srcpkgs/linux6.8/files/i386-dotconfig | 2 +-
srcpkgs/linux6.8/files/x86_64-dotconfig | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/linux6.8/files/arm64-dotconfig b/srcpkgs/linux6.8/files/arm64-dotconfig
index 0eea6c711dad1b..f179c61ef61c24 100644
--- a/srcpkgs/linux6.8/files/arm64-dotconfig
+++ b/srcpkgs/linux6.8/files/arm64-dotconfig
@@ -926,7 +926,7 @@ CONFIG_BLK_ICQ=y
CONFIG_BLK_DEV_BSGLIB=y
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLK_DEV_INTEGRITY_T10=y
-CONFIG_BLK_DEV_WRITE_MOUNTED=y
+CONFIG_BLK_DEV_WRITE_MOUNTED=n
CONFIG_BLK_DEV_ZONED=y
CONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_DEV_THROTTLING_LOW is not set
diff --git a/srcpkgs/linux6.8/files/i386-dotconfig b/srcpkgs/linux6.8/files/i386-dotconfig
index 7694b33cdd9fa7..7e6c3f359f2748 100644
--- a/srcpkgs/linux6.8/files/i386-dotconfig
+++ b/srcpkgs/linux6.8/files/i386-dotconfig
@@ -892,7 +892,7 @@ CONFIG_BLK_ICQ=y
CONFIG_BLK_DEV_BSGLIB=y
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLK_DEV_INTEGRITY_T10=y
-CONFIG_BLK_DEV_WRITE_MOUNTED=y
+CONFIG_BLK_DEV_WRITE_MOUNTED=n
CONFIG_BLK_DEV_ZONED=y
CONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_DEV_THROTTLING_LOW is not set
diff --git a/srcpkgs/linux6.8/files/x86_64-dotconfig b/srcpkgs/linux6.8/files/x86_64-dotconfig
index 9d35674fffd80f..de14554aae0499 100644
--- a/srcpkgs/linux6.8/files/x86_64-dotconfig
+++ b/srcpkgs/linux6.8/files/x86_64-dotconfig
@@ -969,7 +969,7 @@ CONFIG_BLK_ICQ=y
CONFIG_BLK_DEV_BSGLIB=y
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLK_DEV_INTEGRITY_T10=y
-CONFIG_BLK_DEV_WRITE_MOUNTED=y
+CONFIG_BLK_DEV_WRITE_MOUNTED=n
CONFIG_BLK_DEV_ZONED=y
CONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_DEV_THROTTLING_LOW is not set
next reply other threads:[~2024-04-29 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 23:55 classabbyamp [this message]
2024-04-30 0:26 ` classabbyamp
2024-05-01 9:07 ` [PR PATCH] [Merged]: " classabbyamp
2024-05-04 10:53 ` dkwo
2024-05-04 12:02 ` ahesford
2024-05-04 13:42 ` classabbyamp
2024-05-04 16:07 ` dkwo
2024-05-04 19:10 ` classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50124@inbox.vuxu.org \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).