linux-ext4 - Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAN0j2-cp1odcT44ZoeFDGHMF519F2b9Ffa5vc8PJyJfSLcj5-Q@mail.gmail.com>
Date:	Tue, 17 May 2016 19:35:06 -0700
From:	Kamran Khan <krkhan@...pirated.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Difference in jbd2 behavior between CentOS and Ubuntu while unmounting

Yup, the kernel versions are drastically different. It's 3.10 vs 4.2.

The problem on 3.10 though is, while jbd2 holds on to the unmounted
device I cannot even rmmod jbd2 or ext4 *even if no other ext
filesystems are mounted*. That lock makes it all but impossible to do
anything with the block device.

On Tue, May 17, 2016 at 7:17 PM, Eric Sandeen <sandeen@...hat.com> wrote:
> On 5/17/16 7:46 PM, Kamran Khan wrote:
>> I'm trying to understand the difference in jbd2 behavior across Ubuntu
>> 14.04 and Centos 7.1. Will appreciate any help.
>
> For starters, what kernel versions are those?  (I know what centos
> is, "3.10.0" with updates, which I can check out, but I have no idea
> what might be in the Ubuntu distro)
>
> -Eric



-- 
Kamran.

http://inspirated.com/
--
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