On Sun, Jan 23, 2022 at 05:43:57PM +0100, Florian Larysch wrote:
> The LBA Format Data structure is dword-sized, but struct nvme_lba_format
> erroneously contains an additional member, misaligning all LBAF
> descriptors after the first and causing them to be misinterpreted.
> Remove it.
Thanks. I
On 02.02.22 16:24, Kevin O'Connor wrote:
On Wed, Feb 02, 2022 at 11:50:50AM +0100, Alexander Graf wrote:
On 02.02.22 02:52, Kevin O'Connor wrote:
On Tue, Feb 01, 2022 at 08:39:10PM +0100, Florian Larysch wrote:
On Thu, Jan 27, 2022 at 11:37:52AM -0500, Kevin O'Connor wrote:
Thanks. I don't
On Wed, Feb 02, 2022 at 11:50:50AM +0100, Alexander Graf wrote:
>
> On 02.02.22 02:52, Kevin O'Connor wrote:
> > On Tue, Feb 01, 2022 at 08:39:10PM +0100, Florian Larysch wrote:
> > > On Thu, Jan 27, 2022 at 11:37:52AM -0500, Kevin O'Connor wrote:
> > > > Thanks. I don't know enough about NVMe to
On 02.02.22 02:52, Kevin O'Connor wrote:
On Tue, Feb 01, 2022 at 08:39:10PM +0100, Florian Larysch wrote:
On Thu, Jan 27, 2022 at 11:37:52AM -0500, Kevin O'Connor wrote:
Thanks. I don't know enough about NVMe to review this patch though.
Maybe Julian or Alex could comment?
Happy to hear thei
On Tue, Feb 01, 2022 at 08:39:10PM +0100, Florian Larysch wrote:
> On Thu, Jan 27, 2022 at 11:37:52AM -0500, Kevin O'Connor wrote:
> > Thanks. I don't know enough about NVMe to review this patch though.
> > Maybe Julian or Alex could comment?
>
> Happy to hear their comments on this. However, I c
On Thu, Jan 27, 2022 at 11:37:52AM -0500, Kevin O'Connor wrote:
> Thanks. I don't know enough about NVMe to review this patch though.
> Maybe Julian or Alex could comment?
Happy to hear their comments on this. However, I can also try to explain
the reasoning in a bit more detail.
This follows fr
On Sun, Jan 23, 2022 at 05:43:57PM +0100, Florian Larysch wrote:
> The LBA Format Data structure is dword-sized, but struct nvme_lba_format
> erroneously contains an additional member, misaligning all LBAF
> descriptors after the first and causing them to be misinterpreted.
> Remove it.
Thanks. I