From: Christoph Hellwig <hch@infradead.org>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <alexander.levin@microsoft.com>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/staging/exfat - by default, prohibit mount of fat/vfat
Date: Fri, 30 Aug 2019 09:45:03 -0700 [thread overview]
Message-ID: <20190830164503.GA12978@infradead.org> (raw)
In-Reply-To: <245727.1567183359@turing-police>
On Fri, Aug 30, 2019 at 12:42:39PM -0400, Valdis Klētnieks wrote:
> Concerns have been raised about the exfat driver accidentally mounting
> fat/vfat file systems. Add an extra configure option to help prevent that.
Just remove that code. This is exactly what I fear about this staging
crap, all kinds of half-a***ed patches instead of trying to get anything
done. Given that you signed up as the maintainer for this what is your
plan forward on it? What development did you on the code and what are
your next steps?
next prev parent reply other threads:[~2019-08-30 16:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 16:42 [PATCH] drivers/staging/exfat - by default, prohibit mount of fat/vfat Valdis Klētnieks
2019-08-30 16:45 ` Christoph Hellwig [this message]
2019-08-31 0:48 ` Valdis Klētnieks
2019-08-31 6:46 ` Christoph Hellwig
2019-08-31 10:25 ` Valdis Klētnieks
2019-08-31 14:24 ` Andy Shevchenko
2019-08-31 14:51 ` Valdis Klētnieks
2019-09-01 1:07 ` Dave Chinner
2019-09-01 1:37 ` Gao Xiang
2019-09-01 3:05 ` Al Viro
2019-09-01 3:26 ` Gao Xiang
2019-09-01 3:37 ` Valdis Klētnieks
2019-09-01 22:43 ` Dave Chinner
2019-09-01 23:13 ` Valdis Klētnieks
2019-09-02 7:38 ` Christoph Hellwig
2019-09-02 7:35 ` Christoph Hellwig
2019-09-02 15:25 ` Greg Kroah-Hartman
2019-09-02 19:00 ` Valdis Klētnieks
2019-09-02 19:06 ` Greg Kroah-Hartman
2019-09-08 10:50 ` OGAWA Hirofumi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190830164503.GA12978@infradead.org \
--to=hch@infradead.org \
--cc=alexander.levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).