From: "Yuvaraj Ranganathan (QUIC)" <quic_yrangana@quicinc.com>
To: Theodore Ts'o <tytso@mit.edu>,
"linux-fscrypt@vger.kernel.org" <linux-fscrypt@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Software encryption at fscrypt causing the filesystem access unresponsive
Date: Thu, 25 Jul 2024 07:21:36 +0000 [thread overview]
Message-ID: <08079d01e25748108aedb95a3c30e5e7@quicinc.com> (raw)
In-Reply-To: <20240724162132.GB131596@mit.edu>
Hello Ted,
I don't see fast_commit feature is enabled for this filesystem.
Here are the filesystem features enabled for that disk partition,
Filesystem features:
has_journal ext_attr resize_inode dir_index stable_inodes filetype needs_recovery extent 64bit flex_bg encrypt sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Thanks,
Yuvaraj.
-----Original Message-----
From: Theodore Ts'o <tytso@mit.edu>
Sent: Wednesday, July 24, 2024 9:52 PM
To: Yuvaraj Ranganathan <yrangana@qti.qualcomm.com>
Cc: linux-fscrypt@vger.kernel.org; linux-fsdevel@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: Software encryption at fscrypt causing the filesystem access unresponsive
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
On Wed, Jul 24, 2024 at 02:21:26PM +0000, Yuvaraj Ranganathan wrote:
> Hello developers,
>
> We are trying to validate a Software file based encryption with
> standard key by disabling Inline encryption and we are observing the
> adb session is hung. We are not able to access the same filesystem at
> that moment.
The stack trace seems to indicate that the fast_commit feature is enabled. That's a relatively new feature; can you replicate the hang without fast_commit being enabled?
- Ted
next prev parent reply other threads:[~2024-07-25 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 14:21 Software encryption at fscrypt causing the filesystem access unresponsive Yuvaraj Ranganathan
2024-07-24 16:21 ` Theodore Ts'o
2024-07-25 7:21 ` Yuvaraj Ranganathan (QUIC) [this message]
2024-07-25 7:51 ` 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=08079d01e25748108aedb95a3c30e5e7@quicinc.com \
--to=quic_yrangana@quicinc.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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