Linux-Fsdevel Archive on lore.kernel.org help / color / mirror / Atom feed
From: Eric Biggers <email@example.com> To: Daniel Rosenberg <firstname.lastname@example.org> Cc: "Theodore Y . Ts'o" <email@example.com>, Jaegeuk Kim <firstname.lastname@example.org>, Andreas Dilger <email@example.com>, Chao Yu <firstname.lastname@example.org>, Alexander Viro <email@example.com>, Richard Weinberger <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, Gabriel Krisman Bertazi <email@example.com>, firstname.lastname@example.org Subject: Re: [PATCH 0/5] Add support for Encryption and Casefolding in F2FS Date: Tue, 22 Sep 2020 06:59:40 -0700 [thread overview] Message-ID: <20200922135940.GB5599@sol.localdomain> (raw) In-Reply-To: <email@example.com> On Tue, Sep 22, 2020 at 03:48:02AM -0700, Daniel Rosenberg wrote: > These patches are on top of the f2fs dev branch > > F2FS currently supports casefolding and encryption, but not at > the same time. These patches aim to rectify that. In a later follow up, > this will be added for Ext4 as well. I've included one ext4 patch from > the previous set since it isn't in the f2fs branch, but is needed for the > fscrypt changes. > > The f2fs-tools changes have already been applied. > > Since both fscrypt and casefolding require their own dentry operations, > I've moved the responsibility of setting the dentry operations from fscrypt > to the filesystems and provided helper functions that should work for most > cases. > > These are a follow-up to the previously sent patch set > "[PATCH v12 0/4] Prepare for upcoming Casefolding/Encryption patches" > > Daniel Rosenberg (5): > ext4: Use generic casefolding support > fscrypt: Export fscrypt_d_revalidate > libfs: Add generic function for setting dentry_ops > fscrypt: Have filesystems handle their d_ops > f2fs: Handle casefolding with Encryption I only received the cover letter, not the actual patches. Same for the lore archives; they only have the cover letter. - Eric
next prev parent reply other threads:[~2020-09-22 13:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-22 10:48 [PATCH 0/5] Add support for Encryption and Casefolding in F2FS Daniel Rosenberg 2020-09-22 13:59 ` Eric Biggers [this message] 2020-09-22 16:01 ` Jaegeuk Kim 2020-09-23 1:01 Daniel Rosenberg 2020-11-09 22:50 ` Eric Biggers
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=20200922135940.GB5599@sol.localdomain \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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: linkBe 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).