[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

request commit for 6.1 too // scsi: megaraid_sas: Add flexible array member for SGLs



Dear all,

I've already followed the reply instructions on LKML - but it somewhat
messed up my message there (so probably nobody knows what I'm talking about) - however ...

Earlier this year you've committed

scsi: megaraid_sas: Add flexible array member for SGLs
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=a9a3629592ab

... but it only made it into 6.3 at this time.

I hereby kindly request to see this commit in LTS 6.1 too.

Why?
Debian Bookworm is soon to be released (RC4 at this moment) and is not yet aware of this issue...

We're currently testing some new DELL servers and want to roll 'em out
once Bookworm is released.
Previous tests using Debian Bullseye (Kernel 5.10 based) where fine...
but all of a sudden - with Debian Bookworm (Kernel 6.1 based) this weird
call trace shows up in our logs - and this is hard to explain to QA ppl.

Apart from this call trace showing up - I don't see any weird things.
The /dev/disk/by-uuid/ thingie I wrote about in

https://lkml.org/lkml/2023/6/9/1384

is nonsense ofcourse - because upon further thinking about what I wrote
it came apparent that the command I'm using does change/nullify the UUID
I am talking about.

Thankyou!
Frank Reppin


--
43rd Law of Computing:
        Anything that can go wr
fortune: Segmentation violation -- Core dumped


Reply to: