From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH] btrfs: don't return EINTR
Date: Tue, 17 Apr 2012 11:24:01 -0400
Message-ID: <20120417152401.GL28915@shiny>
References: <1334408175-6568-1-git-send-email-sensille@gmx.net>
 <4F8D7B04.9050904@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-btrfs@vger.kernel.org
To: Arne Jansen <sensille@gmx.net>, Josef Bacik <josef@redhat.com>
Return-path: <linux-btrfs-owner@vger.kernel.org>
In-Reply-To: <4F8D7B04.9050904@gmx.net>
List-ID: <linux-btrfs.vger.kernel.org>

On Tue, Apr 17, 2012 at 04:15:32PM +0200, Arne Jansen wrote:
> On 14.04.2012 14:56, Arne Jansen wrote:
> > It is basically a good thing if we are interruptible when waiting for
> > free space, but the generality in which it is implemented currently
> > leads to system calls being interruptible that are not documented this
> > way. For example git can't handle interrupted unlink(), leading to
> > corrupt repos under space pressure.
> 
> Is this patch a candidate for the next rc?

The EINTR came from Josef.  We do want to be able to break out of long
flushes, but I want to check with him to see if there was a specific bug
this was solving?

-chris