linux-kernel - Re: [PATCH] block: don't merge bios with different app

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176775184888.14145.7372547504260204885.b4-ty@kernel.dk>
Date: Tue, 06 Jan 2026 19:10:48 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Caleb Sander Mateos <csander@...estorage.com>
Cc: Kanchan Joshi <joshi.k@...sung.com>, Ming Lei <ming.lei@...hat.com>, 
 linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] block: don't merge bios with different app_tags


On Tue, 06 Jan 2026 13:08:37 -0700, Caleb Sander Mateos wrote:
> nvme_set_app_tag() uses the app_tag value from the bio_integrity_payload
> of the struct request's first bio. This assumes all the request's bios
> have the same app_tag. However, it is possible for bios with different
> app_tag values to be merged into a single request.
> Add a check in blk_integrity_merge_{bio,rq}() to prevent the merging of
> bios/requests with different app_tag values if BIP_CHECK_APPTAG is set.
> 
> [...]

Applied, thanks!

[1/1] block: don't merge bios with different app_tags
      commit: 6acd4ac5f8f0ec9b946875553e52907700bcfc77

Best regards,
-- 
Jens Axboe