ecryptfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: ecryptfs@vger.kernel.org
Cc: code@tyhicks.com, brauner@kernel.org
Subject: [PATCH V2 0/2] ecryptfs: convert to the new mount API
Date: Mon, 28 Oct 2024 09:32:37 -0500	[thread overview]
Message-ID: <20241028143359.605061-1-sandeen@redhat.com> (raw)

This is lightly tested with the kernel tests present in ecryptfs-utils,
but it could certainly use a bit more testing and review, particularly
with invalid mount option sets.

This one is a little unique compared to other filesystems in that I
allocate both an fs context and the *sbi in .init_fs_context; the *sbi
is long-lived, and the context is only present during the initial mount.

Allocating sbi with the filesystem context means we can set options
into it directly, rather than needing to do it after parsing. And it's
particularly simple to do it this way given that there is no remount.

I could squash these two patches into one if you prefer, but
I thought maybe breaking out the first change made review a little
easier.

V2: Fix whitespace issues and remove an accidental double semicolon
    in the 2nd patch.

Thanks,
-Eric


             reply	other threads:[~2024-10-28 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 14:32 Eric Sandeen [this message]
2024-10-28 14:32 ` [PATCH V2 1/2] ecryptfs: Factor out mount option validation Eric Sandeen
2024-10-28 14:32 ` [PATCH V2 2/2] ecryptfs: Convert ecryptfs to use the new mount API Eric Sandeen
2024-10-30 22:03   ` Tyler Hicks
2024-11-06 10:32 ` [PATCH V2 0/2] ecryptfs: convert to " Christian Brauner

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=20241028143359.605061-1-sandeen@redhat.com \
    --to=sandeen@redhat.com \
    --cc=brauner@kernel.org \
    --cc=code@tyhicks.com \
    --cc=ecryptfs@vger.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;
as well as URLs for NNTP newsgroup(s).