Received-SPF: softfail (google.com: domain of transitioning linux-ext4-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     linux-ext4@vger.kernel.org,
        Artem Blagodarenko <artem.blagodarenko@gmail.com>
Cc:     "Theodore Ts'o" <tytso@mit.edu>, adilger.kernel@dilger.ca,
        Andrew Perepechko <andrew.perepechko@hpe.com>
Subject: Re: [PATCH v2] ext4: truncate during setxattr leads to kernel panic
Date:   Fri, 25 Mar 2022 14:49:50 -0400
Message-Id: <164823418309.637667.12757298463000030100.b4-ty@mit.edu>
In-Reply-To: <20220312231830.103920-1-artem.blagodarenko@gmail.com>
References: <20220312231830.103920-1-artem.blagodarenko@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Sat, 12 Mar 2022 18:18:30 -0500, Artem Blagodarenko wrote:
> From: Andrew Perepechko <andrew.perepechko@hpe.com>
> 
> When changing a large xattr value to a different large xattr value,
> the old xattr inode is freed. Truncate during the final iput causes
> current transaction restart. Eventually, parent inode bh is marked
> dirty and kernel panic happens when jbd2 figures out that this bh
> belongs to the committed transaction.
> 
> [...]

Applied, thanks!

[1/1] ext4: truncate during setxattr leads to kernel panic
      commit: c7cded845fc192cc35a1ca37c0cd957ee35abdf8

Best regards,
-- 
Theodore Ts'o <tytso@mit.edu>