Colin,
> Currently if lport is null then the null lport pointer is dereference
> when printing out debug via the FC_LPORT_DB macro. Fix this by using
> the more generic FC_LIBFC_DBG debug macro instead that does not use
> lport.
Applied to 5.3/scsi-fixes, thanks!
--
Martin K. Petersen Or
On Fri, 12 Jul 2019, Hannes Reinecke wrote:
> On 7/2/19 11:18 AM, Colin King wrote:
> > From: Colin Ian King
> >
> > Currently if lport is null then the null lport pointer is dereference
> > when printing out debug via the FC_LPORT_DB macro. Fix this by using
> > the more generic FC_LIBFC_DBG d
On 7/2/19 11:18 AM, Colin King wrote:
> From: Colin Ian King
>
> Currently if lport is null then the null lport pointer is dereference
> when printing out debug via the FC_LPORT_DB macro. Fix this by using
> the more generic FC_LIBFC_DBG debug macro instead that does not use
> lport.
>
> Address
Hannes,
Please review!
> Currently if lport is null then the null lport pointer is dereference
> when printing out debug via the FC_LPORT_DB macro. Fix this by using
> the more generic FC_LIBFC_DBG debug macro instead that does not use
> lport.
--
Martin K. Petersen Oracle Linux Engineer
4 matches
Mail list logo