linux-kernel - Re: [PATCH] ASYNC_TX: fix the bug in async_tx_run

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]

Date:	Fri, 05 Sep 2008 17:16:01 +0400
From:	Ilya Yanok <yanok@...raft.com>
To:	Wolfgang Denk <wd@...x.de>
CC:	linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org,
	Yuri Tikhonov <yur@...raft.com>
Subject: Re: [PATCH] ASYNC_TX: fix the bug in async_tx_run_dependencies

Dear Wolfgang,

this patch is already applied (d2029eba in linux-2.6-denx repo) I just
sent it upstream.

Regards, Ilya.

Wolfgang Denk wrote:
>> Should clear the next pointer of the TX if we are sure that the
>> next TX (say NXT) will be submitted to the channel too. Overwise,
>> we break the chain of descriptors, because we lose the information
>> about the next descriptor to run. So next time, when invoke
>> async_tx_run_dependencies() with TX, it's TX->next will be NULL, and
>> NXT will be never submitted.
>>
>> Signed-off-by: Yuri Tikhonov <yur@...raft.com>
>> ---
>>  crypto/async_tx/async_tx.c |    3 ++-
>>  1 files changed, 2 insertions(+), 1 deletions(-)
>>     
>
> What about this patch? SHould it be applied to our repository?
>
> Best regards,
>
> Wolfgang Denk
>
>   

--
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/