Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp56281ybv; Tue, 18 Feb 2020 17:38:18 -0800 (PST) X-Google-Smtp-Source: APXvYqywfMVzkkSSifymparEdkb2RNrijJs85uqF6eyxghIsc3rZYu97kFauAVcUoT/+Q8PRkAHz X-Received: by 2002:a9d:4801:: with SMTP id c1mr18472279otf.258.1582076298439; Tue, 18 Feb 2020 17:38:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582076298; cv=none; d=google.com; s=arc-20160816; b=hbXbvnLZEaNzX0vDfB5BcrsCHtPEYXfv3RfMNCrjBoiZHHihkvLxKu5HVuExZtM9KV KI8nBPpBwX6VXhzHQMvT63REFyBFt8RErW5o4mIPpF+9TaUL7mbxkfNqSLmQFqt+Q7v/ C1TtitLs1Vx4+shN9zMp+w+uwZI2dk52PYkp6eLhOroxMYmF7jSNgrTD6KJGNQuKiLzi nflkJEkqQxtijdl4wDNsirpBlRm0cCgqFCTkZ7Rv4aTFh4XyAplLQ/WiN9+ulEYdR+WK tboidoppiZc7d8SA5+CCSrObanIvvGbSIdG06UJkrlAxmT5gMgDXzYfoTI8bADcWsMUZ tQDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=1YeOd9uo3Rq2skMsNEuAFJimpSsCP2dpyPDTjtiFOT0=; b=qFF3G4tthoERv91rAFT9I5UJwVgcVA6UXfUWRNtmNEcrJKbSUHYAiCxXeqx/LdA5ug 6irMNurSeqNo6yvtSyZFv2VnBzBFiFeiCeZKrpRXyt7Zd20DE4Hm8YD8r6GTBWJ+xXB8 7N2j2lsfazmzqVpE/3hYJPNdX74REpBZwbo2JFjrKZxRR9PCIOv4uK3SSlPgfr84PE6C CYHL2P7Qn8wD6oCl+V9QQIHjjDR/tIFdqD94DxyBlGeNhFHER8/w9Mx/kP0k59LTZwKf ivQi9e8m7+AKValgJrXw6FWKyDGSzao+6t2VZDfpbOG+zDaoeE+Z4RVyTK+4SOVHjOfs WJhw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hMzCaOIF; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l19si8339944oii.54.2020.02.18.17.38.06; Tue, 18 Feb 2020 17:38:18 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hMzCaOIF; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726922AbgBSBhd (ORCPT + 99 others); Tue, 18 Feb 2020 20:37:33 -0500 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:27315 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726567AbgBSBhd (ORCPT ); Tue, 18 Feb 2020 20:37:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1582076252; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1YeOd9uo3Rq2skMsNEuAFJimpSsCP2dpyPDTjtiFOT0=; b=hMzCaOIFW41kvcv9tbcFDTz80OoemSqKu6Xz2Nlj7DJtYNDCWLUHaI7MiAgH26jDDuKRh7 4ycZ0QXNMIqH7WYQL/mwHjHouOrXAld3N8su8T47hXVT8s7h8pDeE3831iZOeSHD83vj66 OQwaZA9k5i3PCNov0/wca+uW+uR9QM0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-172-gbr0Imr6PB-e84fKDCbUlQ-1; Tue, 18 Feb 2020 20:37:28 -0500 X-MC-Unique: gbr0Imr6PB-e84fKDCbUlQ-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9EF3E8017CC; Wed, 19 Feb 2020 01:37:26 +0000 (UTC) Received: from ming.t460p (ovpn-8-21.pek2.redhat.com [10.72.8.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id F414560C81; Wed, 19 Feb 2020 01:37:18 +0000 (UTC) Date: Wed, 19 Feb 2020 09:37:14 +0800 From: Ming Lei To: Jesse Barnes Cc: Salman Qazi , Ming Lei , Bart Van Assche , Jens Axboe , Christoph Hellwig , Linux Kernel Mailing List , linux-block , Gwendal Grignou Subject: Re: BLKSECDISCARD ioctl and hung tasks Message-ID: <20200219013714.GB31488@ming.t460p> References: <20200213082643.GB9144@ming.t460p> <20200215034652.GA19867@ming.t460p> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 18, 2020 at 08:11:53AM -0800, Jesse Barnes wrote: > On Fri, Feb 14, 2020 at 7:47 PM Ming Lei wrote: > > What are the 'other operations'? Are they block IOs? > > > > If yes, that is why I suggest to fix submit_bio_wait(), which should cover > > most of sync bio submission. > > > > Anyway, the fix is simple & generic enough, I'd plan to post a formal > > patch if no one figures out better doable approaches. > > Yeah I think any block I/O operation that occurs after the > BLKSECDISCARD is submitted will also potentially be affected by the > hung task timeouts, and I think your patch will address that. My only > concern with it is that it might hide some other I/O "hangs" that are > due to device misbehavior instead. Yes driver and device timeouts > should generally catch those, but with this in place we might miss a > few bugs. We may add a warning(device name, request, ...) when one IO isn't completed in sysctl_hung_task_timeout_secs, so this device misbehavior still can be caught. > > Given the nature of these types of storage devices though, I think > that's a minor issue and not worth blocking the patch on, given that > it should prevent a lot of false positive hang reports as Salman > demonstrated. OK, I will post it soon. Thanks, Ming