linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 205197] kernel BUG at fs/ext4/extents_status.c:884
Date: Mon, 04 Mar 2024 04:17:35 +0000	[thread overview]
Message-ID: <bug-205197-13602-P0hTFieP5O@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205197-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205197

Antony Amburose (antony.ambrose@in.bosch.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |antony.ambrose@in.bosch.com

--- Comment #5 from Antony Amburose (antony.ambrose@in.bosch.com) ---
Working with a 5.4.233 on aarch64 (Qualcomm/Android) platform we get the same
error. I am able to reliably reproduce this problem even after applying the
patch #1.Could you please let me know what additional information required ?
As the partition is FBE encrypted , I am not able to look at the hex dump to
check the nature corruption.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-03-04  4:17 UTC|newest]

Thread overview: 9+ 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 [this message]
2024-03-14 21:31 ` bugzilla-daemon
2024-03-15 12:14 ` bugzilla-daemon
2024-03-15 17:03 ` bugzilla-daemon

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-P0hTFieP5O@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 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).