All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@cjr.nz>
To: ronnie sahlberg <ronniesahlberg@gmail.com>,
	Steve French <smfrench@gmail.com>
Cc: Enzo Matsumiya <ematsumiya@suse.de>,
	CIFS <linux-cifs@vger.kernel.org>,
	Shyam Prasad N <nspmangalore@gmail.com>
Subject: Re: [PATCH] cifs: do not include page data when checking signature
Date: Wed, 18 Jan 2023 19:59:12 -0300	[thread overview]
Message-ID: <87mt6fwitb.fsf@cjr.nz> (raw)
In-Reply-To: <CAN05THREk=3Zk2VTpfm6qyAA88mV2xm0qtiL0-p44ZRhXPuzmw@mail.gmail.com>

ronnie sahlberg <ronniesahlberg@gmail.com> writes:

> We should update the buildbot so we clear dmesg before every test and
> then check for and fail any test that results in something unexpected.

Yes, agreed.

Our internal buildbot does this after running a single test

        bad_dmesg_rx = re.compile(r'Call trace:|blocked for more than.*seconds|BUG: sleeping function called from invalid context|^WARNING|possible recursive locking detected')
        if bad_dmesg_rx.search(dmesg):
            ...

We should probably have 'CIFS VFS:' in that regex as well.

      reply	other threads:[~2023-01-18 22:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 17:06 [PATCH] cifs: do not include page data when checking signature Enzo Matsumiya
2023-01-18 20:06 ` Paulo Alcantara
2023-01-18 20:50   ` Steve French
2023-01-18 22:07   ` Steve French
2023-01-18 22:17     ` Paulo Alcantara
     [not found]       ` <CAH2r5mt2UvW32AZrvjde75NL3V5qWLbc=WTTdaLZsi2B4oYEhA@mail.gmail.com>
2023-01-18 22:31         ` ronnie sahlberg
2023-01-18 22:59           ` Paulo Alcantara [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=87mt6fwitb.fsf@cjr.nz \
    --to=pc@cjr.nz \
    --cc=ematsumiya@suse.de \
    --cc=linux-cifs@vger.kernel.org \
    --cc=nspmangalore@gmail.com \
    --cc=ronniesahlberg@gmail.com \
    --cc=smfrench@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.