Re: [PATCH] nbd:clear NBD_BOUND flag when NBD connection is closed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx wrote:
> > From: Medad <medadyoung@xxxxxxxxx>
> >
> >     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@xxxxxxxxx>

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.




[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux