On Tue, Nov 28, 2017 at 2:05 PM, Meelis Roos wrote:
>> I think this chunk would solve the problem and result in the
>> same behavior as before:
>>
>> --- a/drivers/scsi/aacraid/commsup.c
>> +++ b/drivers/scsi/aacraid/commsup.c
>> @@ -2511,8 +2511,8 @@ int aac_command_thread(void *data)
>>
> I think this chunk would solve the problem and result in the
> same behavior as before:
>
> --- a/drivers/scsi/aacraid/commsup.c
> +++ b/drivers/scsi/aacraid/commsup.c
> @@ -2511,8 +2511,8 @@ int aac_command_thread(void *data)
> /* Synchronize our watches */
>
On Mon, Nov 27, 2017 at 8:17 PM, Meelis Roos wrote:
> Tried 4.15-rc1 on an old 32-bit HP Netserver with aacraid card. Compared
> to 4.14, there are new UBSAN warnings with timer related backtraces, so
> the timespec64 change seems suspicious:
> [ 12.228155] UBSAN: Undefined behaviour in
> driv
Tried 4.15-rc1 on an old 32-bit HP Netserver with aacraid card. Compared
to 4.14, there are new UBSAN warnings with timer related backtraces, so
the timespec64 change seems suspicious:
[ 12.228058]
[ 12.228155]
4 matches
Mail list logo