All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re: [PATCH v2 5/7] drivers/net: wrap csum_partial_copy_nocheck()
Date: Thu, 15 Apr 2021 09:21:45 +0200	[thread overview]
Message-ID: <87k0p4ui5y.fsf@xenomai.org> (raw)
In-Reply-To: <f00e7b29-5d8d-cdcb-adeb-630c277f7d67@siemens.com>


Jan Kiszka <jan.kiszka@siemens.com> writes:

> On 27.03.21 11:19, Philippe Gerum wrote:
>> From: Philippe Gerum <rpm@xenomai.org>
>> 
>> Since v5.9-rc1, csum_partial_copy_nocheck() forces a zero seed as its
>> last argument to csum_partial(). According to #cc44c17baf7f3, passing
>> a non-zero value would not even yield the proper result on some
>> architectures.
>> 
>> Nevertheless, the current ICMP code does expect a non-zero csum seed
>> to be used in the next computation, so let's wrap net_csum_copy() to
>> csum_partial_copy_nocheck() for pre-5.9 kernels, and open code it for
>> later kernels so that we still feed csum_partial() with the user-given
>> csum. We still expect the x86, ARM and arm64 implementations of
>> csum_partial() to do the right thing.
>> 
>
> If that issue only affects the ICMP code path, why not only changing
> that, leaving rtskb_copy_and_csum_bits with the benefit of doing copy
> and csum in one step?
>

As a result of #cc44c17baf7f3, I see no common helper available from the
kernel folding the copy and checksum operations anymore, so I see no way
to keep rtskb_copy_and_csum_bits() as is. Did you find an all-in-one
replacement for csum_partial_copy_nocheck() which would allow a csum
value to be fed in?

-- 
Philippe.


  reply	other threads:[~2021-04-15  7:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27 10:19 [PATCH v2 0/7] assorted v5.x related fixups Philippe Gerum
2021-03-27 10:19 ` [PATCH v2 1/7] cobalt/memory: fix __vmalloc() calls Philippe Gerum
2021-03-27 10:19 ` [PATCH v2 2/7] cobalt/debug: switch to mmap_lock interface Philippe Gerum
2021-03-27 10:19 ` [PATCH v2 3/7] cobalt/kernel: convert to proc_ops Philippe Gerum
2021-04-07  9:52   ` Jan Kiszka
2021-04-07 10:17     ` Philippe Gerum
2021-04-07 10:37       ` Jan Kiszka
2021-04-07 11:03         ` Philippe Gerum
2021-03-27 10:19 ` [PATCH v2 4/7] cobalt/debug: prefer dump_stack() to show_stack() Philippe Gerum
2021-03-27 10:19 ` [PATCH v2 5/7] drivers/net: wrap csum_partial_copy_nocheck() Philippe Gerum
2021-04-07 10:06   ` Jan Kiszka
2021-04-15  7:21     ` Philippe Gerum [this message]
2021-04-15  7:35       ` Jan Kiszka
2021-04-15  7:54         ` Philippe Gerum
2021-04-15  8:10           ` Jan Kiszka
2021-04-16 16:48             ` Philippe Gerum
2021-04-16 17:12               ` Jan Kiszka
2021-04-18  9:18                 ` Philippe Gerum
2021-04-18 15:50                   ` Philippe Gerum
2021-05-04 14:48                     ` Philippe Gerum
2021-05-05  5:43                       ` Jan Kiszka
2021-03-27 10:19 ` [PATCH v2 6/7] drivers/net: icmp: remove variable-length array Philippe Gerum
2021-04-07 10:24   ` Jan Kiszka
2021-03-27 10:19 ` [PATCH v2 7/7] drivers/net: cfg: fix config file load up Philippe Gerum
2021-04-07 10:35   ` Jan Kiszka
2021-05-04 17:18     ` Philippe Gerum
2021-04-07 10:39 ` [PATCH v2 0/7] assorted v5.x related fixups Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k0p4ui5y.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.