From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec
Date: Wed, 13 Mar 2019 18:34:47 +0000 [thread overview]
Message-ID: <0264215e45fa5dcfa52a39089a44de2cfa43e467.camel@intel.com> (raw)
In-Reply-To: CANvN+emNV-w_-=NyDgDPHrh_NhZhg8CiNJdCnBG0gVZo0qy6ag@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
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/0fe8cd17111f5870aad56387a57e927d67a20bec.
>
> 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
next reply other threads:[~2019-03-13 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 18:34 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-13 19:31 [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec Andrey Kuzmin
2019-03-13 19:30 Andrey Kuzmin
2019-03-13 18:48 Stojaczyk, Dariusz
2019-03-13 18:13 Luse, Paul E
2019-03-13 17:31 Andrey Kuzmin
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=0264215e45fa5dcfa52a39089a44de2cfa43e467.camel@intel.com \
--to=spdk@lists.01.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