Re: NULL pointer dereference bug triggered by netmap

[Vincenzo Maffione]

Yes.

Actually, we would also need one beteween the following two options:
1) Implementing a dummy if_start() for if_loop.c
2) Prevent netmap from using if_loop.

Cheers,
  Vincenzo

2017-07-11 22:05 GMT+02:00 Marius Strobl :

> On Thu, Jul 06, 2017 at 02:19:42PM -0700, Vincenzo Maffione wrote:
> > Sure, can anyone commit this?
>
> The addition of KASSERTs like the below one to if_handoff() and
> if_start()? Sure.
>
> Marius
>
> >
> > Il 5 lug 2017 4:05 AM, "Marius Strobl"  ha scritto:
> >
> > > On Mon, Jul 03, 2017 at 05:08:09PM +0200, Vincenzo Maffione wrote:
> > > > Details here:
> > > >
> > > > https://github.com/luigirizzo/netmap/issues/322
> > > >
> > > > Is it acceptable to commit the proposed patch?
> > >
> > > As suggested by hselasky@, the outliner problem at hand is better
> solved
> > > by a dummy if_start method in order to not hurt the fast-path. Thus, if
> > > anything at all, a KASSERT(ifp->if_start != NULL, "no if_start method")
> > > should be added to if_handoff() and if_start().
> > >
>



-- 
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: mbuf_jumbo_9k & iSCSI failing

[Ryan Stone]

I've just put up a review that fixes mlx4_en to no longer use clusters
larger than PAGE_SIZE in its receive path.  The patch is based off of the
older version of the driver which did the same, but keeps all of the
changes to the driver since then (including support for bus_dma).  The
review can be found here:

https://reviews.freebsd.org/D11560
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: NULL pointer dereference bug triggered by netmap

[Marius Strobl]

On Thu, Jul 06, 2017 at 02:19:42PM -0700, Vincenzo Maffione wrote:
> Sure, can anyone commit this?

The addition of KASSERTs like the below one to if_handoff() and
if_start()? Sure.

Marius

> 
> Il 5 lug 2017 4:05 AM, "Marius Strobl"  ha scritto:
> 
> > On Mon, Jul 03, 2017 at 05:08:09PM +0200, Vincenzo Maffione wrote:
> > > Details here:
> > >
> > > https://github.com/luigirizzo/netmap/issues/322
> > >
> > > Is it acceptable to commit the proposed patch?
> >
> > As suggested by hselasky@, the outliner problem at hand is better solved
> > by a dummy if_start method in order to not hurt the fast-path. Thus, if
> > anything at all, a KASSERT(ifp->if_start != NULL, "no if_start method")
> > should be added to if_handoff() and if_start().
> >
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 41647] ifconfig(8) doesn't accept lladdr along with inet address family

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=41647

Eugene Grosbein  changed:

   What|Removed |Added

 Resolution|--- |Works As Intended
 Status|In Progress |Closed
 CC||eu...@freebsd.org

--- Comment #10 from Eugene Grosbein  ---
ifconfig(8) treats link-level address as distinct address family (and not an
option) long enough to the moment. And we have enough ways to configure lladdr
by means of rc.conf or other scripts in /etc. There is no point to keep this PR
open for another decade without any code supplied.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: memory leaks in 11.0?

[Grzegorz Junka]

On 11/07/2017 13:56, Kajetan Staszkiewicz wrote:

Hello,

I finally upgraded one of many of my routers to 11.0.

Unfortunately after running fine for a month it ran out of memory. "wired"
memory slowly grows up to allocating all memory in system when no more memory
is left for other programs. Things first get swapped and eventually die.

The router runs BIRD which has not much to do, it is for internal networks
only, pf, pfsync (currently disabled via `ifconfig pfsync0 down`), filebeat,
smokeping, ntp, nrpe and custom python cron job for sending data to Graphite.

`vmstat -z` shows constantly increasing allocation of "512" and "UMA Slabs".
Memory allocated for all pf-related things seems fine. I have graphite graps
for every `vmstat -z` and the icrease on "512" grows in similar way as "wired"
memory. "512" has 2 917 392 used objects allocated at this moment, "UMA Slabs"
is 379 006, there is 2636MiB "wired" memory.

How can I debug which part of kernel is responsible for this? I run GENERIC
kernel with ixl driver 1.7.11 from Intel, as the one in GENERIC had issues
detecting links on my x710 NIC.

I ask here, because it is a router, mostly being busy with his network cards,
routing and pf. Please direct me to a better group if you can.

I can crash this system if needed and dump memory (I hope that is possible on
GENERIC) for analysis.



That's interesting. Are those ARM-based routers or x86/amd64?

This my server:

Mem: 48M Active, 190M Inact, 28G Wired, 3075M Free
ARC: 26G Total, 6118M MFU, 18G MRU, 32K Anon, 184M Header, 1294M Other
Swap: 48G Total, 20M Used, 48G Free

% uptime
 5:12PM  up 93 days,  1:58, 1 users, load averages: 0.23, 0.20, 0.16

 uname -r
11.0-RELEASE-p8

vmstat -z

512:512,  0,2921,1703,505278087, 0,   0
UMA Slabs:   80,  0,  551576,   51574, 1716599, 0,   0

It looks like the memory allocations for '512' constantly go up but I 
didn't check if they go down again at some point. However, 'UMA Slabs' 
seems to be not changing much. I believe the Wired memory as shown in 
top includes ZFS which the server is installed on? If that's the case 
then it's probably ZFS filling up the free memory with ZFS cache?


Grzegorz
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Support for X553 (Denverton) Ethernet devices

[Cassiano Peixoto]

Hi Jeb,

Thank you. Keep me posted to try as soon as it's available.

On Tue, Jul 11, 2017 at 1:42 PM, Cramer, Jeb J 
wrote:

> Hi Cassiano,
>
> We’ve added support to HEAD and are creating the patch to apply to
> 11-STABLE as this moment.  It should be posted today or maybe tomorrow at
> the latest.
>
> Thanks,
> -Jeb
>
> From: Cassiano Peixoto [mailto:peixotocassi...@gmail.com]
> Sent: Tuesday, July 11, 2017 6:52 AM
> To: freebsd-sta...@freebsd.org; freebsd-net@freebsd.org
> Cc: e...@freebsd.org; Cramer, Jeb J ; Pieper,
> Jeffrey E 
> Subject: Support for X553 (Denverton) Ethernet devices
>
> Hi guys,
>
> I've been playing with Denverton, but I realized that ethernet devices
> wasn't recognized.
>
> I found this commit here enabling X553 support on 10-STABLE:
> http://freshbsd.org/commit/freebsd/r315333
> https://reviews.freebsd.org/D9310
>
> I tested on 10-STABLE and worked fined. But on 11-STABLE it didn't find
> the ethernet interfaces.
>
> Seems IFLIB support is needed, anyway I enabled support in kernel but
> nothing has changed.
>
> Am I missing something here or support to X553 wasn't added to 11-STABLE?
>
> Thanks.
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

RE: Support for X553 (Denverton) Ethernet devices

[Cramer, Jeb J]

Hi Cassiano,

We’ve added support to HEAD and are creating the patch to apply to 11-STABLE as 
this moment.  It should be posted today or maybe tomorrow at the latest.

Thanks,
-Jeb

From: Cassiano Peixoto [mailto:peixotocassi...@gmail.com]
Sent: Tuesday, July 11, 2017 6:52 AM
To: freebsd-sta...@freebsd.org; freebsd-net@freebsd.org
Cc: e...@freebsd.org; Cramer, Jeb J ; Pieper, Jeffrey E 

Subject: Support for X553 (Denverton) Ethernet devices

Hi guys,

I've been playing with Denverton, but I realized that ethernet devices wasn't 
recognized.

I found this commit here enabling X553 support on 10-STABLE:
http://freshbsd.org/commit/freebsd/r315333
https://reviews.freebsd.org/D9310

I tested on 10-STABLE and worked fined. But on 11-STABLE it didn't find the 
ethernet interfaces.

Seems IFLIB support is needed, anyway I enabled support in kernel but nothing 
has changed.

Am I missing something here or support to X553 wasn't added to 11-STABLE?

Thanks.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: memory leaks in 11.0?

[Mike Tancsa]

On 7/11/2017 9:56 AM, Kajetan Staszkiewicz wrote:
> Hello,
> 
> I finally upgraded one of many of my routers to 11.0.

Hi,
11.0 as in 11.0R or 11-STABLE ? I have a number of RELENG_11 boxes
running (r316678 to r319309) as routers (with frr, not bird) that are
quite stable and no memory leaks (that I can see anyways).

---Mike

-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: memory leaks in 11.0?

[Konstantin Belousov]

On Tue, Jul 11, 2017 at 03:56:04PM +0200, Kajetan Staszkiewicz wrote:
> `vmstat -z` shows constantly increasing allocation of "512" and "UMA
> Slabs". Memory allocated for all pf-related things seems fine. I have
> graphite graps for every `vmstat -z` and the icrease on "512" grows
> in similar way as "wired" memory. "512" has 2 917 392 used objects
> allocated at this moment, "UMA Slabs" is 379 006, there is 2636MiB
> "wired" memory.

UMA zone 512 is used for kernel mallocs of size less than 512 (and greater
than 256).  You can see mallocs types usage with vmstat -m.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: memory leaks in 11.0?

[Hans Petter Selasky]

On 07/11/17 15:56, Kajetan Staszkiewicz wrote:

Hello,

I finally upgraded one of many of my routers to 11.0.

Unfortunately after running fine for a month it ran out of memory. "wired"
memory slowly grows up to allocating all memory in system when no more memory
is left for other programs. Things first get swapped and eventually die.

The router runs BIRD which has not much to do, it is for internal networks
only, pf, pfsync (currently disabled via `ifconfig pfsync0 down`), filebeat,
smokeping, ntp, nrpe and custom python cron job for sending data to Graphite.

`vmstat -z` shows constantly increasing allocation of "512" and "UMA Slabs".
Memory allocated for all pf-related things seems fine. I have graphite graps
for every `vmstat -z` and the icrease on "512" grows in similar way as "wired"
memory. "512" has 2 917 392 used objects allocated at this moment, "UMA Slabs"
is 379 006, there is 2636MiB "wired" memory.

How can I debug which part of kernel is responsible for this? I run GENERIC
kernel with ixl driver 1.7.11 from Intel, as the one in GENERIC had issues
detecting links on my x710 NIC.

I ask here, because it is a router, mostly being busy with his network cards,
routing and pf. Please direct me to a better group if you can.

I can crash this system if needed and dump memory (I hope that is possible on
GENERIC) for analysis.



Hi,

Last time I traced memory leaks I used some dtrace scripts to trace all 
allocations and frees and then analayzed the result using a perl script 
which I found on the internet.


--HPS
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 100519] [netisr] suggestion to fix suboptimal network polling

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=100519

Josh Paetzel  changed:

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |Overcome By Events
 CC||jpaet...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

memory leaks in 11.0?

[Kajetan Staszkiewicz]

Hello,

I finally upgraded one of many of my routers to 11.0.

Unfortunately after running fine for a month it ran out of memory. "wired" 
memory slowly grows up to allocating all memory in system when no more memory 
is left for other programs. Things first get swapped and eventually die.

The router runs BIRD which has not much to do, it is for internal networks 
only, pf, pfsync (currently disabled via `ifconfig pfsync0 down`), filebeat, 
smokeping, ntp, nrpe and custom python cron job for sending data to Graphite.

`vmstat -z` shows constantly increasing allocation of "512" and "UMA Slabs". 
Memory allocated for all pf-related things seems fine. I have graphite graps 
for every `vmstat -z` and the icrease on "512" grows in similar way as "wired" 
memory. "512" has 2 917 392 used objects allocated at this moment, "UMA Slabs" 
is 379 006, there is 2636MiB "wired" memory.

How can I debug which part of kernel is responsible for this? I run GENERIC 
kernel with ixl driver 1.7.11 from Intel, as the one in GENERIC had issues 
detecting links on my x710 NIC.

I ask here, because it is a router, mostly being busy with his network cards, 
routing and pf. Please direct me to a better group if you can.

I can crash this system if needed and dump memory (I hope that is possible on 
GENERIC) for analysis.

-- 
| pozdrawiam / greetings | powered by Debian, FreeBSD and CentOS |
|  Kajetan Staszkiewicz  | jabber,email: vegeta()tuxpowered net  |
|Vegeta  | www: http://vegeta.tuxpowered.net |
`^---'

signature.asc
Description: This is a digitally signed message part.

Support for X553 (Denverton) Ethernet devices

[Cassiano Peixoto]

Hi guys,

I've been playing with Denverton, but I realized that ethernet devices
wasn't recognized.

I found this commit here enabling X553 support on 10-STABLE:
http://freshbsd.org/commit/freebsd/r315333
https://reviews.freebsd.org/D9310

I tested on 10-STABLE and worked fined. But on 11-STABLE it didn't find the
ethernet interfaces.

Seems IFLIB support is needed, anyway I enabled support in kernel but
nothing has changed.

Am I missing something here or support to X553 wasn't added to 11-STABLE?

Thanks.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 102035] [plip] plip networking disables parallel port printing

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=102035

Josh Paetzel  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 CC||jpaet...@freebsd.org
 Status|In Progress |Closed

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 220611] Fatal trap 12: page fault while in kernel mode (ip6_forward -> log)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220611

Kristof Provost  changed:

   What|Removed |Added

   Assignee|freebsd-net@FreeBSD.org |k...@freebsd.org
 CC||k...@freebsd.org

--- Comment #1 from Kristof Provost  ---
Can you describe the setup of the machine? (Is it a gateway? Where does it
route to? ...)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"