Netdev List
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: patchwork-bot+netdevbpf@kernel.org, davem@davemloft.net,
	 netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	dsahern@gmail.com,  "helpdesk@kernel.org" <helpdesk@kernel.org>
Subject: Re: [PATCH net-next v2 0/2] net: create device lookup API with reference tracking
Date: Thu, 15 Jun 2023 15:41:07 -0400	[thread overview]
Message-ID: <20230615-73rd-axle-trots-7e1c65@meerkat> (raw)
In-Reply-To: <20230615100021.43d2d041@kernel.org>

On Thu, Jun 15, 2023 at 10:00:21AM -0700, Jakub Kicinski wrote:
> Any recent changes to the pw-bot in commit matching?
> We don't do any editing when applying, AFAIK, and it's 3rd or 4th case
> within a week we get a no-match.

Did you, by chance, set your diff.algorithm to "histogram"? I noticed that the
diffs in your submission are very different from what I get when I run "git
show". E.g. notice this block in your email:

    --- a/net/core/dev.c
    +++ b/net/core/dev.c
    @@ -758,18 +758,7 @@  struct net_device *dev_get_by_name_rcu(struct net *net, const char *name)
     }
     EXPORT_SYMBOL(dev_get_by_name_rcu);
     
    -/**
    - *	dev_get_by_name		- find a device by its name
    - *	@net: the applicable net namespace
    - *	@name: name to find
    - *
    - *	Find an interface by name. This can be called from any
    - *	context and does its own locking. The returned handle has
    - *	the usage count incremented and the caller must use dev_put() to
    - *	release it when it is no longer needed. %NULL is returned if no
    - *	matching device is found.
    - */
    -
    +/* Deprecated for new users, call netdev_get_by_name() instead */
     struct net_device *dev_get_by_name(struct net *net, const char *name)
     {
        struct net_device *dev;

When I run "git show 70f7457ad6d655e65f1b93cbba2a519e4b11c946", I get a very
different looking diff:

    --- a/net/core/dev.c
    +++ b/net/core/dev.c
    @@ -758,29 +758,43 @@ struct net_device *dev_get_by_name_rcu(struct net *net, const char *name)
     }
     EXPORT_SYMBOL(dev_get_by_name_rcu);

    +/* Deprecated for new users, call netdev_get_by_name() instead */
    +struct net_device *dev_get_by_name(struct net *net, const char *name)
    +{
    + struct net_device *dev;
    +
    + rcu_read_lock();
    + dev = dev_get_by_name_rcu(net, name);
    + dev_hold(dev);
    + rcu_read_unlock();
    ...

Unless I pass --histogram, in which case it starts to match yours. So, I'm
wondering if you have diff.algorithm set to "histogram" and this generates
patches that we can no longer match against commits, because we are generating
the diffs using the default algorithm.

-K

  reply	other threads:[~2023-06-15 19:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 21:49 [PATCH net-next v2 0/2] net: create device lookup API with reference tracking Jakub Kicinski
2023-06-12 21:49 ` [PATCH net-next v2 1/2] " Jakub Kicinski
2023-06-13  9:14   ` Eric Dumazet
2023-06-14  2:19   ` David Ahern
2023-06-16  8:21   ` Eric Dumazet
2023-06-17  0:10     ` David Ahern
2023-06-12 21:49 ` [PATCH net-next v2 2/2] netpoll: allocate netdev tracker right away Jakub Kicinski
2023-06-15  7:50 ` [PATCH net-next v2 0/2] net: create device lookup API with reference tracking patchwork-bot+netdevbpf
2023-06-15 17:00   ` Jakub Kicinski
2023-06-15 19:41     ` Konstantin Ryabitsev [this message]
2023-06-15 20:17       ` Jakub Kicinski
2023-06-15 20:22         ` Konstantin Ryabitsev
2023-06-15 21:56           ` Jakub Kicinski

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=20230615-73rd-axle-trots-7e1c65@meerkat \
    --to=konstantin@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edumazet@google.com \
    --cc=helpdesk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=patchwork-bot+netdevbpf@kernel.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