Re: [PATCH V4] scsi: avoid potential deadlock in iscsi_if_rx func

From: Martin K. Petersen
Date: Mon Dec 09 2019 - 20:40:21 EST

Next message: Stephen Rothwell: "linux-next: build failure after merge of the selinux tree"
Previous message: kbuild test robot: "[rcu:dev.2019.12.08a 37/105] net/tipc/crypto.c:261:39: error: implicit declaration of function 'lockdep_is_held'; did you mean 'lockdep_rtnl_is_held'?"
In reply to: Lee Duncan: "Re: [PATCH V4] scsi: avoid potential deadlock in iscsi_if_rx func"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Lee,

> My sincere apologies. I told wubo I had already reviewed the patch, so
> he didn't need another Reviewed-by from me. I see I was wrong.

OK.

The patch was all mangled so I had to apply the changes by hand. Can't
say that I'm a big fan of retries going negative but I guess that's just
personal taste.

Applied to 5.5/scsi-fixes. Thanks!

--
Martin K. Petersen Oracle Linux Engineering

Next message: Stephen Rothwell: "linux-next: build failure after merge of the selinux tree"
Previous message: kbuild test robot: "[rcu:dev.2019.12.08a 37/105] net/tipc/crypto.c:261:39: error: implicit declaration of function 'lockdep_is_held'; did you mean 'lockdep_rtnl_is_held'?"
In reply to: Lee Duncan: "Re: [PATCH V4] scsi: avoid potential deadlock in iscsi_if_rx func"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]