[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230821110633.432a1599@canb.auug.org.au>
Date: Mon, 21 Aug 2023 11:06:33 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Cc: Networking <netdev@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the net-next tree with the net tree
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
include/net/inet_sock.h
between commit:
f866fbc842de ("ipv4: fix data-races around inet->inet_id")
from the net tree and commit:
c274af224269 ("inet: introduce inet->inet_flags")
from the net-next tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc include/net/inet_sock.h
index 491ceb7ebe5d,acbb93d7607a..000000000000
--- a/include/net/inet_sock.h
+++ b/include/net/inet_sock.h
@@@ -218,12 -218,12 +218,12 @@@ struct inet_sock
#define inet_dport sk.__sk_common.skc_dport
#define inet_num sk.__sk_common.skc_num
+ unsigned long inet_flags;
__be32 inet_saddr;
__s16 uc_ttl;
- __u16 cmsg_flags;
- struct ip_options_rcu __rcu *inet_opt;
- atomic_t inet_id;
__be16 inet_sport;
++ atomic_t inet_id;
+ struct ip_options_rcu __rcu *inet_opt;
- __u16 inet_id;
__u8 tos;
__u8 min_ttl;
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists