From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B2DB7C47255 for ; Mon, 11 May 2020 18:26:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7F68C2070B for ; Mon, 11 May 2020 18:26:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729719AbgEKS0Z convert rfc822-to-8bit (ORCPT ); Mon, 11 May 2020 14:26:25 -0400 Received: from mail.kernel.org ([198.145.29.99]:58844 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729673AbgEKS0Z (ORCPT ); Mon, 11 May 2020 14:26:25 -0400 From: bugzilla-daemon@bugzilla.kernel.org To: linux-ext4@vger.kernel.org Subject: [Bug 207635] EXT4-fs error (device sda3): ext4_lookup:1701: inode #...: comm find: casefold flag without casefold feature; EXT4-fs (sda3): Remounting filesystem read-only Date: Mon, 11 May 2020 18:26:24 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo fs_ext4@kernel-bugs.osdl.org X-Bugzilla-Product: File System X-Bugzilla-Component: ext4 X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: blocking X-Bugzilla-Who: ebiggers3@gmail.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: fs_ext4@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=207635 --- Comment #7 from Eric Biggers (ebiggers3@gmail.com) --- > Someone might use a kernel with casefold or encryption support on Monday - > and even use these features, causing a few of these flags to be set. > > The same person might run a kernel with casefold and/or encryption disabled > on Tuesday. So, would it really be necessary to set their filesystem to ro - > giving them a hard time, just because they like to use different kernels? I > think not. Casefold is an 'incompat' feature, because it changes the directory format. So if someone enables it (on-disk, which is different from merely using a kernel that supports it), then old kernels can't use the filesystem at all. That's working as intended. But that's *not* actually what this issue is about. This issue is about how the kernel treats inodes that got corrupted to have the casefold flag set when the user didn't actually enable the casefold feature. The ext4 feature flags have clear behavior for how unexpected flags are handled, but the inode flags don't. -- You are receiving this mail because: You are watching the assignee of the bug.