From: Artem Bityutskiy <dedekind@infradead.org>
To: "Aurélien GÉRÔME" <ag@debian.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mtd@lists.infradead.org, Adrian.Hunter@nokia.com
Subject: Re: UBIFS: "sync" mount option does not work
Date: Fri, 29 May 2009 13:03:47 +0300 [thread overview]
Message-ID: <1243591427.11172.108.camel@localhost.localdomain> (raw)
In-Reply-To: <1243591249.11172.106.camel@localhost.localdomain>
On Fri, 2009-05-29 at 13:00 +0300, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> Subject: [PATCH] UBIFS: allow sync option in rootflags
> MIME-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: 8bit
>
> When passing UBIFS parameters via kernel command line, the
> sync option will be passed to UBIFS as a string, not as an
> MS_SYNCHRONOUS flag. Teach UBIFS interpreting this flag.
>
> Reported-by: Aurélien GÉRÔME <ag@debian.org>
> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> ---
> fs/ubifs/super.c | 40 +++++++++++++++++++++++++++++++++++-----
> 1 files changed, 35 insertions(+), 5 deletions(-)
Please, use this patch as a band-aid so far. Not sure it'll
land upstream in this form.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind@infradead.org>
To: "Aurélien GÉRÔME" <ag@debian.org>
Cc: linux-mtd@lists.infradead.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Adrian.Hunter@nokia.com
Subject: Re: UBIFS: "sync" mount option does not work
Date: Fri, 29 May 2009 13:03:47 +0300 [thread overview]
Message-ID: <1243591427.11172.108.camel@localhost.localdomain> (raw)
In-Reply-To: <1243591249.11172.106.camel@localhost.localdomain>
On Fri, 2009-05-29 at 13:00 +0300, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> Subject: [PATCH] UBIFS: allow sync option in rootflags
> MIME-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: 8bit
>
> When passing UBIFS parameters via kernel command line, the
> sync option will be passed to UBIFS as a string, not as an
> MS_SYNCHRONOUS flag. Teach UBIFS interpreting this flag.
>
> Reported-by: Aurélien GÉRÔME <ag@debian.org>
> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> ---
> fs/ubifs/super.c | 40 +++++++++++++++++++++++++++++++++++-----
> 1 files changed, 35 insertions(+), 5 deletions(-)
Please, use this patch as a band-aid so far. Not sure it'll
land upstream in this form.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-29 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 17:06 UBIFS: "sync" mount option does not work Aurélien GÉRÔME
2009-05-29 10:00 ` Artem Bityutskiy
2009-05-29 10:00 ` Artem Bityutskiy
2009-05-29 10:03 ` Artem Bityutskiy [this message]
2009-05-29 10:03 ` Artem Bityutskiy
2009-05-29 13:20 ` Aurélien GÉRÔME
2009-05-29 13:26 ` Artem Bityutskiy
2009-05-29 13:26 ` 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=1243591427.11172.108.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=Adrian.Hunter@nokia.com \
--cc=ag@debian.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.