Ecryptfs
[Prev Page][Next Page]
- [PATCH 23/26] iscsi-target: Use shash and ahash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 24/26] nfsd: Use shash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 25/26] sctp: Use shash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 26/26] tcp: Use ahash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 19/26] ipsec: Use skcipher and ahash when probing algorithms
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 16/26] libceph: Use skcipher
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 14/26] KEYS: Use skcipher
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 12/26] sunrpc: Use skcipher and ahash/shash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 11/26] f2fs: Use skcipher
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 5/26] orinoco: Use ahash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 2/26] ppp_mppe: Use skcipher and ahash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 0/26] crypto: Use skcipher and ahash/shash where possible
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- how to retrun different size to different process when I use ecryptfs
- From: zhangzhilei <sdhzdmzzl@xxxxxxxx>
- Re: Key derivation and passprhase wrapping
- From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
- Re: Key derivation and passprhase wrapping
- From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
- Re: bcrypt or other key derivation algorithm
- From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
- Re: Key derivation and passprhase wrapping
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: bcrypt or other key derivation algorithm
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: bcrypt or other key derivation algorithm
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: bcrypt or other key derivation algorithm
- From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
- Re: bcrypt or other key derivation algorithm
- From: Sylvain Pelissier <sylvain.pelissier@xxxxxxxxx>
- bcrypt or other key derivation algorithm
- From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
- Key derivation and passprhase wrapping
- From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: andreym@xxxxxxxxxxxxxx
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: andreym@xxxxxxxxxxxxxx
- Re: An new, fast and "unbreakable" encryption algorithm
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- An new, fast and "unbreakable" encryption algorithm
- From: Ismail Kizir <ikizir@xxxxxxxxx>
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: andreym@xxxxxxxxxxxxxx
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: andreym@xxxxxxxxxxxxxx
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: andreym@xxxxxxxxxxxxxx
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: andreym@xxxxxxxxxxxxxx
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: andreym@xxxxxxxxxxxxxx
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: andreym@xxxxxxxxxxxxxx
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: kbuild test robot <lkp@xxxxxxxxx>
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: kbuild test robot <lkp@xxxxxxxxx>
- Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: Andrey Markovytch <andreym@xxxxxxxxxxxxxx>
- [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
- From: Andrey Markovytch <andreym@xxxxxxxxxxxxxx>
- [PATCH 6/6] KEYS: Merge the type-specific data with the payload data
- From: David Howells <dhowells@xxxxxxxxxx>
- Re: [PATCH 28/39] ecryptfs: drop null test before destroy functions
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 28/39] ecryptfs: drop null test before destroy functions
- From: Julia Lawall <julia.lawall@xxxxxxx>
- Re: [PATCH 28/39] ecryptfs: drop null test before destroy functions
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 00/39] drop null test before destroy functions
- From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
- [PATCH 00/39] drop null test before destroy functions
- From: Julia Lawall <Julia.Lawall@xxxxxxx>
- [PATCH 28/39] ecryptfs: drop null test before destroy functions
- From: Julia Lawall <Julia.Lawall@xxxxxxx>
- [GIT PULL] eCryptfs fixes for 4.3-rc1
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH V1 Resend 07/10] fs: Drop unlikely before IS_ERR(_OR_NULL)
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH V1 Resend 07/10] fs: Drop unlikely before IS_ERR(_OR_NULL)
- From: Steve French <smfrench@xxxxxxxxx>
- [PATCH V1 Resend 07/10] fs: Drop unlikely before IS_ERR(_OR_NULL)
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- [PATCH V1 Resend 08/11] fs: Drop unlikely before IS_ERR(_OR_NULL)
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: [PATCH] eCryptfs: Delete a check before the function call "key_put"
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Invalidate dcache entries when lower i_nlink is zero
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
- From: Richard Weinberger <richard@xxxxxx>
- Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
- From: Richard Weinberger <richard@xxxxxx>
- Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
- From: Richard Weinberger <richard@xxxxxx>
- Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [RFC][PATCH] ecryptfs: Allow only one instance per lower path
- From: Richard Weinberger <richard@xxxxxx>
- Re: [PATCH 12/15] fs: Drop unlikely before IS_ERR(_OR_NULL)
- From: David Howells <dhowells@xxxxxxxxxx>
- [PATCH 12/15] fs: Drop unlikely before IS_ERR(_OR_NULL)
- From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
- Re: Problem "cracking" a key_sig
- From: Marc Peña Segarra <segarrra@xxxxxxxxx>
- Re: Problem "cracking" a key_sig
- From: "Wiest, Damian" <damian.wiest@xxxxxxxxxxxx>
- Re: Problem "cracking" a key_sig
- From: "Wiest, Damian" <damian.wiest@xxxxxxxxxxxx>
- Fwd: Problem "cracking" a key_sig
- From: Marc Peña Segarra <segarrra@xxxxxxxxx>
- [PATCH] eCryptfs: Delete a check before the function call "key_put"
- From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [f2fs-dev] [PATCH v2] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [f2fs-dev] [PATCH v2] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
- From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
- ecryptfs access restrictions
- From: otherthan company <otherthancompany@xxxxxxxxx>
- Re: Way to decrypt an encrypted /home
- From: Pablo Castellano <pablo@xxxxxxxx>
- Re: Way to decrypt an encrypted /home
- From: Marc de Verdelhan <mdeverdelhan@xxxxxxxxx>
- Re: Way to decrypt an encrypted /home
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Way to decrypt an encrypted /home
- From: Marc de Verdelhan <mdeverdelhan@xxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 4.0-rc3
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: don't pass fs-specific ioctl commands through
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: ensure copy to crypt_stat->cipher does not overrun
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: ensure copy to crypt_stat->cipher does not overrun
- From: Colin King <colin.king@xxxxxxxxxxxxx>
- Re: Changing salt value
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Changing salt value
- From: Sylvain Pelissier <sylvain.pelissier@xxxxxxxxx>
- Re: Changing salt value
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Changing salt value
- From: Sylvain Pelissier <sylvain.pelissier@xxxxxxxxx>
- small buffer overflow in ecryptfs_new_file_context()
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
- Re: 32-byte encryption key for ecryptfs-setup-private ?
- From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
- 32-byte encryption key for ecryptfs-setup-private ?
- From: Eric Lan <tenoreamer@xxxxxxxxx>
- Feature Request: solving too long filenames
- From: Eric Lan <tenoreamer@xxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.19-rc1
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- ecryptfs & error opening lower file for lower_dentry on ZFS volumes with ZFS snapshots
- From: "Alex Braunegg" <alex.braunegg@xxxxxxxxx>
- Re: [PATCH] eCryptfs: Allocate sufficient buffer space for encrypted filename decoding
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Remove buggy and unnecessary write in file name decode routine
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Remove buggy and unnecessary write in file name decode routine
- From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
- Re: [PATCH] eCryptfs: Allocate sufficient buffer space for encrypted filename decoding
- From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
- Re: PROBLEM: apparent out-of-bounds memory write in fs/ecryptfs/crypto.c
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- [PATCH] eCryptfs: Allocate sufficient buffer space for encrypted filename decoding
- From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
- PROBLEM: apparent out-of-bounds memory write in fs/ecryptfs/crypto.c
- From: Dmitry Chernenkov <dmitryc@xxxxxxxxxx>
- [PATCH 16/56] fs/encryptfs: support compiling out splice
- From: Pieter Smith <pieter@xxxxxxxxxx>
- AW: BUG() in ecryptfs_send_miscdev()
- From: Anna Fischer <a.fischer@xxxxxxxxxx>
- BUG() in ecryptfs_send_miscdev()
- From: Anna Fischer <a.fischer@xxxxxxxxxx>
- [PATCH] eCryptfs: Remove unnecessary casts when parsing packet lengths
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: is size correct in ecryptfs_parse_packet_length()
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
- Re: is size correct in ecryptfs_parse_packet_length()
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- is size correct in ecryptfs_parse_packet_length()
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
- Re: [PATCH 3/4] ecryptfs: add fadvise/set_flags calbacks
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- [PATCH 3/4] ecryptfs: add fadvise/set_flags calbacks
- From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
- [PATCH 3/3] ecryptfs: add fadvise/set_flags calbacks
- From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
- Re: [PATCH] ecryptfs: remove unneeded buggy code in ecryptfs_do_create()
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.18
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Force RO mount when encrypted view is enabled
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] NULL pointer dereference in ecryptfs (ecryptfs_setxattr)
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- AW: Separating different ecryptfs mounts
- From: Anna Fischer <a.fischer@xxxxxxxxxx>
- Re: Mount parameters
- From: Wilson <wilson.ubuntu@xxxxxxxxx>
- Re: Mount parameters
- From: Michael Chang <thenewme91@xxxxxxxxx>
- Re: Mount parameters
- From: Wilson <wilson.ubuntu@xxxxxxxxx>
- Re: Mount parameters
- From: Michael Chang <thenewme91@xxxxxxxxx>
- Mount parameters
- From: Wilson <wilson.ubuntu@xxxxxxxxx>
- Re: Separating different ecryptfs mounts
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Separating different ecryptfs mounts
- From: Christian Stüble <stueble@xxxxxxxxxx>
- Re: Separating different ecryptfs mounts
- From: Christian Stüble <stueble@xxxxxxxxxx>
- Re: Separating different ecryptfs mounts
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Separating different ecryptfs mounts
- From: Christian Stüble <stueble@xxxxxxxxxx>
- Re: Separating different ecryptfs mounts
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Separating different ecryptfs mounts
- From: Christian Stüble <stueble@xxxxxxxxxx>
- [PATCH] NULL pointer dereference in ecryptfs (ecryptfs_setxattr)
- From: Priya Bansal <p.bansal@xxxxxxxxxxx>
- Re: Practical questions about locking and re-encrypting
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: hardware acceleration
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- hardware acceleration
- From: Kenneth Waegeman <Kenneth.Waegeman@xxxxxxxx>
- Re: Practical questions about locking and re-encrypting
- From: Kenneth Waegeman <Kenneth.Waegeman@xxxxxxxx>
- [PATCH] ecryptfs: remove unneeded buggy code in ecryptfs_do_create()
- From: Alexey Khoroshilov <khoroshilov@xxxxxxxxx>
- Re: Practical questions about locking and re-encrypting
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Practical questions about locking and re-encrypting
- From: Kenneth Waegeman <Kenneth.Waegeman@xxxxxxxx>
- RE: [PATCH] ecryptfs: avoid to access NULL pointer when write metadata in xattr
- From: Chao Yu <chao2.yu@xxxxxxxxxxx>
- RE: [PATCH] ecryptfs: avoid to access NULL pointer when write metadata in xattr
- From: Chao Yu <chao2.yu@xxxxxxxxxxx>
- Re: [PATCH] ecryptfs: avoid to access NULL pointer when write metadata in xattr
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] ecryptfs: avoid to access NULL pointer when write metadata in xattr
- From: Chao Yu <chao2.yu@xxxxxxxxxxx>
- Re: [PATCH 1/1] ecryptfs: remove unnecessary break after goto
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/1] ecryptfs: remove unnecessary break after goto
- From: Fabian Frederick <fabf@xxxxxxxxx>
- Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/1] fs/ecryptfs/messaging.c: remove null test before kfree
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH v2] ecryptfs: Drop cast
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH v2] ecryptfs: Drop cast
- From: Himangi Saraogi <himangi774@xxxxxxxxx>
- Re: [PATCH] ecryptfs: Drop cast
- From: Joe Perches <joe@xxxxxxxxxxx>
- [PATCH] ecryptfs: Drop cast
- From: Himangi Saraogi <himangi774@xxxxxxxxx>
- Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
- From: Oleg Nesterov <oleg@xxxxxxxxxx>
- Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
- From: Oleg Nesterov <oleg@xxxxxxxxxx>
- Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
- From: Oleg Nesterov <oleg@xxxxxxxxxx>
- Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH 1/1] fs/ecryptfs/messaging.c: remove null test before kfree
- From: Fabian Frederick <fabf@xxxxxxxxx>
- Recovering Encrypted Directory
- From: Tom Browder <tom.browder@xxxxxxxxx>
- Re: kernel crash after enable ecryptfs under abnormal power off
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- kernel crash after enable ecryptfs under abnormal power off
- From: Hanks Wang <wangwenjie@xxxxxxxx>
- Re: Please patch key_mod.c
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: ecryptfs_privileged_open(): when kthread-ecryptfs is required ?
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- ecryptfs_privileged_open(): when kthread-ecryptfs is required ?
- From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
- Please patch key_mod.c
- From: "Jaroslav Fojtik" <jafojtik@xxxxxxxxx>
- Re: [PATCH 3/3] eCryptfs: Enable GCM support in eCryptfs
- From: Will Morrison <camocrazed@xxxxxxxxx>
- Erasing keys in ram
- From: zero <zero923@xxxxxxxxx>
- NFS -> eCryptfs -> Samba = files disappearing
- From: Jon Skarpeteig <jon.skarpeteig@xxxxxxxxx>
- Re: ecryptfs log spew from EINTR
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- ecryptfs log spew from EINTR
- From: Dave Hansen <dave.hansen@xxxxxxxxx>
- [PATCH 3/3] eCryptfs: Enable GCM support in eCryptfs
- From: Will Morrison <camocrazed@xxxxxxxxx>
- [PATCH 2/3] eCryptfs: Extend file headers to store cipher mode.
- From: Will Morrison <camocrazed@xxxxxxxxx>
- [PATCH 1/3] eCryptfs: Add mount option for cipher mode
- From: Will Morrison <camocrazed@xxxxxxxxx>
- PATCH [0/3] Integrity protection with GCM
- From: Will Morrison <camocrazed@xxxxxxxxx>
- Automated home encryption and noexec mount option
- From: Wilson <wilson.ubuntu@xxxxxxxxx>
- Re: Can anyone confirm or deny if ecryptfs will work with a glusterfs backend?
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Can anyone confirm or deny if ecryptfs will work with a glusterfs backend?
- From: Lance Reed <reed.r.lance@xxxxxxxxx>
- Re: Can anyone confirm or deny if ecryptfs will work with a glusterfs backend?
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Can anyone confirm or deny if ecryptfs will work with a glusterfs backend?
- From: Lance Reed <reed.r.lance@xxxxxxxxx>
- Re: [RFC 3/3] Enable GCM support in eCryptfs
- From: Taylor Hornby <havoc@xxxxxxxxx>
- Security Audit
- From: Taylor Hornby <havoc@xxxxxxxxx>
- Re: How best to crack wrapped-passphrase?
- From: Tom Vaughan <thomas.david.vaughan@xxxxxxxxx>
- Re: How best to crack wrapped-passphrase?
- From: Artur Rataj <arturrataj@xxxxxxxxx>
- Re: How best to crack wrapped-passphrase?
- From: Tom Vaughan <thomas.david.vaughan@xxxxxxxxx>
- Re: How best to crack wrapped-passphrase?
- From: Artur Rataj <arturrataj@xxxxxxxxx>
- Fwd: How best to crack wrapped-passphrase?
- From: Artur Rataj <arturrataj@xxxxxxxxx>
- [RFC 0/3] Enable GCM support
- From: Will Morrison <camocrazed@xxxxxxxxx>
- [RFC 3/3] Enable GCM support in eCryptfs
- From: Will Morrison <camocrazed@xxxxxxxxx>
- [RFC 2/3] eCryptfs: Extend file headers to store cipher mode.
- From: Will Morrison <camocrazed@xxxxxxxxx>
- [RFC 1/3] eCryptfs: Add mount option for cipher mode
- From: Will Morrison <camocrazed@xxxxxxxxx>
- How best to crack wrapped-passphrase?
- From: Tom Vaughan <thomas.david.vaughan@xxxxxxxxx>
- PROBLEM: Core dump in ecryptfs directory on ext4 crashes kernel if aesni_intel is used
- From: Maarten Baert <maarten-baert@xxxxxxxxxxx>
- Re: eCryptfs using openssl encountered "Transport endpoint is not connected" when writting file into the mounted folder
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 5/9] Use %pd in eCryptFS
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Did I lost an encrypted folder?
- From: Artur Rataj <arturrataj@xxxxxxxxx>
- Did I lost an encrypted folder?
- From: Artur Rataj <arturrataj@xxxxxxxxx>
- Re: ecryptfs with an epehemeral key
- From: Eric Tschetter <echeddar@xxxxxxxxx>
- Re: ecryptfs with an epehemeral key
- From: Michael Chang <m9chang@xxxxxxxxxxxx>
- ecryptfs with an epehemeral key
- From: Eric Tschetter <echeddar@xxxxxxxxx>
- [PATCH 5/9] Use %pd in eCryptFS
- From: David Howells <dhowells@xxxxxxxxxx>
- eCryptfs using openssl encountered "Transport endpoint is not connected" when writting file into the mounted folder
- From: "cc chen" <cheanchaeng.chen@xxxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: Catalin Ionita <io.catalin@xxxxxxxxx>
- Re: Fwd: Mounting multiple directories using ecryptfs
- From: "Raj [mail list]" <rajlistuser@xxxxxxxxx>
- How to enable crypttab to run at boot
- From: "imagenesis@xxxxxxxxx" <imagenesis@xxxxxxxxx>
- Re: Where is the declaration of execution of ecryptfs for on user login automount?
- From: "imagenesis@xxxxxxxxx" <imagenesis@xxxxxxxxx>
- Where is the declaration of execution of ecryptfs for on user login automount?
- From: "imagenesis@xxxxxxxxx" <imagenesis@xxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: William Roberts <bill.c.roberts@xxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: Catalin Ionita <io.catalin@xxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: William Roberts <bill.c.roberts@xxxxxxxxx>
- Re: Fwd: Mounting multiple directories using ecryptfs
- From: James Muir <muir.james.a@xxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: Catalin Ionita <io.catalin@xxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: Catalin Ionita <io.catalin@xxxxxxxxx>
- Fwd: Mounting multiple directories using ecryptfs
- From: "Raj [mail list]" <rajlistuser@xxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: Catalin Ionita <io.catalin@xxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: Catalin Ionita <io.catalin@xxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: William Roberts <bill.c.roberts@xxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Looking for volunteers to test and review ecryptfs integration with Android
- From: William Roberts <bill.c.roberts@xxxxxxxxx>
- Looking for volunteers to test and review ecryptfs integration with Android
- From: Catalin Ionita <io.catalin@xxxxxxxxx>
- Mounting multiple directories using ecryptfs
- From: "Raj [mail list]" <rajlistuser@xxxxxxxxx>
- [GIT PULL] Minor eCryptfs fix for 3.13-rc1
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: INFO: possible circular locking dependency detected
- From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
- INFO: possible circular locking dependency detected
- From: Alexei Starovoitov <ast@xxxxxxxxxxxx>
- Re: ecryptfs-mount-private fails the first time after boot
- From: Benjamin Moody <benjamin.moody@xxxxxxxxx>
- Re: ecryptfs-mount-private fails the first time after boot
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: ecryptfs-mount-private fails the first time after boot
- From: Benjamin Moody <benjamin.moody@xxxxxxxxx>
- Re: ecryptfs-mount-private fails the first time after boot
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- ecryptfs-mount-private fails the first time after boot
- From: Benjamin Moody <benjamin.moody@xxxxxxxxx>
- Re: [PATCH] ecryptfs: Fix explicit null dereference
- From: Geyslan Gregório Bem <geyslan@xxxxxxxxx>
- Re: [PATCH] ecryptfs: Fix explicit null dereference
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] ecryptfs: Fix explicit null dereference
- From: Geyslan Gregório Bem <geyslan@xxxxxxxxx>
- Re: [PATCH] ecryptfs: Fix explicit null dereference
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] ecryptfs: Fix explicit null dereference
- From: Pekka Enberg <penberg@xxxxxxxxxx>
- [PATCH] ecryptfs: Fix explicit null dereference
- From: "Geyslan G. Bem" <geyslan@xxxxxxxxx>
- [PATCH] eCryptfs: file->private_data is always valid
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- re: file->f_op is never NULL...
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.12-rc7
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] ecryptfs: Fix memory leakage in keystore.c
- From: Geyslan Gregório Bem <geyslan@xxxxxxxxx>
- Re: [PATCH] ecryptfs: Fix memory leakage in keystore.c
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH V9 31/33] ecrpytfs: Convert aio_read/write ops to read/write_iter
- From: Dave Kleikamp <dave.kleikamp@xxxxxxxxxx>
- [PATCH] ecryptfs: Fix memory leakage in keystore.c
- From: "Geyslan G. Bem" <geyslan@xxxxxxxxx>
- Re: porting to android
- From: James Muir <muir.james.a@xxxxxxxxx>
- Re: porting to android
- From: Dustin Kirkland <kirkland@xxxxxxxxxx>
- Re: porting to android
- From: James Muir <muir.james.a@xxxxxxxxx>
- Re: porting to android
- From: James Muir <muir.james.a@xxxxxxxxx>
- Re: porting to android
- From: James Muir <muir.james.a@xxxxxxxxx>
- porting to android
- From: James Muir <muir.james.a@xxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.12-rc1
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] ecryptfs: avoid ctx initialization race
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [patch] ecryptfs: remove check for if an array is NULL
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] ecryptfs: avoid ctx initialization race
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Problem using ecryptfs on top of NFS
- From: Ryan Sawhill <rsaw@xxxxxxxxxx>
- [PATCH] ecryptfs: avoid ctx initialization race
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Problem using ecryptfs on top of NFS
- From: Ruben Gaspar <gasparuben@xxxxxxxxx>
- [patch] ecryptfs: remove check for if an array is NULL
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
- [PATCH V8 31/33] ecrpytfs: Convert aio_read/write ops to read/write_iter
- From: Dave Kleikamp <dave.kleikamp@xxxxxxxxxx>
- Inserting extra extents in lower file
- From: Zameer Manji <zmanji@xxxxxxxxx>
- [GIT PULL] eCryptfs updates for 3.11-rc1
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH v6 08/14] ecrypt-fs: replace direct access of d_count with the d_count() helper
- From: Waiman Long <Waiman.Long@xxxxxx>
- Re: Filesystem boundaries
- From: Karl-Philipp Richter <krichter722@xxxxxx>
- Re: Filesystem boundaries
- From: Li Wang <liwang@xxxxxxxxxxxxxxx>
- Filesystem boundaries
- From: Karl-Philipp Richter <krichter722@xxxxxx>
- [PATCH v5 08/12] ecrypt-fs: replace direct access of d_count with the d_count() helper
- From: Waiman Long <Waiman.Long@xxxxxx>
- [PATCH v4 08/12] ecrypt-fs: rename d_count field of dentry to d_refcount
- From: Waiman Long <Waiman.Long@xxxxxx>
- [PATCH v3 14/25] ecrypt-fs: Change how dentry's d_count field is accessed
- From: Waiman Long <Waiman.Long@xxxxxx>
- [RFC 2/2] eCryptfs: Extend file headers to store cipher mode.
- From: Will Morrison <camocrazed@xxxxxxxxx>
- [RFC 1/2] eCryptfs: Add mount option for cipher mode
- From: Will Morrison <camocrazed@xxxxxxxxx>
- Re: ecryptfs on sub-directory?
- From: Michael Chang <thenewme91@xxxxxxxxx>
- ecryptfs on sub-directory?
- From: Leam Hall <leamhall@xxxxxxxxx>
- [PATCH] Use ecryptfs_dentry_to_lower_path in a couple of places
- From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
- Re: Plans for adding cipher mode to file headers
- From: Will Morrison <camocrazed@xxxxxxxxx>
- Re: Plans for adding cipher mode to file headers
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.10-rc5
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Check return of filemap_write_and_wait during fsync
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Plans for adding cipher mode to file headers
- From: Will Morrison <camocrazed@xxxxxxxxx>
- Re: [RFC] eCryptfs: Add mount option for cipher mode
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [RFC] eCryptfs: Add mount option for cipher mode
- From: Will Morrison <camocrazed@xxxxxxxxx>
- Re: [RFC] eCryptfs: Add mount option for cipher mode
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [RFC] eCryptfs: Add mount option for cipher mode
- From: Will Morrison <camocrazed@xxxxxxxxx>
- Re: [PATCH] eCryptfs: Cocci spatch "memdup.spatch"
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Cocci spatch "memdup.spatch"
- From: Thomas Meyer <thomas@xxxxxxxx>
- Re: [PATCH] Update eCryptFS maintainers
- From: Tyler C Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] Update eCryptFS maintainers
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- [PATCH 4/4] eCryptfs: Make extent and scatterlist crypt function parameters similar
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 0/4] eCryptfs: Combine similar encrypt and decrypt functions
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/4] eCryptfs: Combine page_offset crypto functions
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 2/4] eCryptfs: Merge ecryptfs_encrypt_extent() and ecryptfs_decrypt_extent()
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 3/4] eCryptfs: Collapse crypt_page_offset() into crypt_extent()
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 5/5] eCryptfs: Decrypt pages in-place
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 4/5] eCryptfs: Accept one offset parameter in page offset crypto functions
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 3/5] eCryptfs: Simplify lower file offset calculation
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 2/5] eCryptfs: Read/write entire page during page IO
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/5] eCryptfs: Use entire helper page during page crypto operations
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 0/5] eCryptfs: Clean up usage of helper page for crypto ops
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] fs: ecryptfs: fixed msync to flush data
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] fs: ecryptfs: fixed msync to flush data
- From: Paul Taysom <taysom@xxxxxxxxxxxx>
- Re: Adding cipher mode as a mount option
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Adding cipher mode as a mount option
- From: Will Morrison <camocrazed@xxxxxxxxx>
- [GIT PULL] eCryptfs update for 3.10-rc1
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Ecryptfs over sshfs and timestamps
- From: Ivan Yosifov <iyosifov@xxxxxxxxx>
- Re: Ecryptfs over sshfs and timestamps
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [RFC v3 1/1] eCryptfs: Use the ablkcipher crypto API
- From: Zeev Zilberman <zeev@xxxxxxxxxxxxxxxxx>
- Re: Ecryptfs over sshfs and timestamps
- From: Ivan Yosifov <iyosifov@xxxxxxxxx>
- Re: Ecryptfs over sshfs and timestamps
- From: Ivan Yosifov <iyosifov@xxxxxxxxx>
- Re: Ecryptfs over sshfs and timestamps
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Ecryptfs over sshfs and timestamps
- From: Ivan Yosifov <iyosifov@xxxxxxxxx>
- Re: Ecryptfs over sshfs and timestamps
- From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
- Re: Ecryptfs over sshfs and timestamps
- From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
- Ecryptfs over sshfs and timestamps
- From: Ivan Yosifov <iyosifov@xxxxxxxxx>
- Re: async crashes
- From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxx>
- Re: [RFC v3 1/1] eCryptfs: Use the ablkcipher crypto API
- From: Colin Ian King <colin.king@xxxxxxxxxxxxx>
- Re: [RFC v3 1/1] eCryptfs: Use the ablkcipher crypto API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [RFC v3 1/1] eCryptfs: Use the ablkcipher crypto API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [RFC v2 1/1] eCryptfs: Use the ablkcipher crypto API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [RFC 1/1] eCryptfs: Use the ablkcipher crypto API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: async crashes
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [RFC 1/1] eCryptfs: Use the ablkcipher crypto API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [RFC 0/1] eCryptfs: Use the ablkcipher crypto API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- async crashes
- From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxx>
- Re: Will there be a multi CPU core version of eCryptfs?
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Will there be a multi CPU core version of eCryptfs?
- From: Michael Schneider <michael8schneider@xxxxxxxxx>
- [PATCH V7 -next 31/33] ecrpytfs: Convert aio_read/write ops to read/write_iter
- From: Dave Kleikamp <dave.kleikamp@xxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.9-rc2
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH v2] eCryptfs: allow userspace messaging to be disabled
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH v2] eCryptfs: allow userspace messaging to be disabled
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: allow userspace messaging to be disabled
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: allow userspace messaging to be disabled
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [PATCH linux-next] ecryptfs: ecryptfs_msg_ctx_alloc_to_free(): remove kfree() redundant null check
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH linux-next] eCryptfs: decrypt_pki_encrypted_session_key(): remove kfree() redundant null check
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH linux-next] ecryptfs: ecryptfs_msg_ctx_alloc_to_free(): remove kfree() redundant null check
- From: Tim Gardner <tim.gardner@xxxxxxxxxxxxx>
- [PATCH linux-next] eCryptfs: decrypt_pki_encrypted_session_key(): remove kfree() redundant null check
- From: Tim Gardner <tim.gardner@xxxxxxxxxxxxx>
- Re: Storing the executable bit along with the rest of cryptographic metadata
- From: Thiago Padilha <tpadilha84@xxxxxxxxx>
- Re: Storing the executable bit along with the rest of cryptographic metadata
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Storing the executable bit along with the rest of cryptographic metadata
- From: Thiago Padilha <tpadilha84@xxxxxxxxx>
- [PATCH V6 29/30] ecrpytfs: Convert aio_read/write ops to read/write_iter
- From: Dave Kleikamp <dave.kleikamp@xxxxxxxxxx>
- Re: [patch] eCryptfs: remove unneeded checks in virt_to_scatterlist()
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [patch] eCryptfs: remove unneeded checks in virt_to_scatterlist()
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
- Re: eCryptfs ablkcipher patch
- From: Zeev Zilberman <zeev@xxxxxxxxxxxxxxxxx>
- Re: eCryptfs ablkcipher patch
- From: Zeev Zilberman <zeev@xxxxxxxxxxxxxxxxx>
- Re: [PATCH v2] fs: ecryptfs: initialize payload_len in keystore.c
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH v2] fs: ecryptfs: initialize payload_len in keystore.c
- From: Simon Que <sque@xxxxxxxxxxxx>
- Re: [PATCH] fs: ecryptfs: initialize payload_len in keystore.c
- From: Simon Que <sque@xxxxxxxxxxxx>
- Re: [PATCH] fs: ecryptfs: initialize payload_len in keystore.c
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] fs: ecryptfs: initialize payload_len in keystore.c
- From: Simon Que <sque@xxxxxxxxxxxx>
- Re: Wrapper to mount Private directories without root
- From: David Obadia <dav-ecryptfs@xxxxxxxx>
- Re: Wrapper to mount Private directories without root
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: eCryptfs ablkcipher patch
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH V5 29/30] ecrpytfs: Convert aio_read/write ops to read/write_iter
- From: Dave Kleikamp <dave.kleikamp@xxxxxxxxxx>
- eCryptfs ablkcipher patch
- From: Zeev Zilberman <zeev@xxxxxxxxxxxxxxxxx>
- Re: size limitations?
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- size limitations?
- From: "Warren H. Prince" <wprince@xxxxxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.8-rc2
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Zeev Zilberman <zeev@xxxxxxxxxxxxxxxxx>
- Wrapper to mount Private directories without root
- From: David Obadia <dav-ecryptfs@xxxxxxxx>
- Re: Encrypting BTRFS Volume
- From: Michael Chang <m9chang@xxxxxxxxxxxx>
- Re: Encrypting BTRFS Volume
- From: CACook@xxxxxxxxxxxxxxx
- CRASH Undefined Instruction
- From: William Roberts <bill.c.roberts@xxxxxxxxx>
- [PATCH] fs/ecryptfs/crypto.c: make ecryptfs_encode_for_filename() static
- From: Cong Ding <dinggnu@xxxxxxxxx>
- Re: Encrypting BTRFS Volume
- From: CACook@xxxxxxxxxxxxxxx
- Re: Encrypting BTRFS Volume
- From: Michael Chang <m9chang@xxxxxxxxxxxx>
- Re: Encrypting BTRFS Volume
- From: CACook@xxxxxxxxxxxxxxx
- Re: Encrypting BTRFS Volume
- From: "B. J. Potter" <bjpotter@xxxxxxxxx>
- Re: Encrypting BTRFS Volume
- From: CACook@xxxxxxxxxxxxxxx
- Re: Encrypting BTRFS Volume
- From: CACook@xxxxxxxxxxxxxxx
- Re: Encrypting BTRFS Volume
- From: "B. J. Potter" <bjpotter@xxxxxxxxx>
- Re: Encrypting BTRFS Volume
- From: CACook@xxxxxxxxxxxxxxx
- Re: Encrypting BTRFS Volume
- From: "B. J. Potter" <bjpotter@xxxxxxxxx>
- Re: Encrypting BTRFS Volume
- From: CACook@xxxxxxxxxxxxxxx
- Encrypting BTRFS Volume
- From: CACook@xxxxxxxxxxxxxxx
- Re: Regd: Prefetching and Buffering in eCryptfs
- From: Rahul Agrawal <mailrhl@xxxxxxxxx>
- Re: Regd: Prefetching and Buffering in eCryptfs
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Regd: Prefetching and Buffering in eCryptfs
- From: Rahul Agrawal <mailrhl@xxxxxxxxx>
- Possible error in ecryptfs-recover-private
- From: "B. J. Potter" <bjpotter@xxxxxxxxx>
- [PATCH v4 30/31] ecrpytfs: Convert aio_read/write ops to read/write_iter
- From: Dave Kleikamp <dave.kleikamp@xxxxxxxxxx>
- Re: [3.0.y, 3.2.y, 3.4.y] Re: ecryptfs: corrupted files on a disk full event
- From: Greg KH <greg@xxxxxxxxx>
- Re: [3.0.y, 3.2.y, 3.4.y] Re: ecryptfs: corrupted files on a disk full event
- From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
- Re: [3.0.y, 3.2.y, 3.4.y] Re: ecryptfs: corrupted files on a disk full event
- From: Herton Ronaldo Krzesinski <herton.krzesinski@xxxxxxxxxxxxx>
- [PATCH 2/2] fs:ecryptfs basic code optimization
- From: Abhijit Pawar <abhi.c.pawar@xxxxxxxxx>
- [PATCH 1/2] fs:ecryptfs basic code optimization
- From: Abhijit Pawar <abhi.c.pawar@xxxxxxxxx>
- Re: Odd problem with ECryptFS keys
- From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxx>
- Odd problem with ECryptFS keys
- From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxx>
- Re: [PATCH] eCryptfs: Avoid unnecessary disk read and data decryption during writing
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Avoid unnecessary disk read and data decryption during writing
- From: Li Wang <wangli@xxxxxxxxxxxxxx>
- Re: [3.0.y, 3.2.y, 3.4.y] Re: ecryptfs: corrupted files on a disk full event
- From: Greg KH <greg@xxxxxxxxx>
- Re: [3.0.y, 3.2.y, 3.4.y] Re: ecryptfs: corrupted files on a disk full event
- From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
- [3.0.y, 3.2.y, 3.4.y] Re: ecryptfs: corrupted files on a disk full event
- From: Jonathan Nieder <jrnieder@xxxxxxxxx>
- [PATCH] Pass the f_flags from the upper open to the lower open.
- From: Douglas Leeder <douglas.leeder@xxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.6-rc6
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Copy up attributes of the lower target inode after rename
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 2/2] eCryptfs: Call lower ->flush() from ecryptfs_flush()
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/2] eCryptfs: Write out all dirty pages just before releasing the lower file
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- RE: [PATCH] eCryptfs: use list_for_each_safe() when the loop involves delete items
- From: "yongjun_wei@xxxxxxxxxxxxxxxxx" <yongjun_wei@xxxxxxxxxxxxxxxxx>
- [PATCH] eCryptfs: fix to use list_for_each_entry_safe() when delete items
- From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
- [PATCH] eCryptfs: use list_for_each_safe() when the loop involves delete items
- From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
- Re: ecryptfs and fanotify
- From: Douglas Leeder <douglas.leeder@xxxxxxxxxx>
- Re: ecryptfs and fanotify
- From: Douglas Leeder <douglas.leeder@xxxxxxxxxx>
- Re: ecryptfs and fanotify
- From: Tyler C Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: ecryptfs and fanotify
- From: Douglas Leeder <douglas.leeder@xxxxxxxxxx>
- Re: ecryptfs and fanotify
- From: Douglas Leeder <douglas.leeder@xxxxxxxxxx>
- Re: ecryptfs and fanotify
- From: Florian Westphal <Florian.Westphal@xxxxxxxxxx>
- RE: ecryptfs and fanotify
- From: Douglas Leeder <douglas.leeder@xxxxxxxxxx>
- RE: Process/Scanner hang with ecryptfs and fanotify
- From: Douglas Leeder <douglas.leeder@xxxxxxxxxx>
- Process/Scanner hang with ecryptfs and fanotify
- From: Douglas Leeder <douglas.leeder@xxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.6-rc1
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/1] eCryptfs: check for eCryptfs cipher support at mount
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Revert to a writethrough cache model
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/1] eCryptfs: check for eCryptfs cipher support at mount
- From: Tim Sally <tsally@xxxxxxxxxxxxxxx>
- Re: [PATCH 1/1] eCryptfs: check for eCryptfs cipher support at mount
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/1] eCryptfs: check for eCryptfs cipher support at mount
- From: Tim Sally <tsally@xxxxxxxxxxxxxxx>
- [PATCH 0/1] Check for eCryptfs cipher support at mount time.
- From: Tim Sally <tsally@xxxxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Revert to a writethrough cache model
- From: Colin Ian King <colin.king@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Revert to a writethrough cache model
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.5-rc6
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/3] eCryptfs: Gracefully refuse miscdev file ops on inherited/passed files
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/3] eCryptfs: Gracefully refuse miscdev file ops on inherited/passed files
- From: Sasha Levin <levinsasha928@xxxxxxxxx>
- Re: [PATCH 2/2] eCryptfs: Initialize empty lower files when opening them
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- RE: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: "Li Wang" <dragonylffly@xxxxxxx>
- Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: "'Tyler Hicks'" <tyhicks@xxxxxxxxxxxxx>
- RE: Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re: Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Thieu Le <thieule@xxxxxxxxxx>
- Re:Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: dragonylffly <dragonylffly@xxxxxxx>
- Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Thieu Le <thieule@xxxxxxxxxx>
- Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Thieu Le <thieule@xxxxxxxxxx>
- Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Thieu Le <thieule@xxxxxxxxxx>
- Re: [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 0/1] ecryptfs: Migrate to ablkcipher API
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/1] ecryptfs: Migrate to ablkcipher API
- From: Colin King <colin.king@xxxxxxxxxxxxx>
- [PATCH 0/1] ecryptfs: Migrate to ablkcipher API
- From: Colin King <colin.king@xxxxxxxxxxxxx>
- [PATCH 2/2] eCryptfs: Initialize empty lower files when opening them
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/2] eCryptfs: Unlink lower inode when ecryptfs_create() fails
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/3] eCryptfs: Gracefully refuse miscdev file ops on inherited/passed files
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 3/3] eCryptfs: Make all miscdev functions use daemon ptr in file private_data
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 2/3] eCryptfs: Remove unused messaging declarations and function
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 0/3] eCryptfs: Fix and simplify messaging code
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [patch] eCryptfs: fix ecryptfs_privileged_open() for read only files
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
- Re: [patch] eCryptfs: fix ecryptfs_privileged_open() for read only files
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Copy up POSIX ACL and read-only flags from lower mount
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: ecryptfs o_direct
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
- ecryptfs o_direct
- From: Georg Schönberger <gschoenberger@xxxxxxxxxxxxxxxx>
- [patch] eCryptfs: fix ecryptfs_privileged_open() for read only files
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Marco Stornelli <marco.stornelli@xxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
- Re: [RFC, PATCH] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [RFC, PATCH] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
- [RFC, PATCH, RESEND] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
- From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
- Re: ecryptfs: kernel BUG at fs/ecryptfs/miscdev.c:52
- From: Sasha Levin <levinsasha928@xxxxxxxxx>
- Re: Bugreport on Ubuntu LTS: not ok - 2 Objects creation does not break ACLs with restrictive umask
- From: Stefan Beller <stefanbeller@xxxxxxxxxxxxxx>
- Re: Bugreport on Ubuntu LTS: not ok - 2 Objects creation does not break ACLs with restrictive umask
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Bugreport on Ubuntu LTS: not ok - 2 Objects creation does not break ACLs with restrictive umask
- From: Junio C Hamano <gitster@xxxxxxxxx>
- Re: Bugreport on Ubuntu LTS: not ok - 2 Objects creation does not break ACLs with restrictive umask
- From: Jeff King <peff@xxxxxxxx>
- Re: Bugreport on Ubuntu LTS: not ok - 2 Objects creation does not break ACLs with restrictive umask
- From: Junio C Hamano <gitster@xxxxxxxxx>
- Re: Bugreport on Ubuntu LTS: not ok - 2 Objects creation does not break ACLs with restrictive umask
- From: Jeff King <peff@xxxxxxxx>
- Re: Active Directory Integration?
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Active Directory Integration?
- From: Ray Van Dolson <rvandolson@xxxxxxxx>
- ecryptfs: kernel BUG at fs/ecryptfs/miscdev.c:52
- From: Sasha Levin <levinsasha928@xxxxxxxxx>
- Re: ecryptfs: Kernel BUG when closing device
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: ecryptfs: Kernel BUG when closing device
- From: Sasha Levin <levinsasha928@xxxxxxxxx>
- Re: ecryptfs: Kernel BUG when closing device
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- ecryptfs: Kernel BUG when closing device
- From: Sasha Levin <sasha.levin@xxxxxxxxxx>
- Re: [RFC] eCryptfs file system with HMAC verification
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [RFC] eCryptfs file system with HMAC verification
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- [RFC] eCryptfs file system with HMAC verification
- From: "Li Wang" <dragonylffly@xxxxxxx>
- RE: [PATCH] eCryptfs: Fix kernel bug for writing mmaped non-eCryptfs file
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Fix kernel bug for writing mmaped non-eCryptfs file
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Fix kernel bug for writing mmaped non-eCryptfs file
- From: Li Wang <liwang@xxxxxxxxxxx>
- Re: Linus GIT (3.3.0-rc6+) -- INFO: possible circular locking dependency detected
- From: "Ted Ts'o" <tytso@xxxxxxx>
- Re: Linus GIT (3.3.0-rc6+) -- INFO: possible circular locking dependency detected
- From: "Ted Ts'o" <tytso@xxxxxxx>
- Re: Linus GIT (3.3.0-rc6+) -- INFO: possible circular locking dependency detected
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Linus GIT (3.3.0-rc6+) -- INFO: possible circular locking dependency detected
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Linus GIT (3.3.0-rc6+) -- INFO: possible circular locking dependency detected
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- [PATCH] ecryptfs: fix printk format warning for size_t
- From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.3-rc4
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 3/3] eCryptfs: Remove unreached codes
- From: Li Wang <liwang@xxxxxxxxxxx>
- [PATCH 2/3] eCryptfs: Remove redundant IF statement
- From: Li Wang <liwang@xxxxxxxxxxx>
- [PATCH 1/3] eCryptfs: Write bug for non-ecryptfs file
- From: Li Wang <liwang@xxxxxxxxxxx>
- Re: ecryptfs with aes-ni slower bug
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- Re: ecryptfs with aes-ni slower bug
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- ecryptfs with aes-ni slower bug
- From: Stefan Dröge <stefan@xxxxxxxxxx>
- RE: Re: [PATCH] eCryptfs: Quota check incorrectly ignored
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re: [PATCH 29/60] ecryptfs: remove the second argument of k[un]map_atomic()
- From: Cong Wang <amwang@xxxxxxxxxx>
- Fwd: Re: [PATCH] eCryptfs: Quota check incorrectly ignored
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 29/60] ecryptfs: remove the second argument of k[un]map_atomic()
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Quota check incorrectly ignored
- From: "'Tyler Hicks'" <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Quota check incorrectly ignored
- From: "'Tyler Hicks'" <tyhicks@xxxxxxxxxxxxx>
- RE: [PATCH] eCryptfs: Quota check incorrectly ignored
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Quota check incorrectly ignored
- From: Jan Kara <jack@xxxxxxx>
- [PATCH 29/60] ecryptfs: remove the second argument of k[un]map_atomic()
- From: Cong Wang <amwang@xxxxxxxxxx>
- [PATCH] eCryptfs: Quota check incorrectly ignored
- From: Li Wang <liwang@xxxxxxxxxxx>
- [PATCH] eCryptfs: Copy up lower inode attrs after setting lower xattr
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: dumb question or not?
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- Re: dumb question or not?
- From: Space Cakex <spacecakex@xxxxxxxxx>
- Re: dumb question or not?
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- Re: [PATCH v2] eCryptfs: Write optimization for non-uptodate page
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH v2] eCryptfs: Write optimization for non-uptodate page
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- dumb question or not?
- From: Space Cake <spacecakex@xxxxxxxxx>
- Re: [PATCH v2] eCryptfs: write optimization
- From: "'Tyler Hicks'" <tyhicks@xxxxxxxxxxxxx>
- Re: ecryptfs doesn´t like noauto and noatime
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- Re: ecryptfs doesn´t like noauto and noatime
- From: Martin Steigerwald <ms@xxxxxxxxx>
- [PATCH v2] eCryptfs: write optimization
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re: [PATCH] eCryptfs: write optimization
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.3-rc2
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: write optimization
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- [PATCH] eCryptfs: write optimization
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- [PATCH] eCryptfs: move misleading function comments
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re:[PATCH 1/3] eCryptfs: Make truncate path killable
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re:[PATCH 2/3 v2] eCryptfs: Check inode changes in setattr
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re: Incorrect eCryptfs list archive link
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Incorrect eCryptfs list archive link
- From: David Miller <davem@xxxxxxxxxxxxx>
- Incorrect eCryptfs list archive link
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 2/3 v2] eCryptfs: Check inode changes in setattr
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 2/3] eCryptfs: Check inode changes in setattr
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: eCryptfs: Truncate path improvements
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: eCryptfs: Truncate path improvements
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re:[PATCH 2/3] eCryptfs: Check inode changes in setattr
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- eCryptfs: Truncate path improvements
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 2/3] eCryptfs: Check inode changes in setattr
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 3/3] eCryptfs: Remove unused ecryptfs_read()
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/3] eCryptfs: Make truncate path killable
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/2] ecryptfs: Improve metatdata read failure logging
- From: Tim Gardner <rtg.canonical@xxxxxxxxx>
- Re: [PATCH 1/2] ecryptfs: Improve metatdata read failure logging
- From: Tyler Hicks <tyler.hicks@xxxxxxxxxxxxx>
- [PATCH 3/3] eCryptfs: Replace miscdev read/write magic numbers
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 0/3] eCryptfs: Fix and cleanup miscdev read and write functions
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 2/3] eCryptfs: Report errors in writes to /dev/ecryptfs
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 1/3] eCryptfs: Sanitize write counts of /dev/ecryptfs
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re:Re: [PATCH] eCryptfs: truncate optimization (sometimes upto 25 000x fa ster)
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re: [PATCH] eCryptfs: infinite loop bug
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- Re: [PATCH] eCryptfs: truncate optimization (sometimes upto 25000x fa ster)
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: infinite loop due to overflow in ecryptfs_write()
- From: Cong Wang <xiyou.wangcong@xxxxxxxxx>
- Re: [PATCH] eCryptfs: infinite loop bug
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: infinite loop bug
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- [PATCH] eCryptfs: truncate optimization (sometimes upto 25000x fa ster)
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- [PATCH] eCryptfs: infinite loop due to overflow in ecryptfs_write()
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: infinite loop bug
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: infinite loop bug
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re:Re: [PATCH] eCryptfs: infinite loop bug
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re: [PATCH] eCryptfs: infinite loop bug
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: infinite loop bug
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: infinite loop bug
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: infinite loop bug
- From: Cong Wang <xiyou.wangcong@xxxxxxxxx>
- [PATCH] eCryptfs: infinite loop bug
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re: ecryptfs / aladdin token
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- ecryptfs / aladdin token
- From: Space Cake <spacecakex@xxxxxxxxx>
- Re: ecryptfs doesn´t like noauto and noatime
- From: Jakob Unterwurzacher <jakobunt@xxxxxxxxx>
- Re: ecryptfs doesn´t like noauto and noatime
- From: Martin Steigerwald <Martin@xxxxxxxxxxxx>
- Re: ecryptfs doesn´t like noauto and noatime
- From: Martin Steigerwald <Martin@xxxxxxxxxxxx>
- Re: ecryptfs doesn´t like noauto and noatime
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: ecryptfs doesn´t like noauto and noatime
- From: Jakob Unterwurzacher <jakobunt@xxxxxxxxx>
- ecryptfs doesn´t like noauto and noatime
- From: Martin Steigerwald <Martin@xxxxxxxxxxxx>
- Re: [PATCH] mm: Don't warn if memdup_user fails
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] mm: Don't warn if memdup_user fails
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
- Re: [PATCH] mm: Don't warn if memdup_user fails
- From: David Rientjes <rientjes@xxxxxxxxxx>
- Re: [PATCH] mm: Don't warn if memdup_user fails
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] mm: Don't warn if memdup_user fails
- From: David Rientjes <rientjes@xxxxxxxxxx>
- Re: [PATCH 1/2] ecryptfs: Improve metatdata read failure logging
- From: Tim Gardner <rtg.canonical@xxxxxxxxx>
- Re: [PATCH 1/2] ecryptfs: Improve metatdata read failure logging
- From: Tyler Hicks <tyler.hicks@xxxxxxxxxxxxx>
- Re: [PATCH] mm: Don't warn if memdup_user fails
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] mm: Don't warn if memdup_user fails
- From: Pekka Enberg <penberg@xxxxxxxxxx>
- Re: [PATCH] mm: Don't warn if memdup_user fails
- From: Sasha Levin <levinsasha928@xxxxxxxxx>
- Re: [PATCH] mm: Don't warn if memdup_user fails
- From: Pekka Enberg <penberg@xxxxxxxxxx>
- Re: [PATCH] mm: Don't warn if memdup_user fails
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [GIT PULL] eCryptfs fix for 3.2-rc7
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- [GIT PULL] eCryptfs fix for 3.2-rc7
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH v2] eCryptfs: Improve statfs reporting
- From: John Johansen <john.johansen@xxxxxxxxxxxxx>
- Re: encryption metadata not stored with filesystem
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- Re: ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-13]
- From: Martin Steigerwald <ms@xxxxxxxxx>
- Re: ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-13]
- From: Alexis Hafner <alexis.hafner@xxxxxxxxx>
- Re: encryption metadata not stored with filesystem
- From: Martin Steigerwald <ms@xxxxxxxxx>
- Re: rsync copies twice
- From: Martin Steigerwald <ms@xxxxxxxxx>
- Re: ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-13]
- From: Martin Steigerwald <ms@xxxxxxxxx>
- Re: ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-13]
- From: Martin Steigerwald <ms@xxxxxxxxx>
- Re: ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-13]
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH v2] eCryptfs: Improve statfs reporting
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- [PATCH v2] eCryptfs: Improve statfs reporting
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Improve statfs reporting
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: encryption metadata not stored with filesystem
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Improve statfs reporting
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Improve statfs reporting
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- [PATCH] eCryptfs: Improve statfs reporting
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- rsync copies twice
- From: Martin Steigerwald <ms@xxxxxxxxx>
- encryption metadata not stored with filesystem
- From: Martin Steigerwald <ms@xxxxxxxxx>
- ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-13]
- From: Martin Steigerwald <ms@xxxxxxxxx>
- Re: eCryptfs: how to submit a patch
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- Re: ecryptfs & ssh authentication
- From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
- Re: ecryptfs & ssh authentication
- From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
- Re: ecryptfs & ssh authentication
- From: Robert Freeman-Day <presgas@xxxxxxxxx>
- ecryptfs & ssh authentication
- From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
- Re: [PATCH] MAINTAINERS: Update eCryptfs maintainer address
- From: Tyler C Hicks <tyler.hicks@xxxxxxxxxxxxx>
- [PATCH] MAINTAINERS: Update eCryptfs maintainer address
- From: Dustin Kirkland <dustin.kirkland@xxxxxxxxxxx>
- Re: [PATCH 1/1] fix d_revalidate oopsen on NFS exports
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH 1/1] fix d_revalidate oopsen on NFS exports
- From: Chris Dunlop <chris@xxxxxxxxxxxx>
- Re: [PATCH 1/1] fix d_revalidate oopsen on NFS exports
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH 31/62] ecryptfs: remove the second argument of k[un]map_atomic()
- From: Cong Wang <amwang@xxxxxxxxxx>
- [PATCH]eCryptfs: quota check ignored in the context of kernel thr ead
- From: "Li Wang" <liwang@xxxxxxxxxxx>
- Re: [GIT PULL] eCryptfs fixes for 3.2-rc3
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: [GIT PULL] eCryptfs fixes for 3.2-rc3
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [GIT PULL] eCryptfs fixes for 3.2-rc3
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.2-rc3
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Check array bounds for filename characters
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: 3.2.0-rc2: kernel BUG at fs/ecryptfs/crypto.c:348! regression?
- From: Arnd Hannemann <arnd@xxxxxxxxxx>
- Re: 3.2.0-rc2: kernel BUG at fs/ecryptfs/crypto.c:348! regression?
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- 3.2.0-rc2: kernel BUG at fs/ecryptfs/crypto.c:348! regression?
- From: Arnd Hannemann <arnd@xxxxxxxxxx>
- Re: [PATCH] eCryptfs: Check array bounds for filename characters
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] eCryptfs: Check array bounds for filename characters
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Check array bounds for filename characters
- From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
- Re: eCryptfs tree back on git.kernel.org
- From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
- [PATCH] eCryptfs: Flush file in vma close
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] eCryptfs: Prevent file create race condition
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- eCryptfs tree back on git.kernel.org
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- [PATCH] ecryptfs: Use kmemdup rather than duplicating its implementation
- From: Thomas Meyer <thomas@xxxxxxxx>
- [PATCH] MAINTAINERS: Update eCryptfs maintainer address
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Full lockup when compiling kernel with "optimal" number of threads
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: Full lockup when compiling kernel with "optimal" number of threads
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: Oops in ecryptfs (apparently) with 3.1-rc6
- From: Luciano Coelho <coelho@xxxxxx>
- Re: Oops in ecryptfs (apparently) with 3.1-rc6
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: Oops in ecryptfs (apparently) with 3.1-rc6
- From: Dustin Kirkland <kirkland@xxxxxxxxxxxxx>
- Re: Oops in ecryptfs (apparently) with 3.1-rc6
- From: Luciano Coelho <coelho@xxxxxx>
- [PATCH] ecryptfs/crypto.c: local functions should be static
- From: H Hartley Sweeten <hartleys@xxxxxxxxxxxxxxxxxxx>
- [PATCH] ecryptfs/inode.c: local functions should be static
- From: H Hartley Sweeten <hartleys@xxxxxxxxxxxxxxxxxxx>
- Oops in ecryptfs (apparently) with 3.1-rc6
- From: Luciano Coelho <coelho@xxxxxx>
- Full lockup when compiling kernel with "optimal" number of threads
- From: Pavel Ivanov <paivanof@xxxxxxxxx>
- Re: [PATCH 2/2] ecryptfs: Preallocate space in lower file in write path
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.1-rc2
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxxxxxxx>
- Re: kernel BUG at fs/ecryptfs/read_write.c:47!
- From: Tomasz Chmielewski <mangoo@xxxxxxxx>
- Re: kernel BUG at fs/ecryptfs/read_write.c:47!
- From: Dustin Kirkland <kirkland@xxxxxxxxxx>
- kernel BUG at fs/ecryptfs/read_write.c:47!
- From: Tomasz Chmielewski <mangoo@xxxxxxxx>
- [GIT PULL] eCryptfs fixes for 3.1-rc1
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] ecryptfs: Make inode bdi consistent with superblock bdi
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxxxxxxx>
- [PATCH 2/2] ecryptfs: Preallocate space in lower file in write path
- From: Thieu Le <thieule@xxxxxxxxxxxx>
- Re: [PATCH v3] eCryptfs: Unlock keys needed by ecryptfsd
- From: Roberto Sassu <roberto.sassu@xxxxxxxxx>
- [PATCH v3] eCryptfs: Unlock keys needed by ecryptfsd
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxxxxxxx>
[Index of Archives]
[Linux Crypto]
[Device Mapper Crypto]
[LARTC]
[Linux Security]
[Bugtraq]
[Yosemite News]
[Samba]