Re: [PATCH 1/3] ext4: require key for truncate(2) of encrypted file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Eric Biggers <ebiggers3@xxxxxxxxx>
Subject: Re: [PATCH 1/3] ext4: require key for truncate(2) of encrypted file
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 14 Jun 2017 00:06:14 -0700
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-fscrypt@xxxxxxxxxxxxxxx, "Theodore Ts'o" <tytso@xxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-f2fs-devel@xxxxxxxxxxxxxxxxxxxxx, linux-mtd@xxxxxxxxxxxxxxxxxxx, Eric Biggers <ebiggers@xxxxxxxxxx>
In-reply-to: <20170614070357.GB605@zzz>
User-agent: Mutt/1.8.0 (2017-02-23)

On Wed, Jun 14, 2017 at 12:03:57AM -0700, Eric Biggers wrote:
> None of those are allowed because fallocate() requires a file descriptor, and
> open() fails with ENOKEY if the encryption key is not available.  truncate() is
> different because it takes a path, not a file descriptor.

Ok, that makes sense.

References:
- [PATCH 0/3] fscrypt: forbid truncate(2) without key
  - From: Eric Biggers
- [PATCH 1/3] ext4: require key for truncate(2) of encrypted file
  - From: Eric Biggers
- Re: [PATCH 1/3] ext4: require key for truncate(2) of encrypted file
  - From: Christoph Hellwig
- Re: [PATCH 1/3] ext4: require key for truncate(2) of encrypted file
  - From: Eric Biggers

Prev by Date: Re: [PATCH 1/3] ext4: require key for truncate(2) of encrypted file
Next by Date: Re: [git pull] first batch of ufs fixes
Previous by thread: Re: [PATCH 1/3] ext4: require key for truncate(2) of encrypted file
Next by thread: Re: [PATCH 1/3] ext4: require key for truncate(2) of encrypted file
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]