mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: linux-kernel-owner@vger.kernel.org
Cc: kbuild-all@01.org, Zhouyang Jia <jiazhouyang09@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Thomas Gleixner <tglx@linutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: add error handling for kmem_cache_create
Date: Tue, 12 Jun 2018 13:21:13 +0800	[thread overview]
Message-ID: <201806121333.mrzA7LiM%fengguang.wu@intel.com> (raw)
In-Reply-To: <1528777434-40324-1-git-send-email-jiazhouyang09@gmail.com>

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

Hi,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on linus/master]
[also build test WARNING on v4.17 next-20180608]
[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/linux-kernel-owner-vger-kernel-org/proc-add-error-handling-for-kmem_cache_create/20180612-122737
config: i386-randconfig-x012-201823 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   fs/proc/inode.c: In function 'proc_init_kmemcache':
>> fs/proc/inode.c:108:10: warning: 'return' with a value, in function returning void
      return -ENOMEM;
             ^
   fs/proc/inode.c:96:13: note: declared here
    void __init proc_init_kmemcache(void)
                ^~~~~~~~~~~~~~~~~~~

vim +/return +108 fs/proc/inode.c

    95	
    96	void __init proc_init_kmemcache(void)
    97	{
    98		proc_inode_cachep = kmem_cache_create("proc_inode_cache",
    99						     sizeof(struct proc_inode),
   100						     0, (SLAB_RECLAIM_ACCOUNT|
   101							SLAB_MEM_SPREAD|SLAB_ACCOUNT|
   102							SLAB_PANIC),
   103						     init_once);
   104		pde_opener_cache =
   105			kmem_cache_create("pde_opener", sizeof(struct pde_opener), 0,
   106					  SLAB_ACCOUNT|SLAB_PANIC, NULL);
   107		if (!proc_inode_cachep || !pde_opener_cache)
 > 108			return -ENOMEM;
   109	
   110		proc_dir_entry_cache = kmem_cache_create_usercopy(
   111			"proc_dir_entry", sizeof(struct proc_dir_entry), 0, SLAB_PANIC,
   112			offsetof(struct proc_dir_entry, inline_name),
   113			sizeof_field(struct proc_dir_entry, inline_name), NULL);
   114	}
   115	

---
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: 33159 bytes --]

      parent reply	other threads:[~2018-06-12  5:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  4:23 Zhouyang Jia
2018-06-12  5:09 ` Alexey Dobriyan
2018-06-12  5:21 ` kbuild test robot [this message]

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=201806121333.mrzA7LiM%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiazhouyang09@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel-owner@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    /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®