From: Adriana Kobylak <anoo@linux.ibm.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: axboe@kernel.dk, medadyoung@gmail.com, openbmc@lists.ozlabs.org,
nbd@other.debian.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] nbd:clear NBD_BOUND flag when NBD connection is closed
Date: Thu, 04 Apr 2019 10:31:01 -0500 [thread overview]
Message-ID: <de0564ed9e5316e5fe6c30c08a0ddec2@linux.vnet.ibm.com> (raw)
In-Reply-To: <20190403174908.jk6xuhzvn2gm2l2g@MacBook-Pro-91.local>
On 2019-04-03 12:49, Josef Bacik wrote:
> On Wed, Apr 03, 2019 at 12:13:53PM -0500, Adriana Kobylak wrote:
>> Adding Josef (updated email address in the maintainers file).
>>
>> On 2018-12-13 08:21, Adriana Kobylak wrote:
>> > On 2018-12-11 00:17, medadyoung@gmail.com wrote:
>> > > From: Medad <medadyoung@gmail.com>
>> > >
>> > > If we do NOT clear NBD_BOUND flag when NBD connection is closed,
>> > > then the original NBD device could not be used again.
>> > >
>> > > Signed-off-by: Medad <medadyoung@gmail.com>
>
> This doesn't sound right, this is just making sure we don't use the
> IOCTL
> configuration stuff with the netlink stuff. Once the disconnect
> happens the
> configuration should go away and it doesn't matter anymore. What are
> you doing
> to reproduce this problem? Thanks,
>
> Josef
I'm not seeing an issue now that we've moved to a new version of Yocto
containing
NBD 3.17. For reference we were reproducing by setting up a virtual
media device
on a BMC (https://github.com/openbmc/jsnbd).
We can close this patch request unless Medad still sees an issue in his
environment.
prev parent reply other threads:[~2019-04-04 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 6:17 [PATCH] nbd:clear NBD_BOUND flag when NBD connection is closed medadyoung
2018-12-13 14:21 ` Adriana Kobylak
2019-04-03 17:13 ` Adriana Kobylak
2019-04-03 17:49 ` Josef Bacik
2019-04-04 15:31 ` Adriana Kobylak [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=de0564ed9e5316e5fe6c30c08a0ddec2@linux.vnet.ibm.com \
--to=anoo@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=medadyoung@gmail.com \
--cc=nbd@other.debian.org \
--cc=openbmc@lists.ozlabs.org \
/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).