linux-ext4 - Re: Oops at shutdown: kernel BUG at fs/ext4/super.c:804!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACFbnrwx6SHjyOzf4nU9tC4mn=YxxN8vNcwSe-90Z_1dQAKvEg@mail.gmail.com>
Date:	Mon, 9 Sep 2013 13:05:00 -0400
From:	Marc Meledandri <m.meledandri@...il.com>
To:	Jan Kara <jack@...e.cz>, linux-ext4@...r.kernel.org
Subject: Re: Oops at shutdown: kernel BUG at fs/ext4/super.c:804!

On Mon, Sep 9, 2013 at 12:23 PM, Jan Kara <jack@...e.cz> wrote:
> On Sun 08-09-13 18:28:40, Marc Meledandri wrote:
>> Been seeing this problem at shutdown on 3.10.x kernels.
>>
>> I saw a previous similar thread, but it seemed related to NFS whereas this is
>> affecting my raid device (dm-0).
>   Well, this is likely caused by inodes in filesystem on dm-0 being still
> held by someone. Are you exporting dm-0 via NFS? Because there have been
> recently bugs in NFS in this area (this patch should have fixed them:
> http://www.spinics.net/lists/kernel/msg1592640.html).
>
Thank you. I'd seen that patch, but don't have a remotely similar
configuration as specified in the STR. I also thought NFS was out of
the picture at that stage of the shutdown, but after re-reading the
patch notes, it looks like the earlier delegation may do the trick for
my standard NFS implementation as well. I'll test with this patch.
Looks hopeful.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html