[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181005233721.GI12041@dastard>
Date: Sat, 6 Oct 2018 09:37:21 +1000
From: Dave Chinner <david@...morbit.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-xfs@...r.kernel.org
Subject: Re: [PATCH] writeback: fix range_cyclic writeback vs writepages
deadlock
On Fri, Oct 05, 2018 at 12:46:40PM -0700, Andrew Morton wrote:
> On Fri, 5 Oct 2018 15:45:26 +1000 Dave Chinner <david@...morbit.com> wrote:
>
> > From: Dave Chinner <dchinner@...hat.com>
> >
> > We've recently seen a workload on XFS filesystems with a repeatable
> > deadlock between background writeback and a multi-process
> > application doing concurrent writes and fsyncs to a small range of a
> > file.
> >
> > ...
> >
> > Signed-off-by: Dave Chinner <dchinner@...hat.com>
> > Reviewed-by: Jan Kara <jack@...e.de>
>
> Not a serious enough problem for a -stable backport?
Don't have enough evidence to say one way or another. The reported
incident was from a RHEL 7 kernel, so the bug has been there for
years in one form or another, but it's only ever been triggered by
this one-off custom workload.
I haven't done any analysis on older kernels, nor have I looked to see
if there's any gotchas that a stable backport might encounter. And I
tend not to change stuff in a path that is critical to data integrity
without at least doing enough due diligence to suggest a stable
backport would be fine.
You can mark it for stable backports if you want, but I'm not
prepared to because I haven't done the work necessary to ensure it's
safe to do so.
Cheers,
Dave.
--
Dave Chinner
david@...morbit.com
Powered by blists - more mailing lists