On Fri, Jun 07, 2024 at 11:42:54AM -0400, Mike Snitzer wrote:
> > For dm-integrity my testing showed that even the baseline fails to create
> > the luks-based dm-crypto with dm-integrity backing for the authentication
> > data. As the failure is non-fatal I've not addressed it here.
>
> Setup is
On Fri, 7 Jun 2024, Mike Snitzer wrote:
> On Fri, Jun 07, 2024 at 07:58:54AM +0200, Christoph Hellwig wrote:
> > Hi Jens, hi Martin,
> >
> > this series converts the blk-integrity settings to sit in the queue
> > limits and be updated through the atomic queue limits API.
> >
> > I've mostly t
On Fri, Jun 07, 2024 at 07:58:54AM +0200, Christoph Hellwig wrote:
> Hi Jens, hi Martin,
>
> this series converts the blk-integrity settings to sit in the queue
> limits and be updated through the atomic queue limits API.
>
> I've mostly tested this with nvme, scsi is only covered by simple
> scs
Hi Jens, hi Martin,
this series converts the blk-integrity settings to sit in the queue
limits and be updated through the atomic queue limits API.
I've mostly tested this with nvme, scsi is only covered by simple
scsi_debug based tests.
For MD I found an pre-existing error handling bug when comb
