linux-kernel - Re: [PATCH] drivers/staging/exfat - by default, prohibit mount of fat/vfat

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]

Date:   Sun, 1 Sep 2019 04:05:14 +0100
From:   Al Viro <viro@...iv.linux.org.uk>
To:     Gao Xiang <hsiangkao@....com>
Cc:     Dave Chinner <david@...morbit.com>,
        Valdis Klētnieks <valdis.kletnieks@...edu>,
        Christoph Hellwig <hch@...radead.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Sasha Levin <alexander.levin@...rosoft.com>,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers/staging/exfat - by default, prohibit mount of
 fat/vfat

On Sun, Sep 01, 2019 at 09:37:19AM +0800, Gao Xiang wrote:

> fs/orangefs/file.c
>  19 static int flush_racache(struct inode *inode)

Just why the hell would _that_ one be a problem?  It's static in
file; it can't pollute the namespace even if linked into the
kernel.

Folks, let's keep at least some degree of sanity - this is sinking
to the level of certain killfile denizens...