linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: "sunke (E)" <sunke32@huawei.com>
Cc: linux-block@vger.kernel.org, osandov@fb.com
Subject: Re: [PATCH blktests v4] nbd/003:add mount and clear_sock test for nbd
Date: Tue, 11 Feb 2020 14:23:45 -0800	[thread overview]
Message-ID: <20200211222345.GI100751@vader> (raw)
In-Reply-To: <8ece15f7-addf-44b2-0b54-4e1a450037f2@huawei.com>

On Mon, Dec 23, 2019 at 11:15:35AM +0800, sunke (E) wrote:
> Hi Omar,
> 
> The nbd/003 you simplified does the same I want to do and I made some small
> changes. I ran the simplified nbd/003 with linux kernel at the commit
> 7e0165b2f1a, it could pass.Then, I rollbacked the linux kernel to commit
> 090bb803708, it indeed triggered the BUGON.
> 
> However, there is one difference. NBD has ioctl and netlink interfaces. I
> use the netlink interface and the simplified nbd/003 use the ioctl
> interface. The nbd/003 with the netlink interface indeed seem to trigger
> some other issue. So, can it be nbd/004?

Sure, how about we add a flag to mount_clear_sock that specifies to use
the netlink interface instead of the ioctl interface, and make nbd/004
which is the same as nbd/003 expect it runs it with the netlink flag?

  reply	other threads:[~2020-02-11 22:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23  3:18 [PATCH blktests v4] nbd/003:add mount and clear_sock test for nbd Sun Ke
2019-12-23  3:15 ` sunke (E)
2020-02-11 22:23   ` Omar Sandoval [this message]
2020-02-12  8:13     ` sunke (E)
2020-02-19 16:43       ` Omar Sandoval
2020-02-05  2:02 ` sunke (E)
2020-02-11 22:21 ` Omar Sandoval

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=20200211222345.GI100751@vader \
    --to=osandov@osandov.com \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@fb.com \
    --cc=sunke32@huawei.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).