From: Oleksij Rempel <ore@pengutronix.de>
To: Richard Weinberger <richard@nod.at>, Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-mtd@lists.infradead.org,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Steffen Trumtrar <s.trumtrar@pengutronix.de>
Subject: Re: [PATCH v2 3/3] fs: ubifs: set s_uuid in super block
Date: Tue, 9 May 2017 06:13:26 +0200 [thread overview]
Message-ID: <3fa90f95-c522-ad9f-3f4c-8c45a6cd93c1@pengutronix.de> (raw)
In-Reply-To: <b7d49751-8345-b5c4-1b6d-761e91ddd89e@nod.at>
On 05/02/2017 09:37 AM, Richard Weinberger wrote:
> Amir,
>
> Am 02.05.2017 um 09:19 schrieb Amir Goldstein:
>> On Fri, Apr 28, 2017 at 1:03 AM, Richard Weinberger <richard@nod.at> wrote:
>>> Am 24.04.2017 um 17:47 schrieb Richard Weinberger:
>>>>> So, if some flag should be implemented, who should do it? :)
>>>>
>>>> I'll not do it for you. ;)
>>>
>>> Please also see http://marc.info/?l=linux-fsdevel&m=149327990608749&w=2
>>>
>>
>> Richard,
>>
>> Considering the facts that:
>> 1. I proposed the said flag and Al didn't think it was needed [1]
>> 2. ext4 already sets s_uuid without any flag for a long time now
>> 3. A similar patch was queued for v4.12 to set s_uuid for xfs without any flag
>>
>> I think it would be right to take Oleksij's patch as is.
>>
>> FYI, my current work on 'constant inode numbers for overlayfs' requires that
>> underlying filesystem had set a non-zero s_uuid. Not sure if that matters for
>> ubifs+overlayfs users.
>
> If VFS maintainers are fine with that, I'll take it.
> From UBIFS' POV it does not matter much. :-)
Ping to VFS maintainers?
next prev parent reply other threads:[~2017-05-09 4:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 9:50 [PATCH v2 0/3] make ubifs compatible with IMA and EVM Oleksij Rempel
2017-04-11 9:50 ` [PATCH v2 1/3] fs: ubifs: parse iversion mount option Oleksij Rempel
2017-04-11 9:50 ` [PATCH v2 2/3] fs: ubifs: update i_version on inode changes Oleksij Rempel
2017-04-11 16:05 ` Christoph Hellwig
2017-04-11 21:13 ` Richard Weinberger
2017-04-12 6:05 ` Oleksij Rempel
2017-04-12 6:08 ` Christoph Hellwig
2017-04-12 7:04 ` Oleksij Rempel
2017-04-24 15:44 ` Richard Weinberger
2017-04-11 9:50 ` [PATCH v2 3/3] fs: ubifs: set s_uuid in super block Oleksij Rempel
2017-04-11 20:43 ` Richard Weinberger
2017-04-12 5:48 ` Christoph Hellwig
2017-04-12 7:15 ` Oleksij Rempel
2017-04-24 15:47 ` Richard Weinberger
2017-04-27 22:03 ` Richard Weinberger
2017-04-28 8:53 ` Amir Goldstein
2017-05-02 5:30 ` Oleksij Rempel
2017-05-02 7:19 ` Amir Goldstein
2017-05-02 7:37 ` Richard Weinberger
2017-05-09 4:13 ` Oleksij Rempel [this message]
[not found] ` <CAOQ4uxiEGJLSGS5rK8V8GRNvf9aWqbVG5odu2=nv73xTOmvfNQ@mail.gmail.com>
2017-05-09 5:52 ` Oleksij Rempel
2017-05-09 7:01 ` Richard Weinberger
2017-05-09 7:08 ` Amir Goldstein
2017-05-09 7:35 ` Oleksij Rempel
2017-05-09 7:35 ` Richard Weinberger
2017-05-09 7:50 ` Amir Goldstein
2017-05-02 7:23 ` Artem Bityutskiy
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=3fa90f95-c522-ad9f-3f4c-8c45a6cd93c1@pengutronix.de \
--to=ore@pengutronix.de \
--cc=adrian.hunter@intel.com \
--cc=amir73il@gmail.com \
--cc=dedekind1@gmail.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=s.trumtrar@pengutronix.de \
/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).