From: tianyu2 <tianyu2@kernelsoft.com>
To: "Paolo Abeni" <pabeni@redhat.com>
Cc: eric.dumazet@gmail.com, "Pablo Neira Ayuso" <pablo@netfilter.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4: remove useless arg
Date: Wed, 4 Dec 2024 11:16:02 +0800 (GMT+08:00) [thread overview]
Message-ID: <68a6773c.8deb.1938faae78c.Coremail.tianyu2@kernelsoft.com> (raw)
In-Reply-To: <85376cf2-0c95-4a08-bcbb-33c30c2f2c51@redhat.com>
> On 12/2/24 04:32, tianyu2 wrote:
> > The "struct sock *sk" parameter in ip_rcv_finish_core is unused, which
> > leads the compiler to optimize it out. As a result, the
> > "struct sk_buff *skb" parameter is passed using x1. And this make kprobe
> > hard to use.
> >
> > Signed-off-by: tianyu2 <tianyu2@kernelsoft.com>
>
> The patch code good, but the above does not look like a real name?!?
>
> If so, please re-submit, using your real full name and including the
> target tree (net-next in this case) in the subj prefix.
>
> See:
> https://elixir.bootlin.com/linux/v6.12.1/source/Documentation/process/submitting-patches.rst#L440
> https://elixir.bootlin.com/linux/v6.12.1/source/Documentation/process/maintainer-netdev.rst#L12
>
> @Pablo: after this change will be merged, I *think* that a possible
> follow-up could drop the 'sk' arg from NF_HOOK_LIST and ip_rcv_finish() too.
>
> Thanks!
>
> Paolo
Thank you for the reminder. I’ll adjust the patch format in the next version.
If ip_rcv_finish is modified, NF_HOOK/NF_HOOK_LIST also needs to be adjusted. I noticed that many places use NF_HOOK. These modifications should be fine, right?
However, I found that the ip_rcv_finish function doesn’t seem to be optimized by the compiler.
(ARM64)( gcc version 8.5.0 20210514 (Red Hat 8.5.0-4) (GCC) )
ffff800080faaf9c t ip_rcv_core.isra.26
ffff800080fab334 t ip_rcv_finish_core
ffff800080fab758 t ip_rcv_finish
ffff800080fab7b4 t ip_sublist_rcv
next prev parent reply other threads:[~2024-12-04 3:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 3:32 [PATCH] ipv4: remove useless arg tianyu2
2024-12-03 10:51 ` Paolo Abeni
2024-12-04 3:16 ` tianyu2 [this message]
2024-12-04 9:16 ` Paolo Abeni
2024-12-05 3:23 ` tianyu2
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=68a6773c.8deb.1938faae78c.Coremail.tianyu2@kernelsoft.com \
--to=tianyu2@kernelsoft.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).