From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>,
NetFilter <netfilter-devel@vger.kernel.org>
Cc: David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Matteo Croce <mcroce@redhat.com>, Julian Anastasov <ja@ssi.bg>
Subject: Re: linux-next: manual merge of the net-next tree with the netfilter tree
Date: Thu, 16 Aug 2018 09:47:23 +1000 [thread overview]
Message-ID: <20180816094723.07452406@canb.auug.org.au> (raw)
In-Reply-To: <20180807124932.73422224@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 3027 bytes --]
Hi all,
On Tue, 7 Aug 2018 12:49:32 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> net/netfilter/ipvs/ip_vs_conn.c
>
> between commit:
>
> 16e98cec49a4 ("ipvs: don't show negative times in ip_vs_conn")
>
> from the netfilter tree and commit:
>
> ec1b28ca9674 ("ipvs: provide just conn to ip_vs_state_name")
>
> 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 net/netfilter/ipvs/ip_vs_conn.c
> index 615286dcf4c0,0edc62910ebf..000000000000
> --- a/net/netfilter/ipvs/ip_vs_conn.c
> +++ b/net/netfilter/ipvs/ip_vs_conn.c
> @@@ -1107,10 -1122,8 +1122,10 @@@ static int ip_vs_conn_seq_show(struct s
> &cp->caddr.in6, ntohs(cp->cport),
> &cp->vaddr.in6, ntohs(cp->vport),
> dbuf, ntohs(cp->dport),
> - ip_vs_state_name(cp->protocol, cp->state),
> + ip_vs_state_name(cp),
> - (cp->timer.expires-jiffies)/HZ, pe_data);
> + jiffies_delta_to_msecs(cp->timer.expires -
> + jiffies) / 1000,
> + pe_data);
> else
> #endif
> seq_printf(seq,
> @@@ -1120,10 -1133,8 +1135,10 @@@
> ntohl(cp->caddr.ip), ntohs(cp->cport),
> ntohl(cp->vaddr.ip), ntohs(cp->vport),
> dbuf, ntohs(cp->dport),
> - ip_vs_state_name(cp->protocol, cp->state),
> + ip_vs_state_name(cp),
> - (cp->timer.expires-jiffies)/HZ, pe_data);
> + jiffies_delta_to_msecs(cp->timer.expires -
> + jiffies) / 1000,
> + pe_data);
> }
> return 0;
> }
> @@@ -1173,10 -1184,9 +1188,10 @@@ static int ip_vs_conn_sync_seq_show(str
> &cp->caddr.in6, ntohs(cp->cport),
> &cp->vaddr.in6, ntohs(cp->vport),
> dbuf, ntohs(cp->dport),
> - ip_vs_state_name(cp->protocol, cp->state),
> + ip_vs_state_name(cp),
> ip_vs_origin_name(cp->flags),
> - (cp->timer.expires-jiffies)/HZ);
> + jiffies_delta_to_msecs(cp->timer.expires -
> + jiffies) / 1000);
> else
> #endif
> seq_printf(seq,
> @@@ -1186,10 -1196,9 +1201,10 @@@
> ntohl(cp->caddr.ip), ntohs(cp->cport),
> ntohl(cp->vaddr.ip), ntohs(cp->vport),
> dbuf, ntohs(cp->dport),
> - ip_vs_state_name(cp->protocol, cp->state),
> + ip_vs_state_name(cp),
> ip_vs_origin_name(cp->flags),
> - (cp->timer.expires-jiffies)/HZ);
> + jiffies_delta_to_msecs(cp->timer.expires -
> + jiffies) / 1000);
> }
> return 0;
> }
This is now a conflict between Linus' tree and the netfilter tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-08-15 23:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 2:49 Stephen Rothwell
2018-08-15 23:47 ` Stephen Rothwell [this message]
2018-08-16 0:08 ` Pablo Neira Ayuso
-- strict thread matches above, loose matches on Subject: below --
2026-04-08 14:10 Mark Brown
2026-04-08 15:08 ` Mark Brown
2026-04-08 16:43 ` Matthieu Baerts
2026-04-08 17:00 ` Mark Brown
2026-04-09 1:04 ` Andrea Mayer
2020-12-10 2:11 Stephen Rothwell
2016-11-09 23:56 Stephen Rothwell
2016-11-10 0:31 ` Pablo Neira Ayuso
2016-11-13 4:43 ` David Miller
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=20180816094723.07452406@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=ja@ssi.bg \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcroce@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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®