On Fri, Jan 22, 2016 at 12:46:28AM +0100, Daniel Borkmann wrote:
> Add a test that symbol from relocation entry is actually related
> to map section and bail out with an error message if it's not the
> case; in relation to [1].
>
> [1] https://llvm.org/bugs/show_bug.cgi?id=26243
>
>
On Thu, Jan 21, 2016 at 04:49:35PM -0600, Josh Poimboeuf wrote:
> stacktool reports the following false positive warnings:
>
> stacktool: kernel/bpf/core.o: __bpf_prog_run()+0x5c: sibling call from
> callable instruction with changed frame pointer
> stacktool: kernel/bpf/core.o:
在 2016年01月21日 16:35, Jiri Pirko 写道:
Thu, Jan 21, 2016 at 06:32:58AM CET, wen.gang.w...@oracle.com wrote:
In a bonding setting, we determines fragment size according to MTU and
PMTU associated to the bonding master. If the slave finds the fragment
size is too big, it drops the fragment and
在 2016年01月22日 14:52, Jiri Pirko 写道:
Fri, Jan 22, 2016 at 05:21:28AM CET, wen.gang.w...@oracle.com wrote:
在 2016年01月21日 16:35, Jiri Pirko 写道:
Thu, Jan 21, 2016 at 06:32:58AM CET, wen.gang.w...@oracle.com wrote:
In a bonding setting, we determines fragment size according to MTU and
PMTU
On 01/20/2016 10:09 PM, Michael S. Tsirkin wrote:
> On Tue, Dec 01, 2015 at 02:39:44PM +0800, Jason Wang wrote:
>> Signed-off-by: Jason Wang
> Wow new API with no comments anywhere, and no
> commit log to say what it's good for.
> Want to know what it does and whether
>
On 01/20/2016 10:35 PM, Michael S. Tsirkin wrote:
> On Tue, Dec 01, 2015 at 02:39:45PM +0800, Jason Wang wrote:
>> This patch tries to poll for new added tx buffer or socket receive
>> queue for a while at the end of tx/rx processing. The maximum time
>> spent on polling were specified through a
Fri, Jan 22, 2016 at 05:21:28AM CET, wen.gang.w...@oracle.com wrote:
>
>
>在 2016年01月21日 16:35, Jiri Pirko 写道:
>>Thu, Jan 21, 2016 at 06:32:58AM CET, wen.gang.w...@oracle.com wrote:
>>>In a bonding setting, we determines fragment size according to MTU and
>>>PMTU associated to the bonding master.
* Alexei Starovoitov wrote:
> > > I could be missing something. I think either this patch is not need or
> > > you
> > > need to teach the tool to ignore all JITed stuff. I don't think it's
> > > practical to annotate everything. Different JITs do their own
From: Or Gerlitz
Date: Thu, 21 Jan 2016 14:49:25 +0200
> On Thu, Jan 21, 2016 at 1:27 PM, Jesper Dangaard Brouer
> wrote:
>> On Wed, 20 Jan 2016 15:27:38 -0800 Tom Herbert wrote:
>>
>>> eth_type_trans touches headers
>>
>> True,
On Thu, Jan 21, 2016 at 11:27:36AM -0800, Eric Dumazet wrote:
> On Fri, 2016-01-22 at 01:49 +0800, Xin Long wrote:
> > Previously, before rhashtable, /proc assoc listing was done by
> > read-locking the entire hash entry and dumping all assocs at once, so we
> > were sure that the assoc wasn't
The cgroup methods are no longer used after baac50b ("net:
tcp_memcontrol: simplify linkage between socket and page counter").
The hunk to delete them was included in the original patch but must
have gotten lost during conflict resolution on the way upstream.
Fixes: baac50b ("net: tcp_memcontrol:
From: Shuah Khan
Date: Thu, 21 Jan 2016 07:04:17 -0700
> On 01/20/2016 10:10 PM, Jεan Sacren wrote:
>> From: David Miller
>> Date: Tue, 19 Jan 2016 14:36:28 -0500
>>>
>>> From: Julia Lawall
>>> Date: Tue, 19 Jan 2016 19:54:20
From: Eric Dumazet
Date: Thu, 21 Jan 2016 08:02:54 -0800
> From: Eric Dumazet
>
> Neal reported crashes with this stack trace :
>
> RIP: 0010:[] tcp_v4_send_ack+0x41/0x20f
> ...
> CR2: 0018 CR3: 00044005c000 CR4: 001427e0
On Fri, 2016-01-22 at 01:49 +0800, Xin Long wrote:
> Previously, before rhashtable, /proc assoc listing was done by
> read-locking the entire hash entry and dumping all assocs at once, so we
> were sure that the assoc wasn't freed because it wouldn't be possible to
> remove it from the hash
From: David Miller
Date: Thu, 21 Jan 2016 10:45:20 -0800
>
> Yes, you will submit to me a patch to remove the unused code.
I should have paraphrased it better:
"I have the patch ready and will submit it when net-next opens again."
101 - 115 of 115 matches
Mail list logo