From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============8232012122010429710==" MIME-Version: 1.0 From: Walker, Benjamin Subject: Re: [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec Date: Wed, 13 Mar 2019 18:34:47 +0000 Message-ID: <0264215e45fa5dcfa52a39089a44de2cfa43e467.camel@intel.com> In-Reply-To: CANvN+emNV-w_-=NyDgDPHrh_NhZhg8CiNJdCnBG0gVZo0qy6ag@mail.gmail.com List-ID: To: spdk@lists.01.org --===============8232012122010429710== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Wed, 2019-03-13 at 20:31 +0300, Andrey Kuzmin wrote: > Recently I've spent some time debugging an issue that turned out to be > addressed by the recent commit > https://github.com/spdk/spdk/commit/0fe8cd17111f5870aad56387a57e927d67a20= bec. > = > Could someone give me a hint on what release this is going to be > merged into so that I can properly ifdef the temporary fix in my code? This is part of 19.04. It could be backported to the upcoming 19.01.1 if requested in the next day or two. > = > On a separate note, I've discovered a similar issue when using > bdevperf which seems to be due to the latter opening bdevs without > unregister callback, hitting a corner case of no-callback under > bdev_close. bdevperf unregister callback is fairly straightforward to > provide (the code is basically already there), let me know if there is > any interest in a patch for this. Yes please! > = > Thanks, > Andrey > _______________________________________________ > SPDK mailing list > SPDK(a)lists.01.org > https://lists.01.org/mailman/listinfo/spdk --===============8232012122010429710==--