From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: [PATCHSET] e2scrub: fix some problems
Date: Fri, 15 Dec 2023 14:55:54 -0800 [thread overview]
Message-ID: <170268089742.2679199.16836622895526209331.stgit@frogsfrogsfrogs> (raw)
Hi all,
Here's a couple of fixes for online fsck: First, fix path escaping where
systemd units are involved, so that everything works consistently.
Second, add a udev rule that hints very strongly to application software
that it should not auto-mount ext filesystems without asking.
If you're going to start using this code, I strongly recommend pulling
from my git trees, which are linked below.
Comments and questions are, as always, welcome.
e2fsprogs git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/e2fsprogs.git/log/?h=e2scrub-fixes
---
scrub/Makefile.in | 12 ++++++++++--
scrub/e2scrub@.service.in | 4 ++--
scrub/e2scrub_all.in | 20 ++++----------------
scrub/e2scrub_fail.in | 10 +++++-----
scrub/e2scrub_fail@.service.in | 4 ++--
scrub/ext4.rules.in | 13 +++++++++++++
6 files changed, 36 insertions(+), 27 deletions(-)
create mode 100644 scrub/ext4.rules.in
next reply other threads:[~2023-12-15 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 22:55 Darrick J. Wong [this message]
2023-12-15 22:56 ` [PATCH 1/2] e2scrub: fix pathname escaping across all service definitions Darrick J. Wong
2023-12-15 22:56 ` [PATCH 2/2] e2fsprogs: don't allow udisks to automount ext4 filesystems with no prompt Darrick J. Wong
2023-12-31 20:39 ` [PATCH 3/2] e2scrub_fail: move executable script to /usr/libexec Darrick J. Wong
2023-12-31 21:37 ` Neal Gompa
2024-01-10 5:57 ` [PATCH 4/2] debian: don't restart e2scrub_all when upgrading package Darrick J. Wong
2024-01-10 5:58 ` [RFC PATCH 6/2] e2scrub: skip filesystems that don't have journals Darrick J. Wong
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=170268089742.2679199.16836622895526209331.stgit@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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