linux-kernel - Re: [LTP] 56cbb429d9: ltp.fs

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: <CAHk-=wg+yRjY_AUrjbgrN59OeGAWMF_q=-Dqf2cYtVzoY01j7Q@mail.gmail.com>
Date:   Thu, 25 Jul 2019 09:32:13 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Cyril Hrubis <chrubis@...e.cz>
Cc:     kernel test robot <rong.a.chen@...el.com>,
        Al Viro <viro@...iv.linux.org.uk>, LKP <lkp@...org>,
        LKML <linux-kernel@...r.kernel.org>, ltp@...ts.linux.it
Subject: Re: [LTP] 56cbb429d9: ltp.fs_fill.fail

On Thu, Jul 25, 2019 at 6:26 AM Cyril Hrubis <chrubis@...e.cz> wrote:
>
> This looks like mkfs.vfat got EBUSY after the loop device was
> succesfully umounted.

Hmm. Smells like the RCU-delaying got triggered again.

We have that "synchronize_rcu_expedited()" in namespace_unlock(),
which is so that everything should be done by the time we return to
user space.

Al, maybe that RCU synchronization should be after the mntput()s?

               Linus