netdev - Re: [PATCH v2] [NET]: Unmap fragment page once iterator is done

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANeycqrPeBvOQeSmRZGcJwCvW=W=Hr+QW8O-99TB_Cqpv5Qr_Q@mail.gmail.com>
Date:	Mon, 24 Jun 2013 15:47:18 -0700
From:	Wedson Almeida Filho <wedsonaf@...il.com>
To:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Cc:	"David S. Miller" <davem@...emloft.net>,
	Thomas Graf <tgraf@...g.ch>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] [NET]: Unmap fragment page once iterator is done

The summary line of the original commit is "[NET]: Zerocopy sequential
reading of skb data".

On Mon, Jun 24, 2013 at 3:35 AM, Sergei Shtylyov
<sergei.shtylyov@...entembedded.com> wrote:
> Hello.
>
>
> On 24-06-2013 10:33, Wedson Almeida Filho wrote:
>
>> Callers of skb_seq_read() are currently forced to call
>> skb_abort_seq_read()
>> even when consuming all the data because the last call to skb_seq_read
>> (the
>> one that returns 0 to indicate the end) fails to unmap the last fragment
>> page.
>
>
>> With this patch callers will be allowed to traverse the SKB data by
>> calling
>> skb_prepare_seq_read() once and repeatedly calling skb_seq_read() as
>> originally
>> intended (and documented in the original commit 677e90eda), that is, only
>> call
>
>
>    Please also specify the summary line of that commit.
>
>
>> skb_abort_seq_read() if the sequential read is actually aborted.
>
>
>> Signed-off-by: Wedson Almeida Filho <wedsonaf@...il.com>
>
>
> WBR, Sergei
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html