netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <pabeni@redhat.com>
Cc: <apw@canonical.com>, <davem@davemloft.net>,
	<dwaipayanray1@gmail.com>, <edumazet@google.com>,
	<horms@kernel.org>, <joe@perches.com>, <kuba@kernel.org>,
	<kuni1840@gmail.com>, <kuniyu@amazon.com>,
	<lukas.bulwahn@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v1 net-next] checkpatch: Discourage a new use of rtnl_lock() variants.
Date: Thu, 13 Feb 2025 21:10:28 +0900	[thread overview]
Message-ID: <20250213121028.48711-1-kuniyu@amazon.com> (raw)
In-Reply-To: <410f016d-2ea6-45ae-895c-96fc34fdd1a3@redhat.com>

From: Paolo Abeni <pabeni@redhat.com>
Date: Thu, 13 Feb 2025 12:03:51 +0100
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index 7b28ad331742..09d5420436cc 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -6995,6 +6995,12 @@ sub process {
> >  #			}
> >  #		}
> >  
> > +# A new use of rtnl_lock() is discouraged as it's being converted to rtnl_net_lock(net).
> > +		if ($line =~ /^\+.*\brtnl_(try)?lock(_interruptible|_killable)?\(\)/) {
> 
> I think you need to add '\s*' just before  '\(' to avoid the test being
> fooled by some bad formatting.

Will add that.  BTW, it's also caught by another warning.

  WARNING: space prohibited between function name and open parenthesis '('
  #18: FILE: net/core/rtnetlink.c:79:
  +	rtnl_lock ();


> Also I'm unsure if the '^\+.*' header is strictly required - it should
> but some/most existing tests don't use it, do you know why?

I didn't notice but exactly, the following matches only + line.

  if ($line =~ /\brtnl_(try)?lock(_interruptible|_killable)?\s*\(\)/) {

Looks like the '-' diff is filtered, matching '-' doesn't make sense.

This function looks suspicious ? (maybe wrong, I'm not familiar with perl)

---8<---
sub raw_line {
        my ($linenr, $cnt) = @_;

        my $offset = $linenr - 1;
        $cnt++;

        my $line;
        while ($cnt) {
                $line = $rawlines[$offset++];
                next if (defined($line) && $line =~ /^-/);
                $cnt--;
        }

        return $line;
}
---8<---

Thanks!

  reply	other threads:[~2025-02-13 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11  7:04 [PATCH v1 net-next] checkpatch: Discourage a new use of rtnl_lock() variants Kuniyuki Iwashima
2025-02-12 18:23 ` Simon Horman
2025-02-13 11:03 ` Paolo Abeni
2025-02-13 12:10   ` Kuniyuki Iwashima [this message]
2025-02-13 12:18     ` Kuniyuki Iwashima

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=20250213121028.48711-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=apw@canonical.com \
    --cc=davem@davemloft.net \
    --cc=dwaipayanray1@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=joe@perches.com \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=lukas.bulwahn@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).