From: Miklos Szeredi <miklos@szeredi.hu>
To: Mikhail Efremov <sem@altlinux.ru>
Cc: Mateusz Guzik <mguzik@redhat.com>,
Mikhail Efremov <sem@altlinux.org>,
LKML <linux-kernel@vger.kernel.org>,
Miklos Szeredi <mszeredi@suse.cz>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] vfs: Don't exchange filenames unconditionally.
Date: Tue, 23 Sep 2014 18:19:06 +0200 [thread overview]
Message-ID: <CAELBmZDEEwp1bH9FKBouy+q86u_KLHBth=JvGy_dVLN7bEbmkQ@mail.gmail.com> (raw)
In-Reply-To: <20140919182221.0d8c2a92@sem.office.altlinux.ru>
On Fri, Sep 19, 2014 at 4:22 PM, Mikhail Efremov <sem@altlinux.ru> wrote:
> On Thu, 18 Sep 2014 13:22:07 +0200 Mateusz Guzik wrote:
>> On Thu, Sep 18, 2014 at 02:55:00PM +0400, Mikhail Efremov wrote:
>> > Only exchange source and destination filenames
>> > if flags contain RENAME_EXCHANGE.
Acked-by: Miklos Szeredi <mszeredi@suse.cz>
>>
>> But names are still exchanged without RENAME_EXCHANGE, provided they are
>> long enough.
>>
>> da1ce0670c14 introduced this behaviour also for short names and this is
>> what you are reverting here.
>>
>> That said, I think the patch is fine as an interim change, but should
>> note facts mentioned above.
>>
>> For more info please see https://lkml.org/lkml/2014/9/7/6
>
> Thanks for pointing out that thread to me, I didn't read it before
> sending the patch.
>
>> I'll be posting a RFC patch for actual problem next week.
>
> I suppose then that no sense to resend this patch right now, I'll just
> wait the proper solution from you.
> Yet this patch can be used as a temporary workaround (as you mentioned
> above) if the proper solution takes longer than expected to implement.
Yes, feel free to resend it to Linus, before 3.17 proper is out.
Also please consider adding:
Cc: stable@vger.kernel.org
Thanks,
Miklos
prev parent reply other threads:[~2014-09-23 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 10:55 [PATCH] vfs: Don't exchange filenames unconditionally Mikhail Efremov
2014-09-18 11:22 ` Mateusz Guzik
2014-09-19 14:22 ` Mikhail Efremov
2014-09-23 16:19 ` Miklos Szeredi [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='CAELBmZDEEwp1bH9FKBouy+q86u_KLHBth=JvGy_dVLN7bEbmkQ@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mguzik@redhat.com \
--cc=mszeredi@suse.cz \
--cc=sem@altlinux.org \
--cc=sem@altlinux.ru \
--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;
as well as URLs for NNTP newsgroup(s).