netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Hillf Danton <hdanton@sina.com>,
	syzbot <syzbot+adf6c6c2be1c3a718121@syzkaller.appspotmail.com>,
	coreteam@netfilter.org, David Miller <davem@davemloft.net>,
	Florian Westphal <fw@strlen.de>,
	Jozsef Kadlecsik <kadlec@netfilter.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	NetFilter <netfilter-devel@vger.kernel.org>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: INFO: task hung in hashlimit_mt_check_common
Date: Sat, 1 Feb 2020 10:52:52 -0800	[thread overview]
Message-ID: <CAM_iQpWsfc5U3_csn=qZWZZs7SPptj9ZxGcriMd-aYy8NiN09Q@mail.gmail.com> (raw)
In-Reply-To: <20200201070541.GJ1778@kadam>

On Fri, Jan 31, 2020 at 11:07 PM Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> I wonder if there is some automated way to accept test patches from the
> mailing list.

At least for me, I always test patches before formally posting to mailing
lists. Sometimes I want syzbot to test some debugging or experimental
patches too, those should not be posted to dev mailing lists.

Thanks.

      reply	other threads:[~2020-02-01 18:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 16:00 INFO: task hung in hashlimit_mt_check_common syzbot
2020-01-19  8:17 ` syzbot
2020-01-26  7:26 ` syzbot
     [not found] ` <20200126132352.8212-1-hdanton@sina.com>
2020-02-01  7:05   ` Dan Carpenter
2020-02-01 18:52     ` Cong Wang [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='CAM_iQpWsfc5U3_csn=qZWZZs7SPptj9ZxGcriMd-aYy8NiN09Q@mail.gmail.com' \
    --to=xiyou.wangcong@gmail.com \
    --cc=coreteam@netfilter.org \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=hdanton@sina.com \
    --cc=kadlec@netfilter.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=syzbot+adf6c6c2be1c3a718121@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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).