From: Richard Weinberger <richard@nod.at>
To: Sylvain Etienne <seti@dadboo.eu>,
linux-mtd@lists.infradead.org,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH] ubifs: switch_gc_head: remove redondant sync of wbuf
Date: Thu, 23 Jun 2016 09:47:15 +0200 [thread overview]
Message-ID: <576B9403.7040100@nod.at> (raw)
In-Reply-To: <20160623055344.GA5896@dadboo.eu>
Am 23.06.2016 um 07:53 schrieb Sylvain Etienne:
> The wbuf is already sync-ed before ubifs_leb_unmap()
>
> Signed-off-by: Sylvain Etienne <seti@dadboo.eu>
> ---
>
> Notes:
> This is my first patch on this mailing list. Please let me know if I missed
> something.
>
> fs/ubifs/gc.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/fs/ubifs/gc.c b/fs/ubifs/gc.c
> index 9718da8..821b348 100644
> --- a/fs/ubifs/gc.c
> +++ b/fs/ubifs/gc.c
> @@ -100,10 +100,6 @@ static int switch_gc_head(struct ubifs_info *c)
> if (err)
> return err;
>
> - err = ubifs_wbuf_sync_nolock(wbuf);
> - if (err)
> - return err;
> -
> err = ubifs_add_bud_to_log(c, GCHD, gc_lnum, 0);
> if (err)
> return err;
This call was introduced by:
commit cb14a18465686ea6add51b1008865b8174c28bd7
Author: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Date: Sun May 15 14:51:54 2011 +0300
UBIFS: synchronize write-buffer before switching to the next bud
Which basically syncs the wbuf before each ubifs_add_bud_to_log().
In switch_gc_head() we synced already before ubifs_leb_unmap().
So either the said commit oversaw that sync call or I miss something.
But AFACT your change is correct. Artem, can you please confirm?
Boris, didn't discuss that redundancy while inspecting UBIFS wrt. MLC
support?
Thanks,
//richard
next prev parent reply other threads:[~2016-06-23 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 5:53 [PATCH] ubifs: switch_gc_head: remove redondant sync of wbuf Sylvain Etienne
2016-06-23 7:47 ` Richard Weinberger [this message]
2016-06-23 7:49 ` Boris Brezillon
2016-06-27 10:50 ` 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=576B9403.7040100@nod.at \
--to=richard@nod.at \
--cc=boris.brezillon@free-electrons.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=seti@dadboo.eu \
/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).