All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
To: "Darrick J. Wong" <darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org,
	ebiggers3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] vfs: abort dedupe loop if fatal signals are pending
Date: Sat, 23 Jan 2016 01:30:21 +0000	[thread overview]
Message-ID: <20160123013021.GL17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20160123005828.GB5496-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>

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.

WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
	ebiggers3@gmail.com, xfs@oss.sgi.com
Subject: Re: [PATCH] vfs: abort dedupe loop if fatal signals are pending
Date: Sat, 23 Jan 2016 01:30:21 +0000	[thread overview]
Message-ID: <20160123013021.GL17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20160123005828.GB5496@birch.djwong.org>

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.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-fsdevel@vger.kernel.org, david@fromorbit.com,
	linux-api@vger.kernel.org, xfs@oss.sgi.com, ebiggers3@gmail.com
Subject: Re: [PATCH] vfs: abort dedupe loop if fatal signals are pending
Date: Sat, 23 Jan 2016 01:30:21 +0000	[thread overview]
Message-ID: <20160123013021.GL17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20160123005828.GB5496@birch.djwong.org>

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.

  parent reply	other threads:[~2016-01-23  1:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-23  0:58 [PATCH] vfs: abort dedupe loop if fatal signals are pending Darrick J. Wong
2016-01-23  0:58 ` Darrick J. Wong
2016-01-23  0:58 ` Darrick J. Wong
     [not found] ` <20160123005828.GB5496-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2016-01-23  1:30   ` Al Viro [this message]
2016-01-23  1:30     ` Al Viro
2016-01-23  1:30     ` Al Viro

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=20160123013021.GL17997@ZenIV.linux.org.uk \
    --to=viro-3bdd1+5odreifsdqtta3olvcufugdwfn@public.gmane.org \
    --cc=darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org \
    --cc=ebiggers3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.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.