stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* regression: blktests nvme/004 failed on linux-stable 5.7.y
       [not found] <1528690896.32343478.1593229315244.JavaMail.zimbra@redhat.com>
@ 2020-06-29 10:02 ` Yi Zhang
  2020-06-29 10:59   ` Greg KH
  0 siblings, 1 reply; 3+ messages in thread
From: Yi Zhang @ 2020-06-29 10:02 UTC (permalink / raw)
  To: linux-nvme; +Cc: chaitanya.kulkarni, stable, gregkh

Hello

commit[1] introduced regression that will lead blktest nvme/004 failed on v5.7.5, and commits [2] fixed this issue on latest linux tree.
But commit[2] cannot be directly applied to stable tree due to dependceny[3], could you help backport the fix and dependency to stable tree, thanks.


[1]
64f5e9cdd711 nvmet: fix memory leak when removing namespaces and controllers concurrently

[2]
819f7b88b48f nvmet: fail outstanding host posted AEN req

[3]
1cdf9f7670a7 nvmet: cleanups the loop in nvmet_async_events_process
696ece751366 nvmet: add async event tracing support


Best Regards,
  Yi Zhang


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: regression: blktests nvme/004 failed on linux-stable 5.7.y
  2020-06-29 10:02 ` regression: blktests nvme/004 failed on linux-stable 5.7.y Yi Zhang
@ 2020-06-29 10:59   ` Greg KH
  2020-06-29 11:40     ` Yi Zhang
  0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2020-06-29 10:59 UTC (permalink / raw)
  To: Yi Zhang; +Cc: linux-nvme, chaitanya.kulkarni, stable

On Mon, Jun 29, 2020 at 06:02:23AM -0400, Yi Zhang wrote:
> Hello
> 
> commit[1] introduced regression that will lead blktest nvme/004 failed on v5.7.5, and commits [2] fixed this issue on latest linux tree.
> But commit[2] cannot be directly applied to stable tree due to dependceny[3], could you help backport the fix and dependency to stable tree, thanks.
> 
> 
> [1]
> 64f5e9cdd711 nvmet: fix memory leak when removing namespaces and controllers concurrently
> 
> [2]
> 819f7b88b48f nvmet: fail outstanding host posted AEN req
> 
> [3]
> 1cdf9f7670a7 nvmet: cleanups the loop in nvmet_async_events_process
> 696ece751366 nvmet: add async event tracing support

Why is this last commit needed?

The other ones are already queued up in the current queue, thanks.

greg k-h

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: regression: blktests nvme/004 failed on linux-stable 5.7.y
  2020-06-29 10:59   ` Greg KH
@ 2020-06-29 11:40     ` Yi Zhang
  0 siblings, 0 replies; 3+ messages in thread
From: Yi Zhang @ 2020-06-29 11:40 UTC (permalink / raw)
  To: Greg KH; +Cc: linux-nvme, chaitanya.kulkarni, stable



On 6/29/20 6:59 PM, Greg KH wrote:
> On Mon, Jun 29, 2020 at 06:02:23AM -0400, Yi Zhang wrote:
>> Hello
>>
>> commit[1] introduced regression that will lead blktest nvme/004 failed on v5.7.5, and commits [2] fixed this issue on latest linux tree.
>> But commit[2] cannot be directly applied to stable tree due to dependceny[3], could you help backport the fix and dependency to stable tree, thanks.
>>
>>
>> [1]
>> 64f5e9cdd711 nvmet: fix memory leak when removing namespaces and controllers concurrently
>>
>> [2]
>> 819f7b88b48f nvmet: fail outstanding host posted AEN req
>>
>> [3]
>> 1cdf9f7670a7 nvmet: cleanups the loop in nvmet_async_events_process

Without it, the other patch cannot be applied directly on stable.
yes, we can backport them without bellow patch, I also found they 
already queued up, sorry for the noise.

>> 696ece751366 nvmet: add async event tracing support
> Why is this last commit needed?
>
> The other ones are already queued up in the current queue, thanks.
>
> greg k-h
>


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-06-29 21:35 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <1528690896.32343478.1593229315244.JavaMail.zimbra@redhat.com>
2020-06-29 10:02 ` regression: blktests nvme/004 failed on linux-stable 5.7.y Yi Zhang
2020-06-29 10:59   ` Greg KH
2020-06-29 11:40     ` Yi Zhang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).