From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 219200] update from 6.11.0-rc1 to 6.11.0-rc5 causes file system check every boot
Date: Tue, 27 Aug 2024 05:17:58 +0000 [thread overview]
Message-ID: <bug-219200-13602-tdGr5LT7hK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219200-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219200
--- Comment #1 from ebiggers@kernel.org ---
On Tue, Aug 27, 2024 at 12:04:56AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=219200
>
> Bug ID: 219200
> Summary: update from 6.11.0-rc1 to 6.11.0-rc5 causes file
> system check every boot
> Product: File System
> Version: 2.5
> Hardware: All
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P3
> Component: ext2
> Assignee: fs_ext2@kernel-bugs.osdl.org
> Reporter: publiccontact2020@protonmail.com
> Regression: No
>
> Reverting from 6.11.0-rc5 to 6.11.0-rc1 resolves the issue of file system
> check
> at every boot.
>
> This issue is observed accross Debian, Gentoo, Arch and Fedora Rawhide.
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are watching the assignee of the bug.
This was already fixed by the following commit:
commit 232590ea7fc125986a526e03081b98e5783f70d2
Author: Christian Brauner <brauner@kernel.org>
Date: Mon Aug 19 10:38:23 2024 +0200
Revert "pidfd: prevent creation of pidfds for kthreads"
--
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:[~2024-08-27 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 0:04 [Bug 219200] New: update from 6.11.0-rc1 to 6.11.0-rc5 causes file system check every boot bugzilla-daemon
2024-08-27 5:17 ` Eric Biggers
2024-08-27 5:17 ` bugzilla-daemon [this message]
2024-08-27 11:07 ` [Bug 219200] " 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-219200-13602-tdGr5LT7hK@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