From: Wouter Verhelst <w@uter.be>
To: Eric Blake <eblake@redhat.com>
Cc: Pavel Skripkin <paskripkin@gmail.com>,
josef@toxicpanda.com, axboe@kernel.dk, hch@lst.de,
linux-block@vger.kernel.org, nbd@other.debian.org,
linux-kernel@vger.kernel.org,
syzbot+9937dc42271cd87d4b98@syzkaller.appspotmail.com
Subject: Re: [PATCH] block: nbd: add sanity check for first_minor
Date: Mon, 16 Aug 2021 17:55:14 +0200 [thread overview]
Message-ID: <YRqKYuopmdTXrCva@pc181009.grep.be> (raw)
In-Reply-To: <YRqDn2AVd3ApchWF@pc181009.grep.be>
On Mon, Aug 16, 2021 at 05:26:23PM +0200, Wouter Verhelst wrote:
> On Thu, Aug 12, 2021 at 10:35:25AM -0500, Eric Blake wrote:
> > On Thu, Aug 12, 2021 at 12:42:38PM +0300, Pavel Skripkin wrote:
> > >
> > > Fun thing: I got a reply to this email from
> > > nsd-public@police.gov.hk, which is Hong Kong Police office email. Does
> > > anyone know what is going on? :) It's a bit scary...
> >
> > You are not alone. Apparently, someone subscribed that address to the
> > nbd@other.debian.org list and it is auto-responding to every message
> > it receives; hopefully, a list administrator (I am not one) will be
> > willing to forcefully unsubscribe that address.
>
> FWIW, this has now happened, so you should no longer see such autoreplies.
... except I just received another one myself. I've taken it up with the
list admins again.
I won't update the whole Cc list of this anymore, but rest assured I'll
stay on this until it's been taken care of.
--
w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}
next prev parent reply other threads:[~2021-08-16 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 9:15 [PATCH] block: nbd: add sanity check for first_minor Pavel Skripkin
2021-08-12 9:16 ` Christoph Hellwig
2021-08-12 9:42 ` Pavel Skripkin
2021-08-12 15:35 ` Eric Blake
2021-08-16 15:26 ` Wouter Verhelst
2021-08-16 15:55 ` Wouter Verhelst [this message]
2021-08-16 16:56 ` Jens Axboe
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=YRqKYuopmdTXrCva@pc181009.grep.be \
--to=w@uter.be \
--cc=axboe@kernel.dk \
--cc=eblake@redhat.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=paskripkin@gmail.com \
--cc=syzbot+9937dc42271cd87d4b98@syzkaller.appspotmail.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