linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Joe Perches <joe@perches.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	ksummit-discuss@lists.linuxfoundation.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation
Date: Thu, 26 Sep 2019 08:53:10 -0700	[thread overview]
Message-ID: <201909260848.B429B7DF@keescook> (raw)
In-Reply-To: <4eca5297a213357995c05b90c74a8bc638f54f02.camel@perches.com>

On Thu, Sep 26, 2019 at 08:14:03AM -0700, Joe Perches wrote:
> On Wed, 2019-09-25 at 11:40 -0700, Kees Cook wrote:
> > Is "6" a safe lower bound here? I thought 12 was the way to go?
> []
> > $ git log | egrep 'Fixes: [a-f0-9]{1,40}' | col2 | awk '{print length }' | sort | uniq -c | sort -n | tail
> >     238 8
> >     300 7
> >     330 14
> >     344 6
> >     352 11
> >     408 40
> >     425 10
> >     735 16
> >    1866 13
> >   31446 12
> > 
> > Hmpf, 6 is pretty high up there...
> 
> Yes, but your grep then col2 isn't right.
> You are counting all the 'Fixes: commit <foo>' output
> as 6 because that's the length of 'commit'.

the [a-f0-9]{1,40} already excludes "commit".

> I also think the length of the hex commit value doesn't
> matter much as it's got to be a specific single commit
> SHA1 anyway, otherwise the commit id lookup will fail.

Fail enough. We do already have 6-digit SHA1 collisions, so it seemed
like using more than 6 would be nicer? *shrug* I don't have a strong
opinion. :)

> 
> > > > @@ -1031,6 +1040,7 @@ MAINTAINER field selection options:
> > >      --roles => show roles (status:subsystem, git-signer, list, etc...)
> > >      --rolestats => show roles and statistics (commits/total_commits, %)
> > >      --file-emails => add email addresses found in -f file (default: 0 (off))
> > > +    --fixes => for patches, add signatures of commits with 'Fixes: <commit>' (default: 1 (on))
> > 
> > Should "Tested-by" and "Co-developed-by" get added to @signature_tags ?
> 
> All "<foo>-by:" signatures are added.

Ah, I'd missed where that happened. I do note that's only when
git-all-signature-types is set, which is default 0. (/me goes to add
this to his invocations...)

my $email_git_all_signature_types = 0;
...
    if ($email_git_all_signature_types) {
        $signature_pattern = "(.+?)[Bb][Yy]:";
    } else {
        $signature_pattern = "\(" . join("|", @signature_tags) . "\)";
    }

> > @commit_authors is unused?
> 
> Yes, authors are already required to sign-off so
> it's just duplicating already existing signatures.

Sure, it just seemed odd to populate it if it wasn't going to be used.

-- 
Kees Cook

  reply	other threads:[~2019-09-26 15:53 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <156821693963.2951081.11214256396118531359.stgit@dwillia2-desk3.amr.corp.intel.com>
2019-09-13 16:19 ` [PATCH] media: add a subsystem profile documentation Mauro Carvalho Chehab
2019-09-17  3:35   ` single maintainer profile directory (was Re: [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation) Kees Cook
2019-09-17 13:28     ` Mauro Carvalho Chehab
2019-09-17 16:33       ` Kees Cook
2019-09-18 11:23         ` [Ksummit-discuss] single maintainer profile directory (was " Mauro Carvalho Chehab
2019-09-18 17:39           ` Kees Cook
2019-09-18 18:35             ` Mauro Carvalho Chehab
2019-09-21 19:13           ` Jonathan Corbet
2019-09-21 19:45             ` Mauro Carvalho Chehab
2019-09-23 22:45             ` Kees Cook
2019-09-18 12:36   ` [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation Laurent Pinchart
2019-09-18 13:57     ` Mauro Carvalho Chehab
2019-09-18 17:27       ` Laurent Pinchart
2019-09-18 18:48         ` Mauro Carvalho Chehab
2019-09-19  7:08           ` Dan Carpenter
2019-09-20  5:29             ` Joe Perches
2019-09-20 14:09               ` Daniel Vetter
2019-09-19  6:56       ` Dan Carpenter
2019-09-19  7:22         ` Geert Uytterhoeven
2019-09-19  8:49           ` Jani Nikula
2019-09-19  8:58             ` Geert Uytterhoeven
2019-09-19  9:52               ` Jani Nikula
2019-09-20 14:53           ` Laurent Pinchart
2019-09-20 14:59             ` Doug Anderson
2019-09-21  8:56               ` Jani Nikula
2019-09-23 15:58                 ` Doug Anderson
2019-09-23 16:04                   ` Jonathan Corbet
2019-09-19  9:52         ` Mauro Carvalho Chehab
2019-09-25 17:13         ` Joe Perches
2019-09-25 18:40           ` Kees Cook
2019-09-26 15:14             ` Joe Perches
2019-09-26 15:53               ` Kees Cook [this message]
2019-09-26 16:02                 ` Joe Perches
2019-09-26 16:24                   ` Kees Cook
2019-09-26 10:25           ` Geert Uytterhoeven
2019-09-18 13:59     ` [PATCH v2] " Mauro Carvalho Chehab
2019-09-18 14:07       ` André Almeida
2019-09-18 14:11         ` Mauro Carvalho Chehab

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=201909260848.B429B7DF@keescook \
    --to=keescook@chromium.org \
    --cc=dan.carpenter@oracle.com \
    --cc=joe@perches.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+samsung@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;
as well as URLs for NNTP newsgroup(s).