From: Jamie Heilman <jamie@audible.transient.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Rong Chen <rong.a.chen@intel.com>,
kernel test robot <lkp@intel.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-all@lists.01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-all] Re: [PATCH] gcov: fail build on gcov_info size mismatch
Date: Mon, 15 Mar 2021 20:32:04 +0000 [thread overview]
Message-ID: <YE/ERLHBdjJ19TYT@audible.transient.net> (raw)
In-Reply-To: <CAHk-=wg0DY=cE-6Tjp_Dt32UC6XtMZBa0Rr2GqkK=Sh9HE=5kQ@mail.gmail.com>
Linus Torvalds wrote:
> On Sun, Mar 14, 2021 at 7:32 PM Rong Chen <rong.a.chen@intel.com> wrote:
> >
> > It can be reproduced with '-a' option in dash:
>
> Oh, ok. That kind of explains it.
>
> 'dash' is trash. Please somebody make a bug report.
>
> > $ a="!"
> > $ [ "$a" = ".size" ]
> > $ [ "$a" = ".size" -a "$b" = ".LPBX0," ]
> > sh: 2: [: =: unexpected operator
>
> This is 100% a dash bug. There is no question what-so-ever about it.
> This is not some kind of "POSIX is ambiguous", or "the handling of
> '-a' is complicated".
>
> It's simply just that dash is buggy.
>
> > While dash supports most uses of the -a and -o options, they have
> > very confusing semantics even in bash and are best avoided.
>
> No, they have perfectly sane semantics in bash, and in POSIX.
>
> See
>
> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html
>
> and there is absolutely zero question that bash does this correctly,
> and dash does not.
>
> But yes, it seems to be easy to work around, but still - could some
> Ubuntu person please open a bug report on dash?
fwiw, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850202
next prev parent reply other threads:[~2021-03-15 20:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 13:03 Peter Oberparleiter
2021-03-11 18:38 ` Linus Torvalds
2021-03-12 17:46 ` Peter Oberparleiter
2021-03-11 19:33 ` kernel test robot
2021-03-11 20:02 ` Linus Torvalds
2021-03-12 3:49 ` [kbuild-all] " Rong Chen
2021-03-12 17:52 ` Linus Torvalds
2021-03-15 2:31 ` Rong Chen
2021-03-15 19:12 ` Linus Torvalds
2021-03-15 20:32 ` Jamie Heilman [this message]
2021-03-15 20:57 ` Linus Torvalds
2021-03-15 23:09 ` Herbert Xu
2021-03-15 23:22 ` Linus Torvalds
2021-03-16 9:51 ` Herbert Xu
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=YE/ERLHBdjJ19TYT@audible.transient.net \
--to=jamie@audible.transient.net \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oberpar@linux.ibm.com \
--cc=rong.a.chen@intel.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®