[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170626082315.kun5momxqodrrm67@eorzea.usersys.redhat.com>
Date: Mon, 26 Jun 2017 10:23:15 +0200
From: Carlos Maiolino <cmaiolino@...hat.com>
To: Jeff Layton <jlayton@...hat.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Al Viro <viro@...IV.linux.org.uk>, Jan Kara <jack@...e.cz>,
tytso@....edu, axboe@...nel.dk, mawilcox@...rosoft.com,
ross.zwisler@...ux.intel.com, corbet@....net,
Chris Mason <clm@...com>, Josef Bacik <jbacik@...com>,
David Sterba <dsterba@...e.com>,
"Darrick J . Wong" <darrick.wong@...cle.com>,
Eryu Guan <eguan@...hat.com>,
David Howells <dhowells@...hat.com>,
Christoph Hellwig <hch@...radead.org>,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org,
linux-btrfs@...r.kernel.org, linux-block@...r.kernel.org
Subject: Re: [PATCH v7 05/22] jbd2: don't clear and reset errors after
waiting on writeback
On Fri, Jun 16, 2017 at 03:34:10PM -0400, Jeff Layton wrote:
> Resetting this flag is almost certainly racy, and will be problematic
> with some coming changes.
>
> Make filemap_fdatawait_keep_errors return int, but not clear the flag(s).
> Have jbd2 call it instead of filemap_fdatawait and don't attempt to
> re-set the error flag if it fails.
>
> Signed-off-by: Jeff Layton <jlayton@...hat.com>
> ---
> fs/jbd2/commit.c | 15 +++------------
> include/linux/fs.h | 2 +-
> mm/filemap.c | 16 ++++++++++++++--
> 3 files changed, 18 insertions(+), 15 deletions(-)
>
I'm not too experienced with jbd2 internals, but this patch is clear enough:
Reviewed-by: Carlos Maiolino <cmaiolino@...hat.com>
--
Carlos
Powered by blists - more mailing lists