Users.ReportABug History
Hide minor edits - Show changes to output
Changed lines 1-2 from:
Bug-Reports can be submitted on our bugzilla: %newwin%[[http://multipath-tcp.org/bugzilla3/]]
to:
Bug-Reports can be submitted on our github-page: %newwin%[[https://github.com/multipath-tcp/mptcp/issues]]
Changed lines 11-12 from:
Check in the crash dump if you have a line telling the line number of the bug, like: @@kernel BUG at net/ipv4/mptcp.c:1082!@@.
to:
Check in the crash dump if you have a line telling the line number of the bug, like: @@kernel BUG at net/mptcp/mptcp.c:1082!@@.
Changed line 27 from:
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@\\
to:
@@net/mptcp/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@\\
Changed line 37 from:
It is always useful as well to attach your @@.config@@ file to the ticket.
to:
It is always useful as well to attach your @@.config@@ file to the ticket.
Changed lines 1-2 from:
Bug-Reports can be submitted on our bugracker: %newwin%[[http://multipath-tcp.org/bugzilla3/]]
to:
Bug-Reports can be submitted on our bugzilla: %newwin%[[http://multipath-tcp.org/bugzilla3/]]
Changed line 37 from:
It is always useful as well to attach your @@.config@@ file to the ticket.
to:
It is always useful as well to attach your @@.config@@ file to the ticket.
Changed line 1 from:
Bug-Reports can be submitted on our bugracker: %newwin%[[http://github.com/multipath-tcp/mptcp/issues]]
to:
Bug-Reports can be submitted on our bugracker: %newwin%[[http://multipath-tcp.org/bugzilla3/]]
Changed line 1 from:
Bug-Reports can be submitted on our bugzilla: %newwin%[[http://mptcp.info.ucl.ac.be/bugzilla3/]]
to:
Bug-Reports can be submitted on our bugracker: %newwin%[[http://github.com/multipath-tcp/mptcp/issues]]
Changed lines 20-21 from:
Attach the file bin_excerpt.txt to the bug-report.
to:
Attach the file bin_excerpt.txt to the bug-report.\\
\\
\\
Changed lines 16-17 from:
Then save the useful info in a file, with the following command:
@@objdump -d vmlinux | grep -A 500 -B 500 "c034717a:" > bin_excerpt.txt@@
to:
Then save the useful info in a file, with the following command:\\
\\
@@objdump -d vmlinux | grep -A 500 -B 500 "c034717a:" > bin_excerpt.txt@@\\
\\
\\
@@objdump -d vmlinux | grep -A 500 -B 500 "c034717a:" > bin_excerpt.txt@@\\
\\
Changed lines 21-22 from:
Find the file containing the definition of the function. You should easily find it with @@git grep mptcp_check_rcv_queue@@. In the example, this will tell you\\ \\
to:
Find the file containing the definition of the function. You should easily find it with @@git grep mptcp_check_rcv_queue@@. In the example, this will tell you\\
\\
\\
Changed lines 25-27 from:
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len,...@@\\ \\
A quick check shows you that the function is defined in mptcp.c, hence we compile it:\\ \\
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)\\ \\
A quick check shows you that the function is defined in mptcp.c, hence we compile it:\\
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)\\
to:
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len,...@@\\
\\
A quick check shows you that the function is defined in mptcp.c, hence we compile it:\\
\\
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)\\
\\
\\
A quick check shows you that the function is defined in mptcp.c, hence we compile it:\\
\\
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)\\
\\
Changed line 21 from:
Find the file containing the definition of the function. You should easily find it with @@git grep mptcp_check_rcv_queue@@. In the example, this will tell you\\
to:
Find the file containing the definition of the function. You should easily find it with @@git grep mptcp_check_rcv_queue@@. In the example, this will tell you\\ \\
Changed lines 24-26 from:
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len,...@@\\
A quick check shows you that the function is defined in mptcp.c, hence we compile it:\\
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)\\
to:
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len,...@@\\ \\
A quick check shows you that the function is defined in mptcp.c, hence we compile it:\\ \\
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)\\ \\
A quick check shows you that the function is defined in mptcp.c, hence we compile it:\\ \\
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)\\ \\
Changed lines 21-28 from:
Find the file containing the definition of the function. You should easily find it with @@git grep mptcp_check_rcv_queue@@. In the example, this will tell you
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len,...@@
A quick check shows you that the function is defined in mptcp.c, hence we compile it:
@@make net/ipv4/mptcp.s@@
(note the "s" at the end of@@mptcp@@)
Attach the resulting mptcp.s file to the bug-report.
(note the "s" at the end of
to:
Find the file containing the definition of the function. You should easily find it with @@git grep mptcp_check_rcv_queue@@. In the example, this will tell you\\
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@\\
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@\\
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len,...@@\\
A quick check shows you that the function is defined in mptcp.c, hence we compile it:\\
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)\\
Attach the resulting mptcp.s file to the bug-report.
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@\\
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@\\
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len,...@@\\
A quick check shows you that the function is defined in mptcp.c, hence we compile it:\\
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)\\
Attach the resulting mptcp.s file to the bug-report.
Changed line 26 from:
@@make net/ipv4/mptcp.s@@
to:
@@make net/ipv4/mptcp.s@@
Changed line 26 from:
@@make net/ipv4/mptcp.s@@
to:
@@make net/ipv4/mptcp.s@@
Changed lines 26-28 from:
Attach the resulting mptcp.s file to the bug-report.
to:
@@make net/ipv4/mptcp.s@@
(note the "s" at the end of @@mptcp@@)
Attach the resulting mptcp.s file to the bug-report.
(note the "s" at the end of @@mptcp@@)
Attach the resulting mptcp.s file to the bug-report.
Changed lines 27-28 from:
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
to:
@@make net/ipv4/mptcp.s@@
(note the "s" at the end of @@mptcp@@)
(note the "s" at the end of @@mptcp@@)
Changed line 27 from:
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
to:
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
Changed line 27 from:
to:
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
Changed lines 27-28 from:
to:
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
Changed line 27 from:
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
to:
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
Changed lines 26-28 from:
A quick check shows you that the function is defined in mptcp.c, hence we compile it: @@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@) Attach the resulting mptcp.s file to the bug-report.
to:
A quick check shows you that the function is defined in mptcp.c, hence we compile it:
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
Attach the resulting mptcp.s file to the bug-report.
@@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
Attach the resulting mptcp.s file to the bug-report.
Changed line 15 from:
to:
* Find in the stack trace the line providing the EIP field. ex: EIP: 0060:[<c034717a>]
Changed line 19 from:
to:
* We need the asm file containing the buggy function:
Changed line 18 from:
Attach the file (here, bin_excerpt.txt) to the bug-report.
to:
Attach the file bin_excerpt.txt to the bug-report.
Changed line 17 from:
@@objdump -d vmlinux | grep -A 500 -B 500 "c034717a:" > bin_excerpt.txt@@
to:
@@objdump -d vmlinux | grep -A 500 -B 500 "c034717a:" > bin_excerpt.txt@@
Changed line 1 from:
Bug-Reports can be submitted on our bugzilla: [[http://mptcp.info.ucl.ac.be/bugzilla3/]]
to:
Bug-Reports can be submitted on our bugzilla: %newwin%[[http://mptcp.info.ucl.ac.be/bugzilla3/]]
Changed line 7 from:
If you are using the apt-repository, and you have installed the crashdump-handler as described [[Users/HandleCrashdummps|here]], provide us the crashdump-file by uploading it to a public webhoster.
to:
If you are using the apt-repository, and you have installed the crashdump-handler as described [[Users/HandleCrashdumps|here]], provide us the crashdump-file by uploading it to a public webhoster.
Changed line 7 from:
If you are using the apt-repository, and you have installed the crashdump-handler as described here, provide us the crashdump-file by uploading it to a public webhoster.
to:
If you are using the apt-repository, and you have installed the crashdump-handler as described [[Users/HandleCrashdummps|here]], provide us the crashdump-file by uploading it to a public webhoster.
Changed lines 28-29 from:
to:
It is always useful as well to attach your @@.config@@ file to the ticket.
Changed lines 26-27 from:
A quick check shows you that the function is defined in mptcp.c, hence we compile it: @@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
Attach the resulting mptcp.s file to the bug-report.
to:
A quick check shows you that the function is defined in mptcp.c, hence we compile it: @@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@) Attach the resulting mptcp.s file to the bug-report.
Changed lines 25-26 from:
A quick check shows you that the function is defined in mptcp.c, hence we compile it: @@make net/ipv4/mptcp.s@@
to:
A quick check shows you that the function is defined in mptcp.c, hence we compile it: @@make net/ipv4/mptcp.s@@ (note the "s" at the end of @@mptcp@@)
Added line 28:
Changed lines 22-25 from:
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg,@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
@@
@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");
to:
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len,...@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,...@@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len,...@@
Changed lines 22-25 from:
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg,@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
to:
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg,@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
Changed line 21 from:
Find the file containing the definition of the function. You should easily find it with @@git grep mptcp_check_rcv_queue@@. In the example, this will tell you
to:
Find the file containing the definition of the function. You should easily find it with @@git grep mptcp_check_rcv_queue@@. In the example, this will tell you
Changed lines 22-25 from:
to:
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg,@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
Changed lines 16-17 from:
Attach the file (here, bin_excerpt.txt) to the bug-report.
to:
Then save the useful info in a file, with the following command:
@@objdump -d vmlinux | grep -A 500 -B 500 "c034717a:" > bin_excerpt.txt@@
Attach the file (here, bin_excerpt.txt) to the bug-report.
@@objdump -d vmlinux | grep -A 500 -B 500 "c034717a:" > bin_excerpt.txt@@
Attach the file (here, bin_excerpt.txt) to the bug-report.
Changed line 20 from:
Find in the stack trace the name of the buggy function (just one line after the EIP). ex: EIP is at mtcp_check_rcv_queue+0x32a/0x370
to:
Find in the stack trace the name of the buggy function (just one line after the EIP). ex: EIP is at mtcp_check_rcv_queue+0x32a/0x370
Changed lines 22-28 from:
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg,@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
A quick check shows you that the function is defined in mptcp.c, hence we compile it: @@make net/ipv4/mptcp.s@@
Attach the resulting mptcp.s file to the bug-report.
It is always useful as well to attach your @@.config@@ file to the ticket.
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
It is always useful as well to attach your @@.config@@ file to the ticket.
to:
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg,@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
A quick check shows you that the function is defined in mptcp.c, hence we compile it: @@make net/ipv4/mptcp.s@@
Attach the resulting mptcp.s file to the bug-report.
# It is always useful as well to attach your @@.config@@ file to the ticket.
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
A quick check shows you that the function is defined in mptcp.c, hence we compile it: @@make net/ipv4/mptcp.s@@
Attach the resulting mptcp.s file to the bug-report.
# It is always useful as well to attach your @@.config@@ file to the ticket.
Changed line 15 from:
Find in the stack trace the line providing the EIP field. ex: EIP: 0060:[<c034717a>]
to:
# Find in the stack trace the line providing the EIP field. ex: EIP: 0060:[<c034717a>]
Changed line 18 from:
to:
# We need the asm file containing the buggy function:
Added lines 1-27:
Bug-Reports can be submitted on our bugzilla: [[http://mptcp.info.ucl.ac.be/bugzilla3/]]
Be very explicit with the exact test scenario you have. Otherwise we might be unable to reproduce it. E.g., How many sufblows do you establish? Are you behind a NAT? Are you running through the real Internet or in a testbed? What kind of access mediums are you using? Please show us your routing-tables and ifconfig.
Provide the exact version of MPTCP you are using. If you used the git-repository, give us the git head. If you used the apt-repository show us @@uname -a@@.
If you are using the apt-repository, and you have installed the crashdump-handler as described here, provide us the crashdump-file by uploading it to a public webhoster.
If you use the git-repository, you have to analyze the crashdump yourself, as we cannot easily reproduce the same binary as you.
Check in the crash dump if you have a line telling the line number of the bug, like: @@kernel BUG at net/ipv4/mptcp.c:1082!@@.
Otherwise a bit more work is needed from you :
In order for us to know where in the code the error happened, which is possible by translating the binary address into a line in the source code. But for this, we need an excerpt of the disassembled code of your kernel (the vmlinux binary as you compiled it to produce the bug). You can get the excerpt very easily by conducting the following steps:
Find in the stack trace the line providing the EIP field. ex: EIP: 0060:[<c034717a>]
Then save the useful info in a file, with the following command: objdump -d vmlinux | grep -A 500 -B 500 "c034717a:" > bin_excerpt.txt
Attach the file (here, bin_excerpt.txt) to the bug-report.
Also in case of Segmentation violation or NULL pointer: we need the asm file containing the buggy function:
Find in the stack trace the name of the buggy function (just one line after the EIP). ex: EIP is at mtcp_check_rcv_queue+0x32a/0x370
Find the file containing the definition of the function. You should easily find it with @@git grep mptcp_check_rcv_queue@@. In the example, this will tell you
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg,@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
A quick check shows you that the function is defined in mptcp.c, hence we compile it: @@make net/ipv4/mptcp.s@@
Attach the resulting mptcp.s file to the bug-report.
It is always useful as well to attach your @@.config@@ file to the ticket.
Be very explicit with the exact test scenario you have. Otherwise we might be unable to reproduce it. E.g., How many sufblows do you establish? Are you behind a NAT? Are you running through the real Internet or in a testbed? What kind of access mediums are you using? Please show us your routing-tables and ifconfig.
Provide the exact version of MPTCP you are using. If you used the git-repository, give us the git head. If you used the apt-repository show us @@uname -a@@.
If you are using the apt-repository, and you have installed the crashdump-handler as described here, provide us the crashdump-file by uploading it to a public webhoster.
If you use the git-repository, you have to analyze the crashdump yourself, as we cannot easily reproduce the same binary as you.
Check in the crash dump if you have a line telling the line number of the bug, like: @@kernel BUG at net/ipv4/mptcp.c:1082!@@.
Otherwise a bit more work is needed from you :
In order for us to know where in the code the error happened, which is possible by translating the binary address into a line in the source code. But for this, we need an excerpt of the disassembled code of your kernel (the vmlinux binary as you compiled it to produce the bug). You can get the excerpt very easily by conducting the following steps:
Find in the stack trace the line providing the EIP field. ex: EIP: 0060:[<c034717a>]
Then save the useful info in a file, with the following command: objdump -d vmlinux | grep -A 500 -B 500 "c034717a:" > bin_excerpt.txt
Attach the file (here, bin_excerpt.txt) to the bug-report.
Also in case of Segmentation violation or NULL pointer: we need the asm file containing the buggy function:
Find in the stack trace the name of the buggy function (just one line after the EIP). ex: EIP is at mtcp_check_rcv_queue+0x32a/0x370
Find the file containing the definition of the function. You should easily find it with @@git grep mptcp_check_rcv_queue@@. In the example, this will tell you
@@include/net/mptcp.h:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg,@@
@@net/ipv4/mptcp.c:int mptcp_check_rcv_queue(struct multipath_pcb *mpcb,struct msghdr *msg, @@
@@net/ipv4/tcp.c: err=mptcp_check_rcv_queue(mpcb,msg, &len, data_seq, &copied, flags);@@
@@net/ipv4/tcp.c: printk(KERN_ERR "error in mptcp_check_rcv_queue\n");@@
A quick check shows you that the function is defined in mptcp.c, hence we compile it: @@make net/ipv4/mptcp.s@@
Attach the resulting mptcp.s file to the bug-report.
It is always useful as well to attach your @@.config@@ file to the ticket.

