From: Wouter Verhelst <w@uter.be>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Mike Christie <mchristi@redhat.com>,
syzbot <syzbot+24c12fa8d218ed26011a@syzkaller.appspotmail.com>,
axboe@kernel.dk, josef@toxicpanda.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
nbd@other.debian.org, syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in nbd_ioctl
Date: Wed, 30 Oct 2019 10:41:46 +0200 [thread overview]
Message-ID: <20191030084146.GE25097@grep.be> (raw)
In-Reply-To: <20191030083957.GD25097@grep.be>
On Wed, Oct 30, 2019 at 10:39:57AM +0200, Wouter Verhelst wrote:
> On Thu, Oct 17, 2019 at 03:03:30PM +0100, Richard W.M. Jones wrote:
> > On Tue, Oct 01, 2019 at 04:19:25PM -0500, Mike Christie wrote:
> > > Hey Josef and nbd list,
> > >
> > > I had a question about if there are any socket family restrictions for nbd?
> >
> > In normal circumstances, in userspace, the NBD protocol would only be
> > used over AF_UNIX or AF_INET/AF_INET6.
>
> Note that someone once also did work to make it work over SCTP. I
> incorporated the patch into nbd-client and nbd-server, but never
> actually tested it myself. I have no way of knowing if it even still
> works anymore...
Actually, I meant SDP (as you pointed out downthread). Sorry for the
confusion ;-)
(I should probably kick that out though, indeed)
--
To the thief who stole my anti-depressants: I hope you're happy
-- seen somewhere on the Internet on a photo of a billboard
next prev parent reply other threads:[~2019-10-30 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 22:39 INFO: task hung in nbd_ioctl syzbot
2019-10-01 17:48 ` Mike Christie
2019-10-01 21:19 ` Mike Christie
2019-10-17 14:03 ` Richard W.M. Jones
2019-10-17 15:47 ` Mike Christie
2019-10-17 16:28 ` Richard W.M. Jones
2019-10-17 16:36 ` Eric Biggers
2019-10-17 16:49 ` Richard W.M. Jones
2019-10-17 21:26 ` Mike Christie
2019-10-30 8:39 ` Wouter Verhelst
2019-10-30 8:41 ` Wouter Verhelst [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-16 2:43 Hao Sun
2021-09-18 1:34 Hao Sun
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=20191030084146.GE25097@grep.be \
--to=w@uter.be \
--cc=axboe@kernel.dk \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=nbd@other.debian.org \
--cc=rjones@redhat.com \
--cc=syzbot+24c12fa8d218ed26011a@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 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.