linux-kernel - Re: [PATCH v2 19/24] dyndbg: accept query terms like module:foo and file=bar

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200617140123.GA2588750@kroah.com>
Date:   Wed, 17 Jun 2020 16:01:23 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     jim.cromie@...il.com
Cc:     Petr Mladek <pmladek@...e.com>, Jason Baron <jbaron@...mai.com>,
        LKML <linux-kernel@...r.kernel.org>, akpm@...uxfoundation.org,
        Rasmus Villemoes <linux@...musvillemoes.dk>
Subject: Re: [PATCH v2 19/24] dyndbg: accept query terms like module:foo and
 file=bar

On Wed, Jun 17, 2020 at 07:32:44AM -0600, jim.cromie@...il.com wrote:
> hi Petr
> 
> > You made to do some research and I was wrong. For example, getopt()
> > operates with options and their arguments. So, 'keyword' and 'arg' names
> > look good after all.
> >
> > Well, I still think that only one syntax should be supported. And it
> > is better to distinguish keywords and arguments, so I prefer keyword=arg.
> >
> 
> hehe, Im gonna cite some RFC wisdom to convince you  ;-)
> 
>      Be strict in what you emit, and permissive in what you accept.
> 
> I see no potential for real ambiguity that would override that bias.

No, the kernel should be strict in what it accepts, otherwise it is a
huge maintance burden for no good reason at all.

Only one syntax is a wise idea, stick with that please.

thanks,

greg k-h