* Re: [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec
@ 2019-03-13 19:31 Andrey Kuzmin
0 siblings, 0 replies; 6+ messages in thread
From: Andrey Kuzmin @ 2019-03-13 19:31 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 1956 bytes --]
On Wed, Mar 13, 2019, 21:48 Stojaczyk, Dariusz <dariusz.stojaczyk(a)intel.com>
wrote:
> I've just cherry-picked the patch to v19.01.x
>
Thanks Dariusz.
Regards,
A.
>
> D.
>
> > -----Original Message-----
> > From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Walker,
> > Benjamin
> > Sent: Wednesday, March 13, 2019 7:35 PM
> > To: spdk(a)lists.01.org
> > Subject: Re: [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec
> >
> > 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/0fe8cd17111f5870aad56387a57e927d
> > 67a20bec.
> > >
> > > 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
> >
> > _______________________________________________
> > SPDK mailing list
> > SPDK(a)lists.01.org
> > https://lists.01.org/mailman/listinfo/spdk
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec
@ 2019-03-13 19:30 Andrey Kuzmin
0 siblings, 0 replies; 6+ messages in thread
From: Andrey Kuzmin @ 2019-03-13 19:30 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]
On Wed, Mar 13, 2019, 21:34 Walker, Benjamin <benjamin.walker(a)intel.com>
wrote:
> 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!
>
Ok, will do.
Thanks,
Andrey
>
> >
> > Thanks,
> > Andrey
> > _______________________________________________
> > SPDK mailing list
> > SPDK(a)lists.01.org
> > https://lists.01.org/mailman/listinfo/spdk
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec
@ 2019-03-13 18:48 Stojaczyk, Dariusz
0 siblings, 0 replies; 6+ messages in thread
From: Stojaczyk, Dariusz @ 2019-03-13 18:48 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
I've just cherry-picked the patch to v19.01.x
D.
> -----Original Message-----
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Walker,
> Benjamin
> Sent: Wednesday, March 13, 2019 7:35 PM
> To: spdk(a)lists.01.org
> Subject: Re: [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec
>
> 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/0fe8cd17111f5870aad56387a57e927d
> 67a20bec.
> >
> > 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
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec
@ 2019-03-13 18:34 Walker, Benjamin
0 siblings, 0 replies; 6+ messages in thread
From: Walker, Benjamin @ 2019-03-13 18:34 UTC (permalink / raw)
To: spdk
[-- 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec
@ 2019-03-13 18:13 Luse, Paul E
0 siblings, 0 replies; 6+ messages in thread
From: Luse, Paul E @ 2019-03-13 18:13 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Hi,
It's got enough votes already so it should be in the next release, 19.04 end of Apr.
Thx
Paul
-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Andrey Kuzmin
Sent: Wednesday, March 13, 2019 10:31 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec
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?
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.
Thanks,
Andrey
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
^ permalink raw reply [flat|nested] 6+ messages in thread
* [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec
@ 2019-03-13 17:31 Andrey Kuzmin
0 siblings, 0 replies; 6+ messages in thread
From: Andrey Kuzmin @ 2019-03-13 17:31 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
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?
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.
Thanks,
Andrey
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-03-13 19:31 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-13 19:31 [SPDK] Commit 0fe8cd17111f5870aad56387a57e927d67a20bec Andrey Kuzmin
-- strict thread matches above, loose matches on Subject: below --
2019-03-13 19:30 Andrey Kuzmin
2019-03-13 18:48 Stojaczyk, Dariusz
2019-03-13 18:34 Walker, Benjamin
2019-03-13 18:13 Luse, Paul E
2019-03-13 17:31 Andrey Kuzmin
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.