From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 205197] kernel BUG at fs/ext4/extents_status.c:884
Date: Tue, 13 May 2025 03:03:00 +0000 [thread overview]
Message-ID: <bug-205197-13602-pEubYZblf0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205197-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205197
Andrew.C.Lee (lichuan1@hisense.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lichuan1@hisense.com
--- Comment #12 from Andrew.C.Lee (lichuan1@hisense.com) ---
(In reply to Antony Amburose from comment #9)
> Sorry for the very late reply. We have worked on this issue further and
> understand that, the issue happen when an ongoing encryption is interrupted.
> In the next boot, when the system tries to mount the partition which is in
> partially encrypted state hits a bug on. This is fixed in AOSP by
> implementing a logic to identify interrupted encrypted partition. This is
> not a ext4 bug. Thanks for all the hints.
> I will close this bug.
Hi Antony, could you please let us know which patch was used to resolve it?
Thank you for your assistance.
Best regards,
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-05-13 3:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 12:38 [Bug 205197] New: kernel BUG at fs/ext4/extents_status.c:884 bugzilla-daemon
2019-10-15 13:53 ` [Bug 205197] " bugzilla-daemon
2019-10-17 6:50 ` bugzilla-daemon
2019-10-23 13:13 ` bugzilla-daemon
2019-10-24 6:58 ` bugzilla-daemon
2024-03-04 4:17 ` bugzilla-daemon
2024-03-14 21:31 ` bugzilla-daemon
2024-03-15 12:14 ` bugzilla-daemon
2024-03-15 17:03 ` bugzilla-daemon
2024-08-06 11:27 ` bugzilla-daemon
2024-08-06 11:29 ` bugzilla-daemon
2024-08-06 11:30 ` bugzilla-daemon
2024-08-12 16:01 ` bugzilla-daemon
2025-05-13 3:03 ` bugzilla-daemon [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=bug-205197-13602-pEubYZblf0@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.