All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Andy Whitcroft <apw@canonical.com>,
	"John 'Warthog9' Hawley" <warthog9@eaglescrag.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Allow space leading blank lines in email headers
Date: Wed, 22 Mar 2017 23:20:57 -0700	[thread overview]
Message-ID: <20170323062057.GE17578@localhost.localdomain> (raw)
In-Reply-To: <d75a9f0b78b3488078429f4037d9fff3bdfa3b78.1490247180.git.joe@perches.com>

On Wed, Mar 22, 2017 at 10:35:21PM -0700, Joe Perches wrote:
> Allow a leading space and otherwise blank link in the email headers
> as it can be a line wrapped Spamassassin multiple line string or any
> other valid rfc 2822/5322 email header.
> 
> The line with space causes checkpatch to erroniously think that it's
> in the content body, as opposed to headers and thus flag a mail header
> as an unwrapped long comment line.
> 
> Reported-by: Darren Hart (VMware) <dvhart@infradead.org>
> Original-patch-by: John 'Warthog9' Hawley (VMware) <warthog9@eaglescrag.net>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>  scripts/checkpatch.pl | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 832e8150dba3..089c974aa3a5 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2628,8 +2628,8 @@ sub process {
>  # Check if it's the start of a commit log
>  # (not a header line and we haven't seen the patch filename)
>  		if ($in_header_lines && $realfile =~ /^$/ &&
> -		    !($rawline =~ /^\s+\S/ ||
> -		      $rawline =~ /^(commit\b|from\b|[\w-]+:).*$/i)) {
> +		    !($rawline =~ /^\s+(?:\S|$)/ ||

First, thanks Joe. The above change alone is sufficient to resolve the specific
issue I observed with the long header fields (RFC 5322 2.2.3) used by spam
assassin.

Tested-by: Darren Hart (VMware) <dvhart@infradead.org>

I do have an open question regarding how we're going about testing for the end
of the header lines. Since we're not just testing for an empty line to separate
headers and body, there is clearly more going on here - but I'm not sure what it
is ... so I can't be sure this doesn't have an unintended consequence.

> +		      $rawline =~ /^(?:commit\b|from\b|[\w-]+:)/i)) {

This appears to be an unrelated change, introducing the non-capturing-group
(?:) and dropping the superfluous .*$ postfix. Did I get that right?

-- 
Darren Hart
VMware Open Source Technology Center

  reply	other threads:[~2017-03-23  7:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  5:35 [PATCH] checkpatch: Allow space leading blank lines in email headers Joe Perches
2017-03-23  6:20 ` Darren Hart [this message]
2017-03-23  6:28   ` Joe Perches
2017-03-23 15:55     ` Darren Hart

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=20170323062057.GE17578@localhost.localdomain \
    --to=dvhart@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=warthog9@eaglescrag.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.