| 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
| ||
|
Message-Id: <20200601.144535.203726078659236025.davem@davemloft.net>
Date: Mon, 01 Jun 2020 14:45:35 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: victor@...iniac.net
Cc: netdev@...r.kernel.org, kuba@...nel.org, corbet@....net,
edumazet@...gle.com, willemb@...gle.com, maowenan@...wei.com,
arnd@...db.de, nhorman@...driver.com, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] af-packet: new flag to indicate all csums are
good
From: Victor Julien <victor@...iniac.net>
Date: Mon, 1 Jun 2020 22:49:37 +0200
> @@ -472,6 +472,12 @@ TP_STATUS_CSUM_VALID This flag indicates that at least the transport
> validated on the kernel side. If the flag is not set
> then we are free to check the checksum by ourselves
> provided that TP_STATUS_CSUMNOTREADY is also not set.
> +TP_STATUS_CSUM_UNNECESSARY This flag indicates that the driver validated all
> + the packets csums. If it is not set it might be that
> + the driver doesn't support this, or that one of the
> + layers csums is bad. TP_STATUS_CSUM_VALID may still
> + be set if the transport layer csum is correct or
> + if the driver supports only this mode.
> ====================== =======================================================
^^^^^
I think you need to reformat these dividers.
Powered by blists - more mailing lists