All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 3/8] mmap locking API: use coccinelle to convert mmap_sem rwsem call sites
Date: Fri, 27 Mar 2020 08:01:54 +0800	[thread overview]
Message-ID: <202003270704.CAMJB6m3%lkp@intel.com> (raw)
In-Reply-To: <20200326070236.235835-4-walken@google.com>

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

Hi Michel,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on rdma/for-next]
[also build test ERROR on linus/master v5.6-rc7]
[cannot apply to powerpc/next next-20200326]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Michel-Lespinasse/Add-a-new-mmap-locking-API-wrapping-mmap_sem-calls/20200327-035215
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
config: i386-randconfig-a002-20200326 (attached as .config)
compiler: gcc-4.9 (Ubuntu 4.9.3-13ubuntu2) 4.9.3
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/dma-buf/dma-resv.c: In function 'dma_resv_lockdep':
>> drivers/dma-buf/dma-resv.c:112:2: error: implicit declaration of function 'mmap_read_lock' [-Werror=implicit-function-declaration]
     mmap_read_lock(mm);
     ^
>> drivers/dma-buf/dma-resv.c:121:2: error: implicit declaration of function 'mmap_read_unlock' [-Werror=implicit-function-declaration]
     mmap_read_unlock(mm);
     ^
   cc1: some warnings being treated as errors

vim +/mmap_read_lock +112 drivers/dma-buf/dma-resv.c

    98	
    99	#if IS_ENABLED(CONFIG_LOCKDEP)
   100	static int __init dma_resv_lockdep(void)
   101	{
   102		struct mm_struct *mm = mm_alloc();
   103		struct ww_acquire_ctx ctx;
   104		struct dma_resv obj;
   105		int ret;
   106	
   107		if (!mm)
   108			return -ENOMEM;
   109	
   110		dma_resv_init(&obj);
   111	
 > 112		mmap_read_lock(mm);
   113		ww_acquire_init(&ctx, &reservation_ww_class);
   114		ret = dma_resv_lock(&obj, &ctx);
   115		if (ret == -EDEADLK)
   116			dma_resv_lock_slow(&obj, &ctx);
   117		fs_reclaim_acquire(GFP_KERNEL);
   118		fs_reclaim_release(GFP_KERNEL);
   119		ww_mutex_unlock(&obj.lock);
   120		ww_acquire_fini(&ctx);
 > 121		mmap_read_unlock(mm);
   122		
   123		mmput(mm);
   124	
   125		return 0;
   126	}
   127	subsys_initcall(dma_resv_lockdep);
   128	#endif
   129	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

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

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Michel Lespinasse <walken@google.com>
Cc: kbuild-all@lists.01.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 3/8] mmap locking API: use coccinelle to convert mmap_sem rwsem call sites
Date: Fri, 27 Mar 2020 08:01:54 +0800	[thread overview]
Message-ID: <202003270704.CAMJB6m3%lkp@intel.com> (raw)
In-Reply-To: <20200326070236.235835-4-walken@google.com>

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

Hi Michel,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on rdma/for-next]
[also build test ERROR on linus/master v5.6-rc7]
[cannot apply to powerpc/next next-20200326]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Michel-Lespinasse/Add-a-new-mmap-locking-API-wrapping-mmap_sem-calls/20200327-035215
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
config: i386-randconfig-a002-20200326 (attached as .config)
compiler: gcc-4.9 (Ubuntu 4.9.3-13ubuntu2) 4.9.3
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/dma-buf/dma-resv.c: In function 'dma_resv_lockdep':
>> drivers/dma-buf/dma-resv.c:112:2: error: implicit declaration of function 'mmap_read_lock' [-Werror=implicit-function-declaration]
     mmap_read_lock(mm);
     ^
>> drivers/dma-buf/dma-resv.c:121:2: error: implicit declaration of function 'mmap_read_unlock' [-Werror=implicit-function-declaration]
     mmap_read_unlock(mm);
     ^
   cc1: some warnings being treated as errors

vim +/mmap_read_lock +112 drivers/dma-buf/dma-resv.c

    98	
    99	#if IS_ENABLED(CONFIG_LOCKDEP)
   100	static int __init dma_resv_lockdep(void)
   101	{
   102		struct mm_struct *mm = mm_alloc();
   103		struct ww_acquire_ctx ctx;
   104		struct dma_resv obj;
   105		int ret;
   106	
   107		if (!mm)
   108			return -ENOMEM;
   109	
   110		dma_resv_init(&obj);
   111	
 > 112		mmap_read_lock(mm);
   113		ww_acquire_init(&ctx, &reservation_ww_class);
   114		ret = dma_resv_lock(&obj, &ctx);
   115		if (ret == -EDEADLK)
   116			dma_resv_lock_slow(&obj, &ctx);
   117		fs_reclaim_acquire(GFP_KERNEL);
   118		fs_reclaim_release(GFP_KERNEL);
   119		ww_mutex_unlock(&obj.lock);
   120		ww_acquire_fini(&ctx);
 > 121		mmap_read_unlock(mm);
   122		
   123		mmput(mm);
   124	
   125		return 0;
   126	}
   127	subsys_initcall(dma_resv_lockdep);
   128	#endif
   129	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

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

  reply	other threads:[~2020-03-27  0:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  7:02 [PATCH 0/8] Add a new mmap locking API wrapping mmap_sem calls Michel Lespinasse
2020-03-26  7:02 ` [PATCH 1/8] mmap locking API: initial implementation as rwsem wrappers Michel Lespinasse
2020-03-26 17:56   ` Jason Gunthorpe
2020-03-26 18:06     ` Matthew Wilcox
2020-03-26 18:09       ` Matthew Wilcox
2020-03-26 22:09         ` Michel Lespinasse
2020-03-26  7:02 ` [PATCH 2/8] MMU notifier: use the new mmap locking API Michel Lespinasse
2020-03-26  7:02 ` [PATCH 3/8] mmap locking API: use coccinelle to convert mmap_sem rwsem call sites Michel Lespinasse
2020-03-27  0:01   ` kbuild test robot [this message]
2020-03-27  0:01     ` kbuild test robot
2020-03-27  0:40   ` kbuild test robot
2020-03-27  0:40     ` kbuild test robot
2020-03-26  7:02 ` [PATCH 4/8] mmap locking API: convert mmap_sem call sites missed by coccinelle Michel Lespinasse
2020-03-26 23:13   ` kbuild test robot
2020-03-26 23:13     ` kbuild test robot
2020-03-26 23:27   ` kbuild test robot
2020-03-26 23:27     ` kbuild test robot
2020-03-26  7:02 ` [PATCH 5/8] mmap locking API: convert nested write lock sites Michel Lespinasse
2020-03-26 12:09   ` Matthew Wilcox
2020-03-26 12:56     ` Michel Lespinasse
2020-03-26  7:02 ` [PATCH 6/8] mmap locking API: add mmap_read_release() and mmap_read_unlock_non_owner() Michel Lespinasse
2020-03-26  7:02 ` [PATCH 7/8] mmap locking API: add MMAP_LOCK_INITIALIZER Michel Lespinasse
2020-04-06  9:46   ` Laurent Dufour
2020-04-06 13:04     ` Michel Lespinasse
2020-03-26  7:02 ` [PATCH 8/8] mmap locking API: rename mmap_sem to mmap_lock Michel Lespinasse
2020-04-06 12:45   ` Laurent Dufour
2020-04-06 13:17     ` Michel Lespinasse
2020-04-06 16:03     ` Davidlohr Bueso
2020-03-26  7:13 ` [PATCH 0/8] Add a new mmap locking API wrapping mmap_sem calls Michel Lespinasse
  -- strict thread matches above, loose matches on Subject: below --
2020-03-26 13:30 [PATCH 3/8] mmap locking API: use coccinelle to convert mmap_sem rwsem call sites Markus Elfring
2020-03-26 13:30 ` Markus Elfring
2020-03-26 22:17 ` Michel Lespinasse
2020-03-26 22:17   ` Michel Lespinasse

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=202003270704.CAMJB6m3%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.