linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Ayush Sawal <ayush.sawal@chelsio.com>,
	Vinay Kumar Yadav <vinay.yadav@chelsio.com>,
	Rohit Maheshwari <rohitm@chelsio.com>
Subject: Re: linux-next: Tree for May 26 (drivers/crypto/chelsio/chcr_ktls.c)
Date: Tue, 26 May 2020 08:46:49 -0700	[thread overview]
Message-ID: <ca9f612e-1cd7-d2b8-d1f0-497ffcbd5de5@infradead.org> (raw)
In-Reply-To: <20200526203932.732df7c6@canb.auug.org.au>

On 5/26/20 3:39 AM, Stephen Rothwell wrote:
> Hi all,
> 
> News: there will be no linux-next release tomorrow.
> 
> Changes since 20200525:
> 

on i386:

when CONFIG_IPV6 is not set/enabled:


  CC      drivers/crypto/chelsio/chcr_ktls.o
In file included from ../include/linux/tcp.h:19:0,
                 from ../include/net/tls.h:41,
                 from ../drivers/crypto/chelsio/chcr_ktls.h:8,
                 from ../drivers/crypto/chelsio/chcr_ktls.c:6:
../drivers/crypto/chelsio/chcr_ktls.c: In function 'chcr_ktls_act_open_req6':
../include/net/sock.h:380:37: error: 'struct sock_common' has no member named 'skc_v6_rcv_saddr'; did you mean 'skc_rcv_saddr'?
 #define sk_v6_rcv_saddr __sk_common.skc_v6_rcv_saddr
                                     ^
../drivers/crypto/chelsio/chcr_ktls.c:257:37: note: in expansion of macro 'sk_v6_rcv_saddr'
  cpl->local_ip_hi = *(__be64 *)&sk->sk_v6_rcv_saddr.in6_u.u6_addr8[0];
                                     ^~~~~~~~~~~~~~~
../include/net/sock.h:380:37: error: 'struct sock_common' has no member named 'skc_v6_rcv_saddr'; did you mean 'skc_rcv_saddr'?
 #define sk_v6_rcv_saddr __sk_common.skc_v6_rcv_saddr
                                     ^
../drivers/crypto/chelsio/chcr_ktls.c:258:37: note: in expansion of macro 'sk_v6_rcv_saddr'
  cpl->local_ip_lo = *(__be64 *)&sk->sk_v6_rcv_saddr.in6_u.u6_addr8[8];
                                     ^~~~~~~~~~~~~~~
../include/net/sock.h:379:34: error: 'struct sock_common' has no member named 'skc_v6_daddr'; did you mean 'skc_daddr'?
 #define sk_v6_daddr  __sk_common.skc_v6_daddr
                                  ^
../drivers/crypto/chelsio/chcr_ktls.c:259:36: note: in expansion of macro 'sk_v6_daddr'
  cpl->peer_ip_hi = *(__be64 *)&sk->sk_v6_daddr.in6_u.u6_addr8[0];
                                    ^~~~~~~~~~~
../include/net/sock.h:379:34: error: 'struct sock_common' has no member named 'skc_v6_daddr'; did you mean 'skc_daddr'?
 #define sk_v6_daddr  __sk_common.skc_v6_daddr
                                  ^
../drivers/crypto/chelsio/chcr_ktls.c:260:36: note: in expansion of macro 'sk_v6_daddr'
  cpl->peer_ip_lo = *(__be64 *)&sk->sk_v6_daddr.in6_u.u6_addr8[8];
                                    ^~~~~~~~~~~
../drivers/crypto/chelsio/chcr_ktls.c: In function 'chcr_setup_connection':
../include/net/sock.h:379:34: error: 'struct sock_common' has no member named 'skc_v6_daddr'; did you mean 'skc_daddr'?
 #define sk_v6_daddr  __sk_common.skc_v6_daddr
                                  ^
../drivers/crypto/chelsio/chcr_ktls.c:295:27: note: in expansion of macro 'sk_v6_daddr'
       ipv6_addr_type(&sk->sk_v6_daddr) == IPV6_ADDR_MAPPED)) {
                           ^~~~~~~~~~~
../include/net/sock.h:380:37: error: 'struct sock_common' has no member named 'skc_v6_rcv_saddr'; did you mean 'skc_rcv_saddr'?
 #define sk_v6_rcv_saddr __sk_common.skc_v6_rcv_saddr
                                     ^
../drivers/crypto/chelsio/chcr_ktls.c:302:29: note: in expansion of macro 'sk_v6_rcv_saddr'
           (const u32 *)&sk->sk_v6_rcv_saddr.in6_u.u6_addr8,
                             ^~~~~~~~~~~~~~~
../drivers/crypto/chelsio/chcr_ktls.c: In function 'chcr_ktls_dev_del':
../include/net/sock.h:379:34: error: 'struct sock_common' has no member named 'skc_v6_daddr'; did you mean 'skc_daddr'?
 #define sk_v6_daddr  __sk_common.skc_v6_daddr
                                  ^
../drivers/crypto/chelsio/chcr_ktls.c:400:26: note: in expansion of macro 'sk_v6_daddr'
        (const u32 *)&sk->sk_v6_daddr.in6_u.u6_addr8,
                          ^~~~~~~~~~~
../drivers/crypto/chelsio/chcr_ktls.c: In function 'chcr_ktls_dev_add':
../include/net/sock.h:379:34: error: 'struct sock_common' has no member named 'skc_v6_daddr'; did you mean 'skc_daddr'?
 #define sk_v6_daddr  __sk_common.skc_v6_daddr
                                  ^
../drivers/crypto/chelsio/chcr_ktls.c:494:27: note: in expansion of macro 'sk_v6_daddr'
       ipv6_addr_type(&sk->sk_v6_daddr) == IPV6_ADDR_MAPPED)) {
                           ^~~~~~~~~~~
In file included from ../arch/x86/include/asm/string.h:3:0,
                 from ../include/linux/string.h:20,
                 from ../arch/x86/include/asm/page_32.h:35,
                 from ../arch/x86/include/asm/page.h:14,
                 from ../arch/x86/include/asm/thread_info.h:12,
                 from ../include/linux/thread_info.h:38,
                 from ../arch/x86/include/asm/preempt.h:7,
                 from ../include/linux/preempt.h:78,
                 from ../include/linux/spinlock.h:51,
                 from ../include/linux/wait.h:9,
                 from ../include/linux/wait_bit.h:8,
                 from ../include/linux/fs.h:6,
                 from ../include/linux/highmem.h:5,
                 from ../drivers/crypto/chelsio/chcr_ktls.c:5:
../include/net/sock.h:379:34: error: 'struct sock_common' has no member named 'skc_v6_daddr'; did you mean 'skc_daddr'?
 #define sk_v6_daddr  __sk_common.skc_v6_daddr
                                  ^
../arch/x86/include/asm/string_32.h:182:45: note: in definition of macro 'memcpy'
 #define memcpy(t, f, n) __builtin_memcpy(t, f, n)
                                             ^
../drivers/crypto/chelsio/chcr_ktls.c:497:22: note: in expansion of macro 'sk_v6_daddr'
   memcpy(daaddr, sk->sk_v6_daddr.in6_u.u6_addr8, 16);
                      ^~~~~~~~~~~


-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>

  reply	other threads:[~2020-05-26 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 10:39 linux-next: Tree for May 26 Stephen Rothwell
2020-05-26 15:46 ` Randy Dunlap [this message]
2020-05-26 16:24 ` linux-next: Tree for May 26 (hwmon/amd_energy.c) Randy Dunlap
2020-05-26 17:14   ` Guenter Roeck
2020-05-26 17:17     ` Randy Dunlap

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=ca9f612e-1cd7-d2b8-d1f0-497ffcbd5de5@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=ayush.sawal@chelsio.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rohitm@chelsio.com \
    --cc=sfr@canb.auug.org.au \
    --cc=vinay.yadav@chelsio.com \
    /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;
as well as URLs for NNTP newsgroup(s).