[PATCH] nbd:clear NBD_BOUND flag when NBD connection is closed
Adriana Kobylak
anoo at linux.ibm.com
Fri Apr 5 02:31:01 AEDT 2019
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 at gmail.com wrote:
>> > > From: Medad <medadyoung at 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 at 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.
More information about the openbmc
mailing list