Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3589658imj; Tue, 12 Feb 2019 01:03:27 -0800 (PST) X-Google-Smtp-Source: AHgI3IbrcF1UxsLSYTJpoFTZsOm5n/YwfW4qopiNUHMOqigf0f8UGsyxyXZG8OFR8ZEdFqtkSI7B X-Received: by 2002:a63:d301:: with SMTP id b1mr2688352pgg.61.1549962206919; Tue, 12 Feb 2019 01:03:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549962206; cv=none; d=google.com; s=arc-20160816; b=gwjO+r7N20f6Ut2HXlCo8TQ9Y4IF1jWFumXjXxpbFBbcvfa8O9ip3H5jDMtPsYAxGz shoMmf8iZ8w8ty3DxoQbI29X6fMOl/FyVf3wG/v7hNK+D30Jw4tNFq4U+0Mb3xGQsMU8 DRpmenDcMOzvCNMuVFGsXdDKrTHMtCRaVcpzc+f5cW9qprmwxO+hl1jHPfW927qxITiU M+5vngcNyOZn732LV5QTZz968CKMe5XZd15XMvZHpHJtKQ9pMfw7Jqt1UG4wMlQeGgbs dUvDsoDKxzeCyAOqp7hHS1QULNoKoPVmMQ2bw+WePxd7VzlLRgQduhoFd/ALNXnOrcuY HH5Q== 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=WzFQ+3a7dvtqrg45hRTHTld0jYX/llWzkh8PpjVgQJ0=; b=QBjmpbDmxTOUySWpxQqK+M3pZjIkQ55ZKFXUQ7cGyck5nrUtt8U8+YAdqBfELu9pCk VKvot6Pro03FnMx3cXjIgBeIsRXku7DNg0dRl9wKJS36u9ENhLBqNCy4EvT8ZWinK9iy aSBnZPaqoZ/2QHGW5iOLuyJ6FfUlAozUF/Hw/KPqUlCXsIP54oCQQSS3mmHdfA9u0NL8 ethLimjahMhHBPW/jOp149Jar+8uGQMH7hkonMnuWXeoERSaxR/xsShUzpgLT3iVoVWA 2Loc1rfaPOUaQ5NG+opK5M4NLGVPe8aSmqGxn1MGIAOIU8iGcqAPArrRfl88uN5+6RZ9 Yu2g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=pHQmmPb+; 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 ba4si5092960plb.428.2019.02.12.01.03.11; Tue, 12 Feb 2019 01:03:26 -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=@kernel.org header.s=default header.b=pHQmmPb+; 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 S1728607AbfBLJBe (ORCPT + 99 others); Tue, 12 Feb 2019 04:01:34 -0500 Received: from mail.kernel.org ([198.145.29.99]:49116 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728086AbfBLJBe (ORCPT ); Tue, 12 Feb 2019 04:01:34 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 304BF2073D; Tue, 12 Feb 2019 09:01:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1549962093; bh=WzFQ+3a7dvtqrg45hRTHTld0jYX/llWzkh8PpjVgQJ0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pHQmmPb+5ckkPYqly8Jsy6DrrLVNyYtrMx4sZ2D1aKlZhVqRjrWSEvgNOlwn+jgPi w/JdCmVPEr/Rzle8Zfbql7FkCSSHyPooUU24ruafLqMBk7eYten3uBU+ry1EMbrCwL z9LiNhA/lmzZ9NjZxenCbXPoIY7denIicMaudNlo= Date: Tue, 12 Feb 2019 10:01:31 +0100 From: Greg KH To: Chengguang Xu Cc: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 1/2] chardev: fix an overlap misjudgement case in __register_chrdev_region() Message-ID: <20190212090131.GD31657@kroah.com> References: <20190212084739.27602-1-cgxu519@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190212084739.27602-1-cgxu519@gmx.com> User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 12, 2019 at 04:47:38PM +0800, Chengguang Xu wrote: > Current overlap check of minor range cannot correctly > handle a case which is baseminor < existing baseminor && > baseminor + minorct > existing baseminor + minorct. > Fix it and meanwhile do some code cleanups. Ick, don't do a fix and "code cleanups" in the same patch, that makes it almost impossible to see what the "fix" really was. That should be two separate patches, please break this up. thanks, greg k-h