From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Hou Tao <houtao@huaweicloud.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Networking <netdev@vger.kernel.org>
Subject: Re: linux-next: boot warning from the bpf-next tree
Date: Thu, 14 Sep 2023 08:19:12 +1000 [thread overview]
Message-ID: <20230914081912.33b30cc8@canb.auug.org.au> (raw)
In-Reply-To: <64f1f578-17e7-a8a8-12f2-6a1a0d98a4af@huaweicloud.com>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
Hi Hou,
On Wed, 13 Sep 2023 15:56:04 +0800 Hou Tao <houtao@huaweicloud.com> wrote:
>
> Yes. The warning is due to the checking added in commit c93047255202
> ("bpf: Ensure unit_size is matched with slab cache object size").
> Considering that bpf-next has not merged the patch-set yet, should I
> post a patch to bpf tree to fix it ? A fix patch is attached which can
> fix the warning in my local setup.
I will apply your patch as a merge resolution for the bpf-next tree
merge until something better is done. Please make sure to let me know
if it is not longer needed (in case it is not obvious).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-09-13 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 3:34 linux-next: boot warning from the bpf-next tree Stephen Rothwell
2023-09-13 4:59 ` Stephen Rothwell
2023-09-13 7:56 ` Hou Tao
2023-09-13 22:19 ` Stephen Rothwell [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=20230914081912.33b30cc8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=houtao@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yonghong.song@linux.dev \
/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