lkml.org 
[lkml]   [2016]   [Nov]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH 02/29] fscrypt: Allow fscrypt_decrypt_page() to function with non-writeback pages
    From
    Date
    Eric,

    > On 15.11.2016, at 19:19, Eric Biggers <ebiggers@google.com> wrote:
    >
    > On Sun, Nov 13, 2016 at 10:20:45PM +0100, Richard Weinberger wrote:
    >> /**
    >> * f2crypt_decrypt_page() - Decrypts a page in-place
    >> - * @page: The page to decrypt. Must be locked.
    >> + * @inode: The encrypted inode to decrypt.
    >> + * @page: The page to decrypt. Must be locked.
    >
    > Strictly speaking, it's not the inode itself being decrypted, but rather the
    > data associated with it. Could this be better expressed as something like
    > "The inode to which the page belongs"?

    Yes, you're right. Will address that!

    Thanks,
    David

    \
     
     \ /
      Last update: 2016-11-24 18:44    [W:5.873 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site