mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Jeffy Chen <jeffy.chen@rock-chips.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	xiyou.wangcong@gmail.com, briannorris@chromium.org,
	dianders@chromium.org, Jeffy Chen <jeffy.chen@rock-chips.com>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	Gustavo Padovan <gustavo@padovan.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v4] Bluetooth: btusb: Fix memory leak in play_deferred
Date: Wed, 19 Jul 2017 22:53:10 +0800	[thread overview]
Message-ID: <201707192230.oRZy26Qi%fengguang.wu@intel.com> (raw)
In-Reply-To: <1500371617-5460-1-git-send-email-jeffy.chen@rock-chips.com>

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

Hi Jeffy,

[auto build test WARNING on bluetooth-next/master]
[also build test WARNING on v4.13-rc1]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Jeffy-Chen/Bluetooth-btusb-Fix-memory-leak-in-play_deferred/20170719-044201
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
config: arm-exynos_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=arm 

Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings

All warnings (new ones prefixed by >>):

   In file included from drivers/bluetooth/btusb.c:32:0:
   drivers/bluetooth/btusb.c: In function 'btusb_resume':
>> include/net/bluetooth/bluetooth.h:136:26: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized]
    #define BT_ERR(fmt, ...) bt_err(fmt "\n", ##__VA_ARGS__)
                             ^~~~~~
   drivers/bluetooth/btusb.c:3266:6: note: 'err' was declared here
     int err;
         ^~~
--
   In file included from drivers//bluetooth/btusb.c:32:0:
   drivers//bluetooth/btusb.c: In function 'btusb_resume':
>> include/net/bluetooth/bluetooth.h:136:26: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized]
    #define BT_ERR(fmt, ...) bt_err(fmt "\n", ##__VA_ARGS__)
                             ^~~~~~
   drivers//bluetooth/btusb.c:3266:6: note: 'err' was declared here
     int err;
         ^~~

vim +/err +136 include/net/bluetooth/bluetooth.h

3ed7003e7 Joe Perches    2012-02-16  133  
3ed7003e7 Joe Perches    2012-02-16  134  #define BT_INFO(fmt, ...)	bt_info(fmt "\n", ##__VA_ARGS__)
594b31ea7 Frederic Danis 2015-09-23  135  #define BT_WARN(fmt, ...)	bt_warn(fmt "\n", ##__VA_ARGS__)
3ed7003e7 Joe Perches    2012-02-16 @136  #define BT_ERR(fmt, ...)	bt_err(fmt "\n", ##__VA_ARGS__)
3ed7003e7 Joe Perches    2012-02-16  137  #define BT_DBG(fmt, ...)	pr_debug(fmt "\n", ##__VA_ARGS__)
^1da177e4 Linus Torvalds 2005-04-16  138  

:::::: The code at line 136 was first introduced by commit
:::::: 3ed7003e724a04482e0ef1e794eece8c1c177b37 Bluetooth: Add logging functions bt_info and bt_err

:::::: TO: Joe Perches <joe@perches.com>
:::::: CC: Johan Hedberg <johan.hedberg@intel.com>

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27439 bytes --]

  parent reply	other threads:[~2017-07-19 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18  9:53 Jeffy Chen
2017-07-18  9:58 ` Marcel Holtmann
2017-07-19 14:53 ` kbuild test robot [this message]
2017-07-19 19:21 ` kbuild test robot

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=201707192230.oRZy26Qi%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=briannorris@chromium.org \
    --cc=dianders@chromium.org \
    --cc=gustavo@padovan.org \
    --cc=jeffy.chen@rock-chips.com \
    --cc=johan.hedberg@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=xiyou.wangcong@gmail.com \
    /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®