From: Stephen Kitt <steve@sk2.org>
To: David Miller <davem@davemloft.net>
Cc: joe@perches.com, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: Protect INET_ADDR_COOKIE on 32-bit architectures
Date: Fri, 8 May 2020 14:02:09 +0200 [thread overview]
Message-ID: <20200508140209.1715118b@heffalump.sk2.org> (raw)
In-Reply-To: <20200428.140746.1017253285576997409.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
On Tue, 28 Apr 2020 14:07:46 -0700 (PDT), David Miller <davem@davemloft.net>
wrote:
> From: Stephen Kitt <steve@sk2.org>
> Date: Tue, 28 Apr 2020 09:52:31 +0200
>
> > This patch changes INET_ADDR_COOKIE to declare a dummy typedef (so it
> > makes checkpatch.pl complain, sorry...)
>
> This is trading one problem for another, so in the end doesn't really
> move us forward.
Right, a dummy struct is probably better, I’ll send a v2.
Regards,
Stephen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-05-08 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 7:52 Stephen Kitt
2020-04-28 21:07 ` David Miller
2020-05-08 12:02 ` Stephen Kitt [this message]
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=20200508140209.1715118b@heffalump.sk2.org \
--to=steve@sk2.org \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®