mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: kbuild-all@01.org, Chris Mason <clm@fb.com>,
	Josef Bacik <jbacik@fb.com>, David Sterba <dsterba@suse.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: use kbasename in btrfsic_mount
Date: Fri, 27 Nov 2015 16:32:49 +0800	[thread overview]
Message-ID: <201511271640.QHZdu1xB%fengguang.wu@intel.com> (raw)
In-Reply-To: <1448611892-26144-1-git-send-email-linux@rasmusvillemoes.dk>

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]

Hi Rasmus,

[auto build test WARNING on: v4.4-rc2]
[also build test WARNING on: next-20151127]

url:    https://github.com/0day-ci/linux/commits/Rasmus-Villemoes/btrfs-use-kbasename-in-btrfsic_mount/20151127-161249
config: i386-randconfig-s1-201547 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   fs/btrfs/check-integrity.c: In function 'btrfsic_mount':
>> fs/btrfs/check-integrity.c:3140:5: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
      p = kbasename(ds->name);
        ^

vim +/const +3140 fs/btrfs/check-integrity.c

  3124			char *p;
  3125	
  3126			if (!device->bdev || !device->name)
  3127				continue;
  3128	
  3129			ds = btrfsic_dev_state_alloc();
  3130			if (NULL == ds) {
  3131				printk(KERN_INFO
  3132				       "btrfs check-integrity: kmalloc() failed!\n");
  3133				mutex_unlock(&btrfsic_mutex);
  3134				return -1;
  3135			}
  3136			ds->bdev = device->bdev;
  3137			ds->state = state;
  3138			bdevname(ds->bdev, ds->name);
  3139			ds->name[BDEVNAME_SIZE - 1] = '\0';
> 3140			p = kbasename(ds->name);
  3141			strlcpy(ds->name, p, sizeof(ds->name));
  3142			btrfsic_dev_state_hashtable_add(ds,
  3143							&btrfsic_dev_state_hashtable);
  3144		}
  3145	
  3146		ret = btrfsic_process_superblock(state, fs_devices);
  3147		if (0 != ret) {
  3148			mutex_unlock(&btrfsic_mutex);

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 22744 bytes --]

  parent reply	other threads:[~2015-11-27  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27  8:11 Rasmus Villemoes
2015-11-27  8:31 ` David Sterba
2015-11-27  8:32 ` kbuild test robot [this message]
2015-11-27  8:38   ` Rasmus Villemoes
2015-11-27  9:37 ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201511271640.QHZdu1xB%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jbacik@fb.com \
    --cc=kbuild-all@01.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®