From: kernel test robot <lkp@intel.com>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Cc: oe-kbuild-all@lists.linux.dev, Geliang Tang <geliang.tang@suse.com>
Subject: Re: [PATCH mptcp-next v2 04/30] mptcp: use mptcp_wnd_end helper
Date: Thu, 21 Sep 2023 04:10:57 +0800 [thread overview]
Message-ID: <202309210337.Gf1gTgm6-lkp@intel.com> (raw)
In-Reply-To: <61179b15016da6055cc5a33dfdaacdaa30883cfb.1695095289.git.geliang.tang@suse.com>
Hi Geliang,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.6-rc2 next-20230920]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Geliang-Tang/mptcp-drop-useless-ssk-in-pm_subflow_check_next/20230919-120834
base: linus/master
patch link: https://lore.kernel.org/r/61179b15016da6055cc5a33dfdaacdaa30883cfb.1695095289.git.geliang.tang%40suse.com
patch subject: [PATCH mptcp-next v2 04/30] mptcp: use mptcp_wnd_end helper
config: csky-allmodconfig (https://download.01.org/0day-ci/archive/20230921/202309210337.Gf1gTgm6-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230921/202309210337.Gf1gTgm6-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309210337.Gf1gTgm6-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from net/mptcp/options.c:13:
net/mptcp/options.c: In function 'ack_update_msk':
>> net/mptcp/options.c:1062:21: error: implicit declaration of function 'mptcp_wnd_end'; did you mean 'tcp_wnd_end'? [-Werror=implicit-function-declaration]
1062 | if (after64(mptcp_wnd_end(msk), READ_ONCE(msk->snd_nxt)))
| ^~~~~~~~~~~~~
net/mptcp/protocol.h:141:48: note: in definition of macro 'after64'
141 | #define after64(seq2, seq1) before64(seq1, seq2)
| ^~~~
cc1: some warnings being treated as errors
vim +1062 net/mptcp/options.c
1034
1035 static void ack_update_msk(struct mptcp_sock *msk,
1036 struct sock *ssk,
1037 struct mptcp_options_received *mp_opt)
1038 {
1039 u64 new_wnd_end, new_snd_una, snd_nxt = READ_ONCE(msk->snd_nxt);
1040 struct sock *sk = (struct sock *)msk;
1041 u64 old_snd_una;
1042
1043 mptcp_data_lock(sk);
1044
1045 /* avoid ack expansion on update conflict, to reduce the risk of
1046 * wrongly expanding to a future ack sequence number, which is way
1047 * more dangerous than missing an ack
1048 */
1049 old_snd_una = msk->snd_una;
1050 new_snd_una = mptcp_expand_seq(old_snd_una, mp_opt->data_ack, mp_opt->ack64);
1051
1052 /* ACK for data not even sent yet? Ignore.*/
1053 if (unlikely(after64(new_snd_una, snd_nxt)))
1054 new_snd_una = old_snd_una;
1055
1056 new_wnd_end = new_snd_una + tcp_sk(ssk)->snd_wnd;
1057
1058 if (after64(new_wnd_end, msk->wnd_end))
1059 msk->wnd_end = new_wnd_end;
1060
1061 /* this assumes mptcp_incoming_options() is invoked after tcp_ack() */
> 1062 if (after64(mptcp_wnd_end(msk), READ_ONCE(msk->snd_nxt)))
1063 __mptcp_check_push(sk, ssk);
1064
1065 if (after64(new_snd_una, old_snd_una)) {
1066 __mptcp_snd_una_update(msk, new_snd_una);
1067 __mptcp_data_acked(sk);
1068 }
1069 mptcp_data_unlock(sk);
1070
1071 trace_ack_update_msk(mp_opt->data_ack,
1072 old_snd_una, new_snd_una,
1073 new_wnd_end, msk->wnd_end);
1074 }
1075
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-20 20:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 4:02 [PATCH mptcp-next v2 00/30] userspace pm enhancements Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 01/30] mptcp: drop useless ssk in pm_subflow_check_next Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 02/30] mptcp: use mptcp_check_fallback helper Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 03/30] mptcp: use mptcp_get_ext helper Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 04/30] mptcp: use mptcp_wnd_end helper Geliang Tang
2023-09-20 20:10 ` kernel test robot [this message]
2023-09-19 4:02 ` [PATCH mptcp-next v2 05/30] mptcp: move sk assignment statement ahead Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 06/30] mptcp: define more local variables sk Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 07/30] selftests: mptcp: sockopt: drop mptcp_connect var Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 08/30] selftests: mptcp: display simult in extra_msg Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 09/30] mptcp: add mptcpi_subflows_total counter Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 10/30] selftests: mptcp: add chk_subflows_total helper Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 11/30] selftests: mptcp: add evts_get_info helper Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 12/30] selftests: mptcp: update userspace pm test helpers Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 13/30] selftests: mptcp: userspace pm remove id 0 subflow Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 14/30] mptcp: userspace pm allow creating " Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 15/30] selftests: mptcp: userspace pm create " Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 16/30] mptcp: userspace pm remove id 0 address Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 17/30] selftests: " Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 18/30] mptcp: add userspace_pm_get_entry helper Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 19/30] mptcp: add userspace pm addr entry refcount Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 20/30] mptcp: add netlink " Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 21/30] selftests: mptcp: add userspace pm fullmesh tests Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 22/30] selftests: mptcp: add mptcp_lib_kill_wait Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 23/30] selftests: mptcp: add mptcp_lib_evts_* Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 24/30] selftests: mptcp: userspace: print colored results Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 25/30] selftests: mptcp: add mptcp_lib_verify_listener_events Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 26/30] selftests: mptcp: add mptcp_lib_is_v6 Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 27/30] selftests: mptcp: add mptcp_lib_get_counter Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 28/30] selftests: mptcp: add mptcp_lib_make_file Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 29/30] selftests: mptcp: add mptcp_lib_check_transfer Geliang Tang
2023-09-19 4:02 ` [PATCH mptcp-next v2 30/30] selftests: mptcp: add mptcp_lib_wait_local_port_listen Geliang Tang
2023-09-19 4:45 ` selftests: mptcp: add mptcp_lib_wait_local_port_listen: Build Failure MPTCP CI
2023-09-19 8:10 ` Matthieu Baerts
2023-09-19 6:00 ` selftests: mptcp: add mptcp_lib_wait_local_port_listen: Tests Results MPTCP CI
2023-09-19 8:55 ` [PATCH mptcp-next v2 00/30] userspace pm enhancements Matthieu Baerts
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=202309210337.Gf1gTgm6-lkp@intel.com \
--to=lkp@intel.com \
--cc=geliang.tang@suse.com \
--cc=mptcp@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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