From: Alexandru Ardelean
Seems that musl libc's default thread stack size is 80k, which
causes a segfault (stack overflow actually) when trying to add
a bridge (via the "ovs-vsctl add-br" command).
OpenWRT has been switching to musl libc for a few months now.
So far, we've been using OVS with uC
¹ºæJ
Ö³¤õïè
òá;|×0JGO]Öë^ß$½ìtºÜ¶
ônõkÒ&ö rª°Éº_Þðôö×H¹QÜÚ(®Änç¥(²#ËOE2
øÅÄzØH'ê}§qâìïRrÖ$Iö²ÑÚ]Rju×òôF1*í®\uwÐßK¬¥ß÷¦OFÙâòMü
×û!Nü`iå[¬ªïnOA¼Z©>kØɼëÙ3ĸîÈþ *9|
õû[Ä{
wÍ
ó1ÈøçyÈU>öõVðKw§Nx(¥Bkóøß5nã}éSìÖ!þ_yóÊæ(
ûúPç3èá«ne
½Lé\þ
Ncc_Vúïµ»ÝV¡V»àMÌ·öx`Î)ó·!
On Thu, Jan 21, 2016 at 1:11 PM, Russell Bryant wrote:
>
> Multiple logical ports on the same chassis that were connected to the
> same physical network via localnet ports were not able to send packets
> to each other. This was because ovn-controller created a single patch
> port between br-int a
æÙu.\twái|Ë¡'{gçéá(GßÑð¹$[ì$~B#
!Ò¨"$ä(ô¼â(;uç'b0?vJÁè´9«Vx Eï»x#ÃT>S1Û×%
<¯?kZ¿ßÁÉRBCxC9â_ql#ÎsbÀ6:ïJ4W¯¯bT&¡[¨|Ã*:{s²Z¾óùhgb
[èÈ[á(_%¼YF¤®,
<
{ľÍ>4§B2/C<Ömóñ÷
["Ò÷)hy-Ú¹ýãéß´B]·ñGq¯5ÒJ³¥ë¿ÐDÒlúÔÈf¬ÔQÇ|SÃ!¢0Æë«£\à&ã8HYÏd
ëÓ!kKO úü±½4r!(û<
{Éë4®ÉÅo
92cê
I think auto mark is useful, merged the change,
On 18 January 2016 at 14:31, ALeX Wang wrote:
> Marked committed patches as 'Accepted'
> Marked duplicates as 'Not Applicable'
>
> I have a patch that automates the marking above,
>
> https://github.com/yew011/openvswitch.patchwork.mgmt/pull/1
>
>
I went into the "bad key length" in below datapath flow in a test
environment:
recirc_id(0x109),in_port(5),ct_state(-new+est-rel-inv+trk),eth(src=fa:16:3e:00:49:66,dst=fa:16:3e:ca:4a:20),eth_type(0x0800),ipv4(src=
22.22.22.4/255.255.255.252,dst=22.22.23.4,tos=0/0x3,ttl=64,frag=no),
packets:4, byte
Mark Committed as Accepted
==
Mark Dup as Not Applicable
==
On 24 January 2016 at 16:01, wrote:
> 30+ Day Old Patches
> ===
> ID State Date Name
> -- -
> 548008 New201
The message was not delivered due to the following reason(s):
Your message could not be delivered because the destination server was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.
Most likely
On Thu, Jan 21, 2016 at 2:09 PM, Russell Bryant wrote:
> On 01/20/2016 05:59 PM, Ansis Atteka wrote:
>> CentOS, RHEL and Fedora distributions ship with their own Open vSwitch
>> SELinux policy that is too strict and prevents Open vSwitch to work
>> normally out of the box.
>>
>> As a solution, thi
30+ Day Old Patches
===
ID State Date Name
-- -
548008 New2015-11-24 11:19:01 [ovs-dev,v4,2/4] ovn: New flows for DHCP
tranffic
548010 New2015-11-24 11:19:02 [ovs-dev,v4,3/4] ovn: Process dhcp
packet-ins and
On 01/24/2016 08:56 AM, Alexandru Ardelean wrote:
> Seems that musl libc's default thread stack size is 80k, which
> causes a segfault (stack overflow actually) when trying to add
> a bridge (via the "ovs-vsctl add-br" command).
>
> OpenWRT has been switching to musl libc for a few months now.
> S
Seems that musl libc's default thread stack size is 80k, which
causes a segfault (stack overflow actually) when trying to add
a bridge (via the "ovs-vsctl add-br" command).
OpenWRT has been switching to musl libc for a few months now.
So far, we've been using OVS with uClibc, so I did not catch th
On Sun, Jan 24, 2016 at 11:59:57PM +0800, Huanle Han wrote:
> I think a more line "mirrors &= ~ctx->mirrors;" is needed at the end of the
> "while" loop.
> Otherwise, duplicated mirror action may be applied in recursive
> mirror_packet called by output_normal.
Did you arrive at that conclusion fro
Before this commit, emc_processing() copied a netdev_flow_key if there was
no exact-match cache (EMC) hit. This commit eliminates the copy by
constructing the netdev_flow_key in the place it would be copied.
Found by inspection.
Shahbaz (CCed) reports that this reduces the cost of an EMC miss by
Hi, Ben,
I think a more line "mirrors &= ~ctx->mirrors;" is needed at the end of the
"while" loop.
Otherwise, duplicated mirror action may be applied in recursive
mirror_packet called by output_normal.
Here are the test cases:
Test case for the bug I mentioned in previous mail:
1. setup port: v
15 matches
Mail list logo
