From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <axboe@kernel.dk>
Date: Thu, 10 Dec 2015 11:15:40 -0700
From: Jens Axboe <axboe@kernel.dk>
Subject: Re: Exit all jobs on error
Message-ID: <20151210181540.GB21415@kernel.dk>
References: <CALjAwxhfyQ3ppw-MXoRwAkhk4+-LSJSTkZQa32ymKizKU0Ox-A@mail.gmail.com>
 <5669B23C.1020001@kernel.dk>
 <CALjAwxjLXTCRe0Ky08DB6in2aq_czkx5Oz8Osi7Mo=+7eFH9PQ@mail.gmail.com>
 <CANvN+e=CtQBfUmj6fQPUgaqHUXwzwY1SLuXV76n=AG2kLFpWSQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANvN+e=CtQBfUmj6fQPUgaqHUXwzwY1SLuXV76n=AG2kLFpWSQ@mail.gmail.com>
To: Andrey Kuzmin <andrey.v.kuzmin@gmail.com>
Cc: Sitsofe Wheeler <sitsofe@gmail.com>, "fio@vger.kernel.org" <fio@vger.kernel.org>
List-ID: <fio@vger.kernel.org>

On Thu, Dec 10 2015, Andrey Kuzmin wrote:
> I've also encountered a similar issue a number of times where the job
> failed to stop (and refused to terminate in response to C-C) when a
> thread/process fails, e.g. due to an error. My guess is that the loop
> that waits for completions doesn't check for td->terminate being set.

Attach with gdb and see what they are doing, could be a missing
terminate check. Or it could already be sitting waiting for completions.

-- 
Jens Axboe