From: Omar Sandoval <osandov@osandov.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: Omar Sandoval <osandov@fb.com>, linux-block@vger.kernel.org
Subject: Re: [PATCH 0/9] blktests: Re-enable shellcheck warnings
Date: Mon, 25 Jun 2018 12:48:57 -0700 [thread overview]
Message-ID: <20180625194857.GC1218@vader> (raw)
In-Reply-To: <20180619202353.23631-1-bart.vanassche@wdc.com>
On Tue, Jun 19, 2018 at 01:23:44PM -0700, Bart Van Assche wrote:
> Hello Omar,
>
> Since I noticed that several useful shellcheck warnings are suppressed in the
> blktests project, I came up with this patch series that reenables all
> shellcheck warnings and also suppresses false positive shellcheck reports. It
> would be appreciated if you could have a look at this patch series.
>
> Thanks,
>
> Bart.
> Bart Van Assche (9):
> common/rc: Fix _have_tracepoint()
> Annotate include statements in shell scripts where the source file is
> a variable
> check, tests/meta/012: Use array["index"] instead of array[index]
Applied these.
> Suppress shellcheck complaints about global variables
> check: Avoid that shellcheck complains that $FULL appears unused
These are definitely useful warnings that would be good to reenable, but
I'm not a huge fan of this fix. Adding boilerplate for the sake of
appeasing the linter is... meh. I think what we can do is make the
tests/foo/group and common/rc sourcing explicit and put the workaround
stuff in common/rc. Still boilerplate but it at least appears to serve a
real purpose. I'll work on that.
> Multiple tests: remove unused and undefined variables
Applied this one.
> Avoid passing tests/block/002 arguments to _init_scsi_debug
This warning is stupid, I'd prefer to keep it disabled.
> check: Suppress a shellcheck warning about the DMESG_FILTER
> initialization
This warning is also pretty pointless, but the fix is so trivial that I
applied it anyways.
> Makefile: Do not suppress useful shellcheck warnings
Of course, I had to replace this patch since I kept some of the warnings
in.
Thanks for the cleanup!
> Makefile | 15 +-------------
> check | 53 ++++++++++++++++++++++++++---------------------
> common/cpuhotplug | 2 ++
> common/fio | 2 ++
> common/iopoll | 2 ++
> common/loop | 1 +
> common/nbd | 2 ++
> common/nvme | 2 ++
> common/rc | 2 ++
> common/scsi | 2 ++
> common/scsi_debug | 3 +++
> common/shellcheck | 4 ++++
> new | 1 +
> tests/block/001 | 1 +
> tests/block/002 | 3 ++-
> tests/block/003 | 2 ++
> tests/block/004 | 2 ++
> tests/block/005 | 2 ++
> tests/block/006 | 2 ++
> tests/block/007 | 1 +
> tests/block/009 | 1 +
> tests/block/010 | 2 ++
> tests/block/011 | 2 ++
> tests/block/012 | 2 ++
> tests/block/013 | 2 ++
> tests/block/014 | 2 ++
> tests/block/015 | 2 ++
> tests/block/016 | 2 ++
> tests/block/017 | 2 ++
> tests/block/018 | 2 ++
> tests/block/019 | 2 ++
> tests/block/020 | 2 ++
> tests/block/021 | 2 ++
> tests/loop/001 | 2 ++
> tests/loop/003 | 5 ++---
> tests/loop/005 | 2 ++
> tests/meta/001 | 2 ++
> tests/meta/002 | 2 ++
> tests/meta/003 | 2 ++
> tests/meta/004 | 2 ++
> tests/meta/005 | 2 ++
> tests/meta/006 | 2 ++
> tests/meta/007 | 2 ++
> tests/meta/008 | 2 ++
> tests/meta/009 | 2 ++
> tests/meta/010 | 2 ++
> tests/meta/011 | 2 ++
> tests/meta/012 | 6 ++++--
> tests/nbd/001 | 2 ++
> tests/nbd/002 | 2 ++
> tests/nvme/001 | 2 ++
> tests/nvme/002 | 2 ++
> tests/nvme/003 | 2 ++
> tests/nvme/004 | 2 ++
> tests/nvme/005 | 2 ++
> tests/nvme/006 | 2 ++
> tests/nvme/007 | 2 ++
> tests/nvme/008 | 2 ++
> tests/nvme/009 | 2 ++
> tests/nvme/010 | 5 +++--
> tests/nvme/011 | 5 +++--
> tests/nvme/012 | 3 ++-
> tests/nvme/013 | 3 ++-
> tests/scsi/001 | 2 ++
> tests/scsi/002 | 2 ++
> tests/scsi/003 | 2 ++
> tests/scsi/004 | 1 +
> 67 files changed, 161 insertions(+), 50 deletions(-)
> create mode 100644 common/shellcheck
>
> --
> 2.17.1
>
prev parent reply other threads:[~2018-06-25 19:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 20:23 [PATCH 0/9] blktests: Re-enable shellcheck warnings Bart Van Assche
2018-06-19 20:23 ` [PATCH 1/9] common/rc: Fix _have_tracepoint() Bart Van Assche
2018-06-25 9:07 ` Johannes Thumshirn
2018-06-19 20:23 ` [PATCH 2/9] Annotate include statements in shell scripts where the source file is a variable Bart Van Assche
2018-06-25 9:08 ` Johannes Thumshirn
2018-06-19 20:23 ` [PATCH 3/9] check, tests/meta/012: Use array["index"] instead of array[index] Bart Van Assche
2018-06-25 9:09 ` Johannes Thumshirn
2018-06-19 20:23 ` [PATCH 4/9] Suppress shellcheck complaints about global variables Bart Van Assche
2018-06-25 9:09 ` Johannes Thumshirn
2018-06-19 20:23 ` [PATCH 5/9] check: Avoid that shellcheck complains that $FULL appears unused Bart Van Assche
2018-06-25 9:10 ` Johannes Thumshirn
2018-06-19 20:23 ` [PATCH 6/9] Multiple tests: remove unused and undefined variables Bart Van Assche
2018-06-25 9:13 ` Johannes Thumshirn
2018-06-19 20:23 ` [PATCH 7/9] Avoid passing tests/block/002 arguments to _init_scsi_debug Bart Van Assche
2018-06-25 9:16 ` Johannes Thumshirn
2018-06-19 20:23 ` [PATCH 8/9] check: Suppress a shellcheck warning about the DMESG_FILTER initialization Bart Van Assche
2018-06-25 9:16 ` Johannes Thumshirn
2018-06-19 20:23 ` [PATCH 9/9] Makefile: Do not suppress useful shellcheck warnings Bart Van Assche
2018-06-25 9:16 ` Johannes Thumshirn
2018-06-25 19:48 ` Omar Sandoval [this message]
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=20180625194857.GC1218@vader \
--to=osandov@osandov.com \
--cc=bart.vanassche@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.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).