FSTests Archive on lore.kernel.org
 help / color / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: "Paulo Alcantara (SUSE)" <pc@cjr.nz>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic/310: slightly improve check for dmesg error
Date: Tue, 17 Mar 2020 18:55:44 +0800
Message-ID: <20200317105544.GF14282@dhcp-12-102.nay.redhat.com> (raw)
In-Reply-To: <20200317015439.7406-1-pc@cjr.nz>

On Mon, Mar 16, 2020 at 10:54:39PM -0300, Paulo Alcantara (SUSE) wrote:
> The 'grep -c "error"' check was causing false positive results for
> cifs.ko when running it with 'echo 1 > /proc/fs/cifs/cifsFYI'.
> 
> That is, the test would fail when cifs.ko prints out a non-error
> message like this:
> 
>   [ 2320.903987] fs/cifs/smb2maperror.c: Mapping SMB2 status code
>   0x80000006 to POSIX err -61
> 
> Signed-off-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
> ---
>  tests/generic/310 | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/generic/310 b/tests/generic/310
> index 1fcd517e4e6f..504f7c44c177 100755
> --- a/tests/generic/310
> +++ b/tests/generic/310
> @@ -49,7 +49,7 @@ _require_command "$KILLALL_PROG" killall
>  dmesg -c > /dev/null
>  
>  nr_bug=`dmesg | grep -c "kernel BUG"`
> -nr_error=`dmesg | grep -c "error"`
> +nr_error=`dmesg | grep -c "EXT[234]-fs error"`

This's a generic test, which is not only for extN filesystem. If only for
"fs/cifs/smb2maperror.c: Mapping SMB2 status ...", how about:
   grep -wc "error"
or
   grep -c "\berror"

or something better:)

I think it still works for "EXT3-fs error (device loop1): ext3_readdir:
bad entry in ....".

Thanks,
Zorro

>  nr_null=`dmesg | grep -c "kernel NULL pointer dereference"`
>  nr_warning=`dmesg | grep -c "^WARNING"`
>  nr_lockdep=`dmesg | grep -c "possible recursive locking detected"`
> @@ -58,7 +58,7 @@ nr_lockdep=`dmesg | grep -c "possible recursive locking detected"`
>  check_kernel_bug()
>  {
>  	new_bug=`dmesg | grep -c "kernel BUG"`
> -	new_error=`dmesg | grep -c "error"`
> +	new_error=`dmesg | grep -c "EXT[234]-fs error"`
>  	new_null=`dmesg | grep -c "kernel NULL pointer dereference"`
>  	new_warning=`dmesg | grep -c "^WARNING"`
>  	new_lockdep=`dmesg | grep -c "possible recursive locking detected"`
> -- 
> 2.25.1
> 


  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17  1:54 Paulo Alcantara (SUSE)
2020-03-17 10:55 ` Zorro Lang [this message]
2020-03-17 15:23   ` Paulo Alcantara
2020-03-18  2:10     ` Eryu Guan

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=20200317105544.GF14282@dhcp-12-102.nay.redhat.com \
    --to=zlang@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=pc@cjr.nz \
    /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

FSTests Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/fstests/0 fstests/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 fstests fstests/ https://lore.kernel.org/fstests \
		fstests@vger.kernel.org
	public-inbox-index fstests

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.fstests


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git