linux-kernel - Re: [PATCH] mtip32xx: Correctly handle bio->bi

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20130515080939.GD3276@kernel.dk>
Date:	Wed, 15 May 2013 10:09:39 +0200
From:	Jens Axboe <axboe@...nel.dk>
To:	Sam Bradshaw <sbradshaw@...ron.com>
Cc:	linux-kernel@...r.kernel.org, asamymuthupa@...ron.com
Subject: Re: [PATCH] mtip32xx: Correctly handle bio->bi_idx != 0 conditions

On Tue, May 14 2013, Sam Bradshaw wrote:
> 
> Stacking drivers may append bvecs to existing bio's, resulting
> in non-zero bi_idx conditions.  This patch counts the loops of
> bio_for_each_segment() rather than inheriting the bi_idx value
> to pass as a segment count to the hardware submission routine.

Yup, that's a plain bug. Iteration always starts at current index and
forward, so nents wont necessarily start at 0. Applied.

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/