From: Arthur Marsh <arthur.marsh@internode.on.net>
To: Josh Boyer <jwboyer@gmail.com>
Cc: miklos@szeredi.hu, viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: fuse: implement i_op->atomic_open() prevents writes to ntfs-3g filesystem
Date: Mon, 13 Aug 2012 02:20:31 +0930 [thread overview]
Message-ID: <5027DED7.3050606@internode.on.net> (raw)
In-Reply-To: <CA+5PVA6B7aOnsH6w=4vixe2c9OgR5gvKB+QaQ-Tpy-7rw-tqeQ@mail.gmail.com>
Josh Boyer wrote, on 13/08/12 00:07:
> On Sun, Aug 12, 2012 at 9:59 AM, Arthur Marsh
...
>> Has this problem been seen by anyone else?
>
> Yep, it was reported in Fedora last week.
>
>> Is a fix already in the works?
>
> Miklos posted this patch series that fixed things:
>
> http://thread.gmane.org/gmane.linux.file-systems/66445/focus=1339000
>
> josh
>
Thanks, after applying these 4 patches to the current Linus git head,
the resulting kernel has no problems creating files with ntfs-3g.
Arthur.
prev parent reply other threads:[~2012-08-12 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 13:59 Arthur Marsh
2012-08-12 14:10 ` richard -rw- weinberger
2012-08-12 14:37 ` Josh Boyer
2012-08-12 16:50 ` Arthur Marsh [this message]
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=5027DED7.3050606@internode.on.net \
--to=arthur.marsh@internode.on.net \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome