From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
linux-ext4@vger.kernel.org, linux-fscrypt@vger.kernel.org,
Eric Biggers <ebiggers@kernel.org>,
Disha Goel <disgoel@linux.ibm.com>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>, Jan Kara <jack@suse.cz>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH 6.6] ext4: don't enable DAX on new encrypted files
Date: Thu, 27 Aug 2026 21:46:20 -0400 [thread overview]
Message-ID: <20260827-stable-daily-0007-ext4-dax-6-6@kernel.org> (raw)
In-Reply-To: <20260827032857.82762-1-ebiggers@kernel.org>
> commit da32af420d6d466e247c43ac0b829edeac7ae0ad upstream.
>
> Currently, when a new encrypted regular file is created, the call to
> ext4_set_inode_flags(inode, init=true) in __ext4_new_inode() is made
> before EXT4_INODE_ENCRYPT is set. As a result, it can set S_DAX if the
> filesystem is mounted with "-o dax=always".
Queued for 6.6, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-08-28 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 3:28 [PATCH 6.6] ext4: don't enable DAX on new encrypted files Eric Biggers
2026-08-27 3:40 ` sashiko-bot
2026-08-28 1:46 ` Sasha Levin [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=20260827-stable-daily-0007-ext4-dax-6-6@kernel.org \
--to=sashal@kernel.org \
--cc=disgoel@linux.ibm.com \
--cc=ebiggers@kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=stable@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