From: Richard Weinberger <richard@nod.at> To: linux-mtd@lists.infradead.org Cc: linux-fscrypt@vger.kernel.org, jaegeuk@kernel.org, tytso@mit.edu, linux-unionfs@vger.kernel.org, miklos@szeredi.hu, amir73il@gmail.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, paullawrence@google.com, Richard Weinberger <richard@nod.at> Subject: [PATCH 2/4] fscrypt: Export fscrypt_d_ops Date: Thu, 14 Mar 2019 18:15:57 +0100 [thread overview] Message-ID: <20190314171559.27584-3-richard@nod.at> (raw) In-Reply-To: <20190314171559.27584-1-richard@nod.at> If a filesystem manages dentry operations itself it might want to re-use fscrypt_d_ops. Signed-off-by: Richard Weinberger <richard@nod.at> --- fs/crypto/crypto.c | 1 + fs/crypto/fscrypt_private.h | 1 - include/linux/fscrypt.h | 1 + 3 files changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c index 4dc788e3bc96..8018f8bba50d 100644 --- a/fs/crypto/crypto.c +++ b/fs/crypto/crypto.c @@ -357,6 +357,7 @@ static int fscrypt_d_revalidate(struct dentry *dentry, unsigned int flags) const struct dentry_operations fscrypt_d_ops = { .d_revalidate = fscrypt_d_revalidate, }; +EXPORT_SYMBOL(fscrypt_d_ops); void fscrypt_restore_control_page(struct page *page) { diff --git a/fs/crypto/fscrypt_private.h b/fs/crypto/fscrypt_private.h index 7da276159593..bced1ee4fd64 100644 --- a/fs/crypto/fscrypt_private.h +++ b/fs/crypto/fscrypt_private.h @@ -125,7 +125,6 @@ extern int fscrypt_do_page_crypto(const struct inode *inode, gfp_t gfp_flags); extern struct page *fscrypt_alloc_bounce_page(struct fscrypt_ctx *ctx, gfp_t gfp_flags); -extern const struct dentry_operations fscrypt_d_ops; extern void __printf(3, 4) __cold fscrypt_msg(struct super_block *sb, const char *level, const char *fmt, ...); diff --git a/include/linux/fscrypt.h b/include/linux/fscrypt.h index 7139a110ac4f..2b9577e4707f 100644 --- a/include/linux/fscrypt.h +++ b/include/linux/fscrypt.h @@ -231,6 +231,7 @@ extern int __fscrypt_encrypt_symlink(struct inode *inode, const char *target, extern const char *fscrypt_get_symlink(struct inode *inode, const void *caddr, unsigned int max_size, struct delayed_call *done); +extern const struct dentry_operations fscrypt_d_ops; #else /* !CONFIG_FS_ENCRYPTION */ static inline bool fscrypt_has_encryption_key(const struct inode *inode) -- 2.21.0
WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at> To: linux-mtd@lists.infradead.org Cc: tytso@mit.edu, miklos@szeredi.hu, Richard Weinberger <richard@nod.at>, amir73il@gmail.com, linux-unionfs@vger.kernel.org, linux-kernel@vger.kernel.org, paullawrence@google.com, linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org Subject: [PATCH 2/4] fscrypt: Export fscrypt_d_ops Date: Thu, 14 Mar 2019 18:15:57 +0100 [thread overview] Message-ID: <20190314171559.27584-3-richard@nod.at> (raw) In-Reply-To: <20190314171559.27584-1-richard@nod.at> If a filesystem manages dentry operations itself it might want to re-use fscrypt_d_ops. Signed-off-by: Richard Weinberger <richard@nod.at> --- fs/crypto/crypto.c | 1 + fs/crypto/fscrypt_private.h | 1 - include/linux/fscrypt.h | 1 + 3 files changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c index 4dc788e3bc96..8018f8bba50d 100644 --- a/fs/crypto/crypto.c +++ b/fs/crypto/crypto.c @@ -357,6 +357,7 @@ static int fscrypt_d_revalidate(struct dentry *dentry, unsigned int flags) const struct dentry_operations fscrypt_d_ops = { .d_revalidate = fscrypt_d_revalidate, }; +EXPORT_SYMBOL(fscrypt_d_ops); void fscrypt_restore_control_page(struct page *page) { diff --git a/fs/crypto/fscrypt_private.h b/fs/crypto/fscrypt_private.h index 7da276159593..bced1ee4fd64 100644 --- a/fs/crypto/fscrypt_private.h +++ b/fs/crypto/fscrypt_private.h @@ -125,7 +125,6 @@ extern int fscrypt_do_page_crypto(const struct inode *inode, gfp_t gfp_flags); extern struct page *fscrypt_alloc_bounce_page(struct fscrypt_ctx *ctx, gfp_t gfp_flags); -extern const struct dentry_operations fscrypt_d_ops; extern void __printf(3, 4) __cold fscrypt_msg(struct super_block *sb, const char *level, const char *fmt, ...); diff --git a/include/linux/fscrypt.h b/include/linux/fscrypt.h index 7139a110ac4f..2b9577e4707f 100644 --- a/include/linux/fscrypt.h +++ b/include/linux/fscrypt.h @@ -231,6 +231,7 @@ extern int __fscrypt_encrypt_symlink(struct inode *inode, const char *target, extern const char *fscrypt_get_symlink(struct inode *inode, const void *caddr, unsigned int max_size, struct delayed_call *done); +extern const struct dentry_operations fscrypt_d_ops; #else /* !CONFIG_FS_ENCRYPTION */ static inline bool fscrypt_has_encryption_key(const struct inode *inode) -- 2.21.0 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-03-14 17:23 UTC|newest] Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-13 12:31 overlayfs vs. fscrypt Richard Weinberger 2019-03-13 12:31 ` Richard Weinberger 2019-03-13 12:36 ` Miklos Szeredi 2019-03-13 12:47 ` Richard Weinberger 2019-03-13 12:47 ` Richard Weinberger 2019-03-13 12:58 ` Miklos Szeredi 2019-03-13 13:00 ` Richard Weinberger 2019-03-13 13:00 ` Richard Weinberger 2019-03-13 13:24 ` Miklos Szeredi 2019-03-13 13:32 ` Richard Weinberger 2019-03-13 13:32 ` Richard Weinberger 2019-03-13 14:26 ` Amir Goldstein 2019-03-13 15:16 ` Theodore Ts'o 2019-03-13 15:30 ` Richard Weinberger 2019-03-13 15:30 ` Richard Weinberger 2019-03-13 15:36 ` James Bottomley 2019-03-13 15:51 ` Eric Biggers 2019-03-13 16:13 ` James Bottomley 2019-03-13 16:24 ` Richard Weinberger 2019-03-13 16:44 ` Theodore Ts'o 2019-03-13 17:45 ` James Bottomley 2019-03-13 18:58 ` Theodore Ts'o 2019-03-13 19:17 ` James Bottomley 2019-03-13 19:57 ` Eric Biggers 2019-03-13 20:06 ` James Bottomley 2019-03-13 20:25 ` Eric Biggers 2019-03-13 21:04 ` James Bottomley 2019-03-13 22:13 ` Eric Biggers 2019-03-13 22:29 ` James Bottomley 2019-03-13 22:58 ` Eric Biggers 2019-03-13 16:06 ` Al Viro 2019-03-13 16:44 ` Eric Biggers 2019-03-13 19:19 ` Al Viro 2019-03-13 19:43 ` Eric Biggers 2019-03-13 15:30 ` Eric Biggers 2019-03-13 15:30 ` Eric Biggers 2019-03-13 20:33 ` Richard Weinberger 2019-03-13 20:33 ` Richard Weinberger 2019-03-13 22:26 ` Eric Biggers 2019-03-13 22:26 ` Eric Biggers 2019-03-13 22:42 ` Richard Weinberger 2019-03-14 7:34 ` Miklos Szeredi 2019-03-14 17:15 ` [RFC] fscrypt_key_required mount option Richard Weinberger 2019-03-14 17:15 ` Richard Weinberger 2019-03-14 17:15 ` [PATCH 1/4] fscrypt: Implement FS_CFLG_OWN_D_OPS Richard Weinberger 2019-03-14 17:15 ` Richard Weinberger 2019-03-14 17:15 ` Richard Weinberger [this message] 2019-03-14 17:15 ` [PATCH 2/4] fscrypt: Export fscrypt_d_ops Richard Weinberger 2019-03-14 17:15 ` [PATCH 3/4] ubifs: Simplify fscrypt_get_encryption_info() error handling Richard Weinberger 2019-03-14 17:15 ` Richard Weinberger 2019-03-14 17:15 ` [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required Richard Weinberger 2019-03-14 17:15 ` Richard Weinberger 2019-03-14 17:49 ` Eric Biggers 2019-03-14 17:49 ` Eric Biggers 2019-03-14 20:54 ` Richard Weinberger 2019-03-14 20:54 ` Richard Weinberger 2019-03-14 23:07 ` Theodore Ts'o 2019-03-14 23:07 ` Theodore Ts'o 2019-03-15 0:26 ` Unsubscribe Shane Volpe 2019-03-15 7:48 ` [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required Richard Weinberger 2019-03-15 7:48 ` Richard Weinberger 2019-03-15 13:51 ` Theodore Ts'o 2019-03-15 13:51 ` Theodore Ts'o 2019-03-15 13:51 ` Theodore Ts'o 2019-03-15 13:59 ` Richard Weinberger 2019-03-15 13:59 ` Richard Weinberger 2019-03-14 23:15 ` James Bottomley 2019-03-14 23:15 ` James Bottomley 2019-03-14 23:42 ` Theodore Ts'o 2019-03-14 23:42 ` Theodore Ts'o 2019-03-14 23:55 ` James Bottomley 2019-03-14 23:55 ` James Bottomley 2019-03-13 15:01 ` overlayfs vs. fscrypt Eric Biggers 2019-03-13 15:01 ` Eric Biggers 2019-03-13 16:11 ` Al Viro 2019-03-13 16:33 ` 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=20190314171559.27584-3-richard@nod.at \ --to=richard@nod.at \ --cc=amir73il@gmail.com \ --cc=jaegeuk@kernel.org \ --cc=linux-fscrypt@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=linux-unionfs@vger.kernel.org \ --cc=miklos@szeredi.hu \ --cc=paullawrence@google.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.