From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 214655] BUG: unable to handle kernel paging request in __dquot_free_space
Date: Wed, 20 Oct 2021 16:43:16 +0000 [thread overview]
Message-ID: <bug-214655-13602-lxcKc9r6vN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214655-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214655
Jan Kara (jack@suse.cz) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jack@suse.cz
--- Comment #1 from Jan Kara (jack@suse.cz) ---
Thanks for report. I'll try to reproduce this in my test VM. I have recently
merged some fixes for detecting corrupted quota files from Zhang Yi so maybe
this is already fixed but let's see...
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-10-20 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 1:16 [Bug 214655] New: BUG: unable to handle kernel paging request in __dquot_free_space bugzilla-daemon
2021-10-20 16:43 ` bugzilla-daemon [this message]
2021-10-20 17:00 ` [Bug 214655] " 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-214655-13602-lxcKc9r6vN@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).