linux-kernel - Re: [PATCH] vringh: don't use vringh_kiov_advance() in vringh_iov

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: <169640462443.26245.17654721515803300599.git-patchwork-notify@kernel.org>
Date:   Wed, 04 Oct 2023 07:30:24 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Stefano Garzarella <sgarzare@...hat.com>
Cc:     virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org,
        kvm@...r.kernel.org, mst@...hat.com, jasowang@...hat.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@...emloft.net>:

On Mon, 25 Sep 2023 12:30:57 +0200 you wrote:
> In the while loop of vringh_iov_xfer(), `partlen` could be 0 if one of
> the `iov` has 0 lenght.
> In this case, we should skip the iov and go to the next one.
> But calling vringh_kiov_advance() with 0 lenght does not cause the
> advancement, since it returns immediately if asked to advance by 0 bytes.
> 
> Let's restore the code that was there before commit b8c06ad4d67d
> ("vringh: implement vringh_kiov_advance()"), avoiding using
> vringh_kiov_advance().
> 
> [...]

Here is the summary with links:
  - vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()
    https://git.kernel.org/netdev/net/c/7aed44babc7f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html