From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9E56BC433DF for ; Tue, 11 Aug 2020 23:44:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7B9B720782 for ; Tue, 11 Aug 2020 23:44:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="VQLdeuOn" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726255AbgHKXol (ORCPT ); Tue, 11 Aug 2020 19:44:41 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:21284 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726143AbgHKXok (ORCPT ); Tue, 11 Aug 2020 19:44:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1597189479; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=AAi7QgDlgwa6vXyUFB2roc4ydwBgYOiEWcbw2Mkt8HA=; b=VQLdeuOn/+J6FGREhN8JslaflPzwweGc0P2kXfKFN/dSYUUPT4V7SkA9ex7uTThkOOiNmt i0BWUKX+gMsBW9K+8Z3q6Yzyxf8T7Lvhxxa6B9B8VUoir2wyZm/t8lTuFrXw2IBGVks+1o 03sJ49u0qYW3L4Hf8VJmXASiPxRW7Xs= 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-364-QPWel0fLPqK9s7s2pQ0NCQ-1; Tue, 11 Aug 2020 19:44:35 -0400 X-MC-Unique: QPWel0fLPqK9s7s2pQ0NCQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A34E78017F4; Tue, 11 Aug 2020 23:44:34 +0000 (UTC) Received: from localhost (ovpn-13-156.pek2.redhat.com [10.72.13.156]) by smtp.corp.redhat.com (Postfix) with ESMTP id B98631A92C; Tue, 11 Aug 2020 23:44:25 +0000 (UTC) From: Ming Lei To: Jens Axboe Cc: linux-block@vger.kernel.org, Ming Lei , Christoph Hellwig , Changpeng Liu , Daniel Verkamp , "Michael S . Tsirkin" , Stefan Hajnoczi , Stefano Garzarella Subject: [PATCH V2 0/3] block: fix discard merge for single max discard segment Date: Wed, 12 Aug 2020 07:44:17 +0800 Message-Id: <20200811234420.2297137-1-ming.lei@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org Hello, The 1st patch checks max discard segment limit in request merge code, and one discard request failure is fixed for virtio_blk. The 2nd patch fixes handling of single max discard segment for virtio_blk, and potential memory corruption is fixed. The 3rd patch renames the confusing blk_discard_mergable(). The biggest problem is that virtio_blk handles discard request in multi-range style, however it(at least qemu) may claim that multi range discard isn't supported by returning 1 for max discard segment. V2: - add comment - warn on mismatched bios and discard segment number - rename blk_discard_mergable Ming Lei (3): block: respect queue limit of max discard segment block: virtio_blk: fix handling single range discard request block: rename blk_discard_mergable as blk_discard_support_multi_range block/blk-merge.c | 21 +++++++++++++++------ drivers/block/virtio_blk.c | 31 +++++++++++++++++++++++-------- 2 files changed, 38 insertions(+), 14 deletions(-) Cc: Christoph Hellwig Cc: Changpeng Liu Cc: Daniel Verkamp Cc: Michael S. Tsirkin Cc: Stefan Hajnoczi Cc: Stefano Garzarella -- 2.25.2