Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp594360pxb; Wed, 27 Oct 2021 08:42:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx5gHDadXvxA/qyVVoxi7n9F6Fj1mVbfA5DSQMut6kz2li6TWtYnULDWtVC5AOupqZdaeiI X-Received: by 2002:aa7:83cc:0:b0:455:c394:caba with SMTP id j12-20020aa783cc000000b00455c394cabamr33779957pfn.28.1635349336443; Wed, 27 Oct 2021 08:42:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635349336; cv=none; d=google.com; s=arc-20160816; b=oNfl5Ed9mNCp6GRwl9uifKIpCSHU8oL8bbQIdT/W/WO17GQVVEcvOvhjdpuOMr9N6P crqy7rC4vSDe1VyHicIVb5ZTQvU6mvmOtYplZ87LYzCvoMf70N9Np+++HMZHsqTBVf3l 571dWg7WTPzYR1pNAhtz4AcAK479Y8nQuuTxzlbtdWRuVW8JxY5jYq/U45pJl+nwrImj M0+kKFXDcdkgLq0K8kJQUyVfds0KAz+NH3nEdIaOFZVRQ+dGw6r00hXQqDiPGpRU+nIL gjiZ7hln8g1orsZqn7iAzmfhSbwJZArRv5jBExDyM+ZxZdGuUnD4qNZE1gyV49mt09dA Of2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=6GFlJ/1yKhFUIfKvLc15dlLwuXZ5oRP74dAa8t2k6+Q=; b=PEirVVH51PAf4RA4wimz9wwX2fYybN/aiHrg0YhhfunpR/1j8gX+Mg4H+SBn6LUHe6 KnY6ZbIPHM44H/sapxyG1IpO9PCZHpdGcJ+ej1C3Wf9m6yM8SFrn4KiTKq+YWbOb9vnF n/9vDFOieWH1K0TWPrxDQ7FbyOZwoaFgJmRZGT+CYMBNDL4rH6bidabh4INw7Yn27rpA 5Pw4YCKQPYEtnKZer9Qjso7wpjIof1DiSp7d6fXarj8YpgEZwprsua8y8+cejjYO71gT WqpBb9M2xVlbnsXxneCfgETrNcvdrn4zq2CyAfWdPKPmV46MZWYjVpI5rEwnB6JNM51n 8hEQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=R+gAe9p6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id i15si318594pgl.640.2021.10.27.08.41.41; Wed, 27 Oct 2021 08:42:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=R+gAe9p6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S236637AbhJ0C2Y (ORCPT + 99 others); Tue, 26 Oct 2021 22:28:24 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:31524 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232024AbhJ0C2Y (ORCPT ); Tue, 26 Oct 2021 22:28:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1635301559; 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=6GFlJ/1yKhFUIfKvLc15dlLwuXZ5oRP74dAa8t2k6+Q=; b=R+gAe9p6547UrvTjrpYawCdKt3s9sNESv60eB2IY6BQVnE5s9+2g5e5jM6cACHm/lg9vI3 6ZeEgqO9iYzNWPB2TTJ0NEGI4PQZf/WQujEZEMRXcT0LI8hOjxxRyWAfJ9dBCTguqdSako VvkugYg76sNdqnr7CF1OOhrmflmn0Fo= Received: from mail-lf1-f69.google.com (mail-lf1-f69.google.com [209.85.167.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-176-X3yNBK-nNxSAwOOqPu_6TA-1; Tue, 26 Oct 2021 22:25:57 -0400 X-MC-Unique: X3yNBK-nNxSAwOOqPu_6TA-1 Received: by mail-lf1-f69.google.com with SMTP id p19-20020a056512139300b003ff6dfea137so643505lfa.9 for ; Tue, 26 Oct 2021 19:25:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6GFlJ/1yKhFUIfKvLc15dlLwuXZ5oRP74dAa8t2k6+Q=; b=Yp61giDMoG9A6xa7SN7goclyKnyPSSPFRn/0C/NfdTCXQPRX9Kyd2QDXKW9kqMyGCB 2NQTuV9zn0xXD3W6/dc9Y+oZyqmJYBj/O4XHxlncuSY+jqJ8kfA9PGvRxUdMeDN8nok7 IW04XRllDy4UK3GzGW7Ap/NSZbeCePcURA8bamjy1Devz3hQoK0Ne0PNDkw4nzR1XYrG w/GfKHDyIBsYSbuQiChc3EtfRzUIPXnHXxSfGxUajDh8v3dYzSYmMnlj6qHFDeH0GWFl poAiRrubTHAbZRR7Tn6rdzNp6n+zy6gXuUPOwTCZgnB4TnguJH+n9lth2YeUCrfuTr32 NSjg== X-Gm-Message-State: AOAM530bNmHAgyM5LYzyVBIYGRKNF2zzhttN3Vbi77GFCJb5pz5eLXnq HZbxPTRXsOzPHlgHAOeVtMMPeYLviIG70Z8mHHhVFaJ6ya8nYF+9tiIGVWH/xCi+a8t9LjTpISW LBwPibKSsFMzsieillGkjzHGF8NElfs1qlvMwABCa X-Received: by 2002:a2e:9bd0:: with SMTP id w16mr30330450ljj.390.1635301556305; Tue, 26 Oct 2021 19:25:56 -0700 (PDT) X-Received: by 2002:a2e:9bd0:: with SMTP id w16mr30330429ljj.390.1635301556076; Tue, 26 Oct 2021 19:25:56 -0700 (PDT) MIME-Version: 1.0 References: <20210806142914.70556-1-pkalever@redhat.com> <20210806142914.70556-3-pkalever@redhat.com> In-Reply-To: From: Prasanna Kalever Date: Wed, 27 Oct 2021 07:55:44 +0530 Message-ID: Subject: Re: [PATCH v1 2/2] nbd: reset the queue/io_timeout to default on disconnect To: Josef Bacik , Jens Axboe , linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, nbd@other.debian.org Cc: Ilya Dryomov , Xiubo Li , Prasanna Kumar Kalever , Ming Lei Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 16, 2021 at 1:53 PM Ming Lei wrote: > > On Fri, Aug 06, 2021 at 07:59:14PM +0530, pkalever@redhat.com wrote: > > From: Prasanna Kumar Kalever > > > > Without any changes to NBD_ATTR_TIMEOUT (default is 30 secs), > > $ rbd-nbd map rbd-pool/image0 --try-netlink > > /dev/nbd0 > > $ cat /sys/block/nbd0/queue/io_timeout > > 30000 > > $ rbd-nbd unmap /dev/nbd0 > > $ cat /sys/block/nbd0/queue/io_timeout > > 30000 > > > > Now user sets NBD_ATTR_TIMEOUT to 60, > > $ rbd-nbd map rbd-pool/image0 --try-netlink --io-timeout 60 > > /dev/nbd0 > > $ cat /sys/block/nbd0/queue/io_timeout > > 60000 > > $ rbd-nbd unmap /dev/nbd0 > > $ cat /sys/block/nbd0/queue/io_timeout > > 60000 > > > > Now user doesn't alter NBD_ATTR_TIMEOUT, but sysfs still shows it as 60, > > $ rbd-nbd map rbd-pool/image0 --try-netlink > > /dev/nbd0 > > $ cat /sys/block/nbd0/queue/io_timeout > > 60000 > > $ rbd-nbd unmap /dev/nbd0 > > $ cat /sys/block/nbd0/queue/io_timeout > > 60000 > > > > The problem exists with ioctl interface too. > > > > Signed-off-by: Prasanna Kumar Kalever > > --- > > drivers/block/nbd.c | 7 ++++++- > > 1 file changed, 6 insertions(+), 1 deletion(-) > > > > diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c > > index 16a1a14b1fd1..a45aabc4914b 100644 > > --- a/drivers/block/nbd.c > > +++ b/drivers/block/nbd.c > > @@ -158,6 +158,7 @@ static void nbd_connect_reply(struct genl_info *info, int index); > > static int nbd_genl_status(struct sk_buff *skb, struct genl_info *info); > > static void nbd_dead_link_work(struct work_struct *work); > > static void nbd_disconnect_and_put(struct nbd_device *nbd); > > +static void nbd_set_cmd_timeout(struct nbd_device *nbd, u64 timeout); > > > > static inline struct device *nbd_to_dev(struct nbd_device *nbd) > > { > > @@ -1250,7 +1251,7 @@ static void nbd_config_put(struct nbd_device *nbd) > > destroy_workqueue(nbd->recv_workq); > > nbd->recv_workq = NULL; > > > > - nbd->tag_set.timeout = 0; > > + nbd_set_cmd_timeout(nbd, 0); > > nbd->disk->queue->limits.discard_granularity = 0; > > nbd->disk->queue->limits.discard_alignment = 0; > > blk_queue_max_discard_sectors(nbd->disk->queue, UINT_MAX); > > @@ -2124,6 +2125,10 @@ static int nbd_genl_reconfigure(struct sk_buff *skb, struct genl_info *info) > > if (ret) > > goto out; > > > > + /* > > + * On reconfigure, if NBD_ATTR_TIMEOUT is not provided, we will > > + * continue to use the cmd timeout provided with connect initially. > > + */ > > if (info->attrs[NBD_ATTR_TIMEOUT]) > > nbd_set_cmd_timeout(nbd, > > nla_get_u64(info->attrs[NBD_ATTR_TIMEOUT])); > > -- > > 2.31.1 > > > > Looks fine: > > Reviewed-by: Ming Lei Thanks for the review Ming. Attempting to bring this to the top again for more reviews/acks. Thanks! -- Prasanna > > -- > Ming >