Re: [PATCH] vfs: abort dedupe loop if fatal signals are pending

xfs

Re: [PATCH] vfs: abort dedupe loop if fatal signals are pending

To:	"Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Subject:	Re: [PATCH] vfs: abort dedupe loop if fatal signals are pending
From:	Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Date:	Sat, 23 Jan 2016 01:30:21 +0000
Cc:	linux-fsdevel@xxxxxxxxxxxxxxx, david@xxxxxxxxxxxxx, linux-api@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, ebiggers3@xxxxxxxxx
Delivered-to:	xfs@xxxxxxxxxxx
In-reply-to:	<20160123005828.GB5496@xxxxxxxxxxxxxxxx>
References:	<20160123005828.GB5496@xxxxxxxxxxxxxxxx>
Sender:	Al Viro <viro@xxxxxxxxxxxxxxxx>
User-agent:	Mutt/1.5.21 (2010-09-15)

On Fri, Jan 22, 2016 at 04:58:28PM -0800, Darrick J. Wong wrote:
> If the program running dedupe receives a fatal signal during the
> dedupe loop, we should bail out to avoid tying up the system.

Applied.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH] vfs: abort dedupe loop if fatal signals are pending, Darrick J. Wong Re: [PATCH] vfs: abort dedupe loop if fatal signals are pending, Al Viro <=

Previous by Date:	[PATCH] vfs: abort dedupe loop if fatal signals are pending, Darrick J. Wong
Next by Date:	RFCv4+ WIP rollup of XFS reverse-mapping, reflink, and dedupe support, Darrick J. Wong
Previous by Thread:	[PATCH] vfs: abort dedupe loop if fatal signals are pending, Darrick J. Wong
Next by Thread:	RFCv4+ WIP rollup of XFS reverse-mapping, reflink, and dedupe support, Darrick J. Wong
Indexes:	[Date] [Thread] [Top] [All Lists]