Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3178835ybl; Mon, 20 Jan 2020 17:47:09 -0800 (PST) X-Google-Smtp-Source: APXvYqwt0llH5C3AARXhEcK5mjPLhVpaKnCYSsOpy4HL8Uwq3Q62dvCZupzhyBsYLZjoF1/2Zlf9 X-Received: by 2002:a9d:7d99:: with SMTP id j25mr1759437otn.226.1579571229753; Mon, 20 Jan 2020 17:47:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579571229; cv=none; d=google.com; s=arc-20160816; b=Vq1Phb8+bjnCaj7ptOo3eMZ4WLuBAH7l9BXimihp6YxzRn3mYyLiCp9QHgGU+ZmLvH Q9rWMoqwbgDHh+ICdNfY78kMYECdSwJSfMAhBEa1adgmuKvGokgcTsC1tsrHmfB+H2xm mYyQTHyrJnjv35Vq6Qiwt8lGLJtgLhK8FwVJV/WuSzfh8kqXmkNX1dMnxzoLfC5WNzLE QosBEgLG41UMsxh21D2ZnnYC3vJgnPAvehROlGKEKh0/6t6LYYkm0oYVV0q2U55uxk8Y 7UOolex8JIuiCbnUYtoZyvP/VanSjQOPB/rHoEWEg5o76UxLDDH+2l8gY/bC5CbAUNrj SvhA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=3HtHSYwo8Z1nUcvvjxI4JdHUsaAPPwLFd7EOqOPaoME=; b=LFcCcvo/24cDnbByLrI7UibQBteB+4Vb8ch+zMwbBiN5HMZM1QrsnMocgAToAt5uo/ Tdf1bl9F7HZdNa2dHx3BDzPe4ycXiSeW8DOYKx+uR98DcjsXm3QObCqB8Z7oOPhSMcP2 IS4kXfrSyyDuCnZYQlsFGufeeZDbUdXEMADo5f+ojShWETEbAYwawR1Tfq6XNbnGroPO 8WS1FaKAsTot4cstaVQMUF+akYsXZEgrJyr7hF5jogFTNlQr9n2TQRc14vCvq2ee4Xnr lRSJ29Cg96SvWNDTaCEDPAyGnLiJcaQlk3zTONnVpssAJt4nkMF8/+jU7u+LMYMhuQTr kDKw== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w2si19966364oib.252.2020.01.20.17.46.56; Mon, 20 Jan 2020 17:47:09 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728977AbgAUBpA (ORCPT + 99 others); Mon, 20 Jan 2020 20:45:00 -0500 Received: from szxga05-in.huawei.com ([45.249.212.191]:9222 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728512AbgAUBpA (ORCPT ); Mon, 20 Jan 2020 20:45:00 -0500 Received: from DGGEMS409-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id AD32333EE0431CDAE50B; Tue, 21 Jan 2020 09:44:57 +0800 (CST) Received: from [127.0.0.1] (10.173.220.183) by DGGEMS409-HUB.china.huawei.com (10.3.19.209) with Microsoft SMTP Server id 14.3.439.0; Tue, 21 Jan 2020 09:44:47 +0800 Subject: Re: [PATCH V3] brd: check and limit max_part par To: Ming Lei CC: Jens Axboe , , "linux-kernel@vger.kernel.org" , Mingfangsen , Guiyao , zhangsaisai , "wubo (T)" References: <20200115022725.GA14585@ming.t460p> <20200120225858.GB19571@ming.t460p> From: Zhiqiang Liu Message-ID: <1378f7d0-7166-a860-03cd-523cef8ea14b@huawei.com> Date: Tue, 21 Jan 2020 09:44:46 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <20200120225858.GB19571@ming.t460p> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 8bit X-Originating-IP: [10.173.220.183] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020/1/21 6:58, Ming Lei wrote: > On Mon, Jan 20, 2020 at 09:14:50PM +0800, Zhiqiang Liu wrote: >>>> +static inline void brd_check_and_reset_par(void) >>>> +{ >>>> +       if (unlikely(!rd_nr)) >>>> +               rd_nr = 1; >>>> + >>>> +       if (unlikely(!max_part)) >>>> +               max_part = 1; >>> >>> Another limit is that 'max_part' needs to be divided exactly by (1U << >>> MINORBITS), something like: >>> >>> max_part = 1UL << fls(max_part) >> >> Do we have to limit that 'max_part' needs to be divided exactly by (1U << >>> MINORBITS)? As your suggestion, the i * max_part is larger than MINORMASK, >> we can allocate from extended devt. > > Exact dividing is for reserving same minors for all disks with > RAMDISK_MAJOR, otherwise there is still chance to get same dev_t when > adding partitions. > > Extended devt is for covering more disks, not related with 'max_part'. > Thank you very much. I will change that as you said.