From: kernel test robot <lkp@intel.com>
To: Dave Marchevsky <davemarchevsky@fb.com>, bpf@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@kernel.org>,
Kernel Team <kernel-team@fb.com>,
Dave Marchevsky <davemarchevsky@fb.com>,
Nathan Slingerland <slinger@meta.com>
Subject: Re: [PATCH v4 bpf-next 2/3] bpf: Introduce task_vma open-coded iterator kfuncs
Date: Wed, 4 Oct 2023 00:28:45 +0800 [thread overview]
Message-ID: <202310040045.CufS8H4U-lkp@intel.com> (raw)
In-Reply-To: <20231002195341.2940874-3-davemarchevsky@fb.com>
Hi Dave,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Dave-Marchevsky/bpf-Don-t-explicitly-emit-BTF-for-struct-btf_iter_num/20231003-035600
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20231002195341.2940874-3-davemarchevsky%40fb.com
patch subject: [PATCH v4 bpf-next 2/3] bpf: Introduce task_vma open-coded iterator kfuncs
config: i386-buildonly-randconfig-001-20231003 (https://download.01.org/0day-ci/archive/20231004/202310040045.CufS8H4U-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231004/202310040045.CufS8H4U-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310040045.CufS8H4U-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/bpf/task_iter.c:827:17: warning: no previous declaration for 'bpf_iter_task_vma_new' [-Wmissing-declarations]
__bpf_kfunc int bpf_iter_task_vma_new(struct bpf_iter_task_vma *it,
^~~~~~~~~~~~~~~~~~~~~
>> kernel/bpf/task_iter.c:871:36: warning: no previous declaration for 'bpf_iter_task_vma_next' [-Wmissing-declarations]
__bpf_kfunc struct vm_area_struct *bpf_iter_task_vma_next(struct bpf_iter_task_vma *it)
^~~~~~~~~~~~~~~~~~~~~~
>> kernel/bpf/task_iter.c:880:18: warning: no previous declaration for 'bpf_iter_task_vma_destroy' [-Wmissing-declarations]
__bpf_kfunc void bpf_iter_task_vma_destroy(struct bpf_iter_task_vma *it)
^~~~~~~~~~~~~~~~~~~~~~~~~
vim +/bpf_iter_task_vma_new +827 kernel/bpf/task_iter.c
826
> 827 __bpf_kfunc int bpf_iter_task_vma_new(struct bpf_iter_task_vma *it,
828 struct task_struct *task, u64 addr)
829 {
830 struct bpf_iter_task_vma_kern *kit = (void *)it;
831 bool irq_work_busy = false;
832 int err;
833
834 BUILD_BUG_ON(sizeof(struct bpf_iter_task_vma_kern) != sizeof(struct bpf_iter_task_vma));
835 BUILD_BUG_ON(__alignof__(struct bpf_iter_task_vma_kern) != __alignof__(struct bpf_iter_task_vma));
836
837 /* is_iter_reg_valid_uninit guarantees that kit hasn't been initialized
838 * before, so non-NULL kit->data doesn't point to previously
839 * bpf_mem_alloc'd bpf_iter_task_vma_kern_data
840 */
841 kit->data = bpf_mem_alloc(&bpf_global_ma, sizeof(struct bpf_iter_task_vma_kern_data));
842 if (!kit->data)
843 return -ENOMEM;
844
845 kit->data->task = get_task_struct(task);
846 kit->data->mm = task->mm;
847 if (!kit->data->mm) {
848 err = -ENOENT;
849 goto err_cleanup_iter;
850 }
851
852 /* kit->data->work == NULL is valid after bpf_mmap_unlock_get_irq_work */
853 irq_work_busy = bpf_mmap_unlock_get_irq_work(&kit->data->work);
854 if (irq_work_busy || !mmap_read_trylock(kit->data->mm)) {
855 err = -EBUSY;
856 goto err_cleanup_iter;
857 }
858
859 vma_iter_init(&kit->data->vmi, kit->data->mm, addr);
860 return 0;
861
862 err_cleanup_iter:
863 if (kit->data->task)
864 put_task_struct(kit->data->task);
865 bpf_mem_free(&bpf_global_ma, kit->data);
866 /* NULL kit->data signals failed bpf_iter_task_vma initialization */
867 kit->data = NULL;
868 return err;
869 }
870
> 871 __bpf_kfunc struct vm_area_struct *bpf_iter_task_vma_next(struct bpf_iter_task_vma *it)
872 {
873 struct bpf_iter_task_vma_kern *kit = (void *)it;
874
875 if (!kit->data) /* bpf_iter_task_vma_new failed */
876 return NULL;
877 return vma_next(&kit->data->vmi);
878 }
879
> 880 __bpf_kfunc void bpf_iter_task_vma_destroy(struct bpf_iter_task_vma *it)
881 {
882 struct bpf_iter_task_vma_kern *kit = (void *)it;
883
884 if (kit->data) {
885 bpf_mmap_unlock_mm(kit->data->work, kit->data->mm);
886 put_task_struct(kit->data->task);
887 bpf_mem_free(&bpf_global_ma, kit->data);
888 }
889 }
890
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-03 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 19:53 [PATCH v4 bpf-next 0/3] Open-coded task_vma iter Dave Marchevsky
2023-10-02 19:53 ` [PATCH v4 bpf-next 1/3] bpf: Don't explicitly emit BTF for struct btf_iter_num Dave Marchevsky
2023-10-02 19:53 ` [PATCH v4 bpf-next 2/3] bpf: Introduce task_vma open-coded iterator kfuncs Dave Marchevsky
2023-10-02 21:29 ` kernel test robot
2023-10-03 16:28 ` kernel test robot [this message]
2023-10-03 22:39 ` Andrii Nakryiko
2023-10-02 19:53 ` [PATCH v4 bpf-next 3/3] selftests/bpf: Add tests for open-coded task_vma iter Dave Marchevsky
2023-10-03 22:46 ` Andrii Nakryiko
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=202310040045.CufS8H4U-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=slinger@meta.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