linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sahitya Tummala <stummala@codeaurora.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck on encrypted directories
Date: Wed, 2 Aug 2017 12:43:27 +0530	[thread overview]
Message-ID: <045b2521-e3bb-7a5c-3bee-cc3d7308b254@codeaurora.org> (raw)
In-Reply-To: <20170801143343.7kphdxfvw7qzth3z@thunk.org>


On 8/1/2017 8:03 PM, Theodore Ts'o wrote:
> On Fri, Jul 28, 2017 at 03:32:24PM +0530, Sahitya Tummala wrote:
>> Hi Ted,
>>
>> I got a question on usage of e2fsck with -D option on EXT4 FS, where
>> file based encryption is enabled. Is this option supposed to work on
>> encrypted directories?
>>
>> I have encountered a case where e2fsck gets stuck
>> in duplicate_search_and_fix() due to strncmp checks done in this function
>> on encrypted file names, which may contain NUL characters.
>>
>> Also, even without -D option passed, there can be a case of duplicate
>> entries (i.e.,
>> ctx->dirs_to_hash is not NULL). In this case too we may see the same issue
>> in duplicate_search_and_fix() if the directory is encrypted.
>> Is my understanding correct? Please share your comments.
> Thanks, your understanding is indeed correct.  Thanks for pointing
> this out.  The following patch should fix the problem; can you
> confirm, if you have a convenient test case?

Thanks for the patch. I could reproduce this issue only once so far. I 
have already
tried the proposed fix and it works fine.

-- 
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.

      parent reply	other threads:[~2017-08-02  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 10:02 e2fsck on encrypted directories Sahitya Tummala
2017-08-01 14:33 ` Theodore Ts'o
2017-08-01 19:18   ` Eric Biggers
2017-08-02  7:13   ` Sahitya Tummala [this message]

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=045b2521-e3bb-7a5c-3bee-cc3d7308b254@codeaurora.org \
    --to=stummala@codeaurora.org \
    --cc=linux-ext4@vger.kernel.org \
    --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: link
Be 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).