From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966430AbcIHO4e (ORCPT ); Thu, 8 Sep 2016 10:56:34 -0400 Received: from mail-oi0-f43.google.com ([209.85.218.43]:36364 "EHLO mail-oi0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932500AbcIHO4d (ORCPT ); Thu, 8 Sep 2016 10:56:33 -0400 MIME-Version: 1.0 In-Reply-To: <20160908135431.1310985-1-arnd@arndb.de> References: <20160908135431.1310985-1-arnd@arndb.de> From: Dan Williams Date: Thu, 8 Sep 2016 07:56:31 -0700 Message-ID: Subject: Re: [PATCH] dax: use correct dev_t value To: Arnd Bergmann Cc: Johannes Thumshirn , "linux-kernel@vger.kernel.org" , kbuild test robot Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [ adding 0day robot ] On Thu, Sep 8, 2016 at 6:53 AM, Arnd Bergmann wrote: > The dev_t variable in devm_create_dax_dev() is used before it's > first set: > > drivers/dax/dax.c: In function 'devm_create_dax_dev': > drivers/dax/dax.c:205:39: error: 'dev_t' may be used uninitialized in this function [-Werror=maybe-uninitialized] > inode = iget5_locked(dax_superblock, hash_32(devt + DAXFS_MAGIC, 31), > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > drivers/dax/dax.c:688:8: note: 'dev_t' was declared here > > This reorders the code to how it looks correct to me. > > Signed-off-by: Arnd Bergmann > Fixes: 3bc52c45bac2 ("dax: define a unified inode/address_space for device-dax mappings") > --- > drivers/dax/dax.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/dax/dax.c b/drivers/dax/dax.c > index 68bb5e35b639..98dbbc12055f 100644 > --- a/drivers/dax/dax.c > +++ b/drivers/dax/dax.c > @@ -731,6 +731,8 @@ struct dax_dev *devm_create_dax_dev(struct dax_region *dax_region, > goto err_minor; > } > > + dev_t = MKDEV(MAJOR(dax_devt), minor); > + dev = &dax_dev->dev; > dax_dev->inode = dax_inode_get(&dax_dev->cdev, dev_t); > if (!dax_dev->inode) { > rc = -ENOMEM; > @@ -738,8 +740,6 @@ struct dax_dev *devm_create_dax_dev(struct dax_region *dax_region, > } > > /* device_initialize() so cdev can reference kobj parent */ > - dev_t = MKDEV(MAJOR(dax_devt), minor); > - dev = &dax_dev->dev; > device_initialize(dev); > > cdev = &dax_dev->cdev; Looks good to me. Strange, I don't see this error with gcc-5.3.1, I assume 0day missed it for a similar reason?