search for: 4b0d

Displaying 11 results from an estimated 11 matches for "4b0d".

Did you mean: 4b06
2023 Aug 16
1
[Bridge] [PATCH net-next v2] netfilter: ebtables: replace zero-length array members
..., GONG, Ruiqi wrote: > From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> > > As suggested by Kees[1], replace the old-style 0-element array members > of multiple structs in ebtables.h with modern C99 flexible array. > > [1]: https://lore.kernel.org/all/5E8E0F9C-EE3F-4B0D-B827-DC47397E2A4A at kernel.org/ > > Link: https://github.com/KSPP/linux/issues/21 > Signed-off-by: GONG, Ruiqi <gongruiqi1 at huawei.com> > Reviewed-by: Kees Cook <keescook at chromium.org> > --- > > v2: designate to net-next; cc more netdev maintainers It's...
2023 Aug 16
1
[Bridge] [PATCH net-next v2] netfilter: ebtables: replace zero-length array members
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> As suggested by Kees[1], replace the old-style 0-element array members of multiple structs in ebtables.h with modern C99 flexible array. [1]: https://lore.kernel.org/all/5E8E0F9C-EE3F-4B0D-B827-DC47397E2A4A at kernel.org/ Link: https://github.com/KSPP/linux/issues/21 Signed-off-by: GONG, Ruiqi <gongruiqi1 at huawei.com> Reviewed-by: Kees Cook <keescook at chromium.org> --- v2: designate to net-next; cc more netdev maintainers include/uapi/linux/netfilter_bridge/ebtabl...
2017 Jun 21
2
Gluster failure due to "0-management: Lock not released for <volumename>"
...t's not "released" due to the whole setup losing power all of a sudden. I've tried restarting all the nodes, restarting glusterfs-server etc. I'm out of ideas. Thanks in advance! Victor Volume Name: teravolume Type: Distributed-Replicate Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 Status: Started Snapshot Count: 0 Number of Bricks: 3 x 2 = 6 Transport-type: tcp Bricks: Brick1: gfsnode1:/media/brick1 Brick2: gfsnode2:/media/brick1 Brick3: gfsnode3:/media/brick1 Brick4: gfsnode1:/media/brick2 Brick5: gfsnode2:/media/brick2 Brick6: gfsnode3:/media/b...
2017 Jun 22
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...all > of a sudden. I?ve tried restarting all the nodes, restarting > glusterfs-server etc. I?m out of ideas. > > > > Thanks in advance! > > > > Victor > > > > Volume Name: teravolume > > Type: Distributed-Replicate > > Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 > > Status: Started > > Snapshot Count: 0 > > Number of Bricks: 3 x 2 = 6 > > Transport-type: tcp > > Bricks: > > Brick1: gfsnode1:/media/brick1 > > Brick2: gfsnode2:/media/brick1 > > Brick3: gfsnode3:/media/brick1 > > Brick4:...
2017 Jun 27
2
Gluster failure due to "0-management: Lock not released for <volumename>"
...ing >> glusterfs-server etc. I?m out of ideas. >> >> >> >> Thanks in advance! >> >> >> >> Victor >> >> >> >> Volume Name: teravolume >> >> Type: Distributed-Replicate >> >> Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 >> >> Status: Started >> >> Snapshot Count: 0 >> >> Number of Bricks: 3 x 2 = 6 >> >> Transport-type: tcp >> >> Bricks: >> >> Brick1: gfsnode1:/media/brick1 >> >> Brick2: gfsnode2:/media/brick1 &gt...
2017 Jun 29
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...g it?s this ?lock? that?s not ?released? due to the whole setup losing power all of a sudden. I?ve tried restarting all the nodes, restarting glusterfs-server etc. I?m out of ideas. Thanks in advance! Victor Volume Name: teravolume Type: Distributed-Replicate Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 Status: Started Snapshot Count: 0 Number of Bricks: 3 x 2 = 6 Transport-type: tcp Bricks: Brick1: gfsnode1:/media/brick1 Brick2: gfsnode2:/media/brick1 Brick3: gfsnode3:/media/brick1 Brick4: gfsnode1:/media/brick2 Brick5: gfsnode2:/media/brick2 Brick6: gfsnode3:/media/b...
2017 Jun 30
3
Gluster failure due to "0-management: Lock not released for <volumename>"
...all > of a sudden. I?ve tried restarting all the nodes, restarting > glusterfs-server etc. I?m out of ideas. > > > > Thanks in advance! > > > > Victor > > > > Volume Name: teravolume > > Type: Distributed-Replicate > > Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 > > Status: Started > > Snapshot Count: 0 > > Number of Bricks: 3 x 2 = 6 > > Transport-type: tcp > > Bricks: > > Brick1: gfsnode1:/media/brick1 > > Brick2: gfsnode2:/media/brick1 > > Brick3: gfsnode3:/media/brick1 > > Brick4:...
2017 Jul 04
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...g it?s this ?lock? that?s not ?released? due to the whole setup losing power all of a sudden. I?ve tried restarting all the nodes, restarting glusterfs-server etc. I?m out of ideas. Thanks in advance! Victor Volume Name: teravolume Type: Distributed-Replicate Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 Status: Started Snapshot Count: 0 Number of Bricks: 3 x 2 = 6 Transport-type: tcp Bricks: Brick1: gfsnode1:/media/brick1 Brick2: gfsnode2:/media/brick1 Brick3: gfsnode3:/media/brick1 Brick4: gfsnode1:/media/brick2 Brick5: gfsnode2:/media/brick2 Brick6: gfsnode3:/media/b...
2017 Jul 05
1
Gluster failure due to "0-management: Lock not released for <volumename>"
...all > of a sudden. I?ve tried restarting all the nodes, restarting > glusterfs-server etc. I?m out of ideas. > > > > Thanks in advance! > > > > Victor > > > > Volume Name: teravolume > > Type: Distributed-Replicate > > Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 > > Status: Started > > Snapshot Count: 0 > > Number of Bricks: 3 x 2 = 6 > > Transport-type: tcp > > Bricks: > > Brick1: gfsnode1:/media/brick1 > > Brick2: gfsnode2:/media/brick1 > > Brick3: gfsnode3:/media/brick1 > > Brick4:...
2017 Jul 04
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...g it?s this ?lock? that?s not ?released? due to the whole setup losing power all of a sudden. I?ve tried restarting all the nodes, restarting glusterfs-server etc. I?m out of ideas. Thanks in advance! Victor Volume Name: teravolume Type: Distributed-Replicate Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 Status: Started Snapshot Count: 0 Number of Bricks: 3 x 2 = 6 Transport-type: tcp Bricks: Brick1: gfsnode1:/media/brick1 Brick2: gfsnode2:/media/brick1 Brick3: gfsnode3:/media/brick1 Brick4: gfsnode1:/media/brick2 Brick5: gfsnode2:/media/brick2 Brick6: gfsnode3:/media/b...
2016 Nov 21
2
Winbind traffic not encrypted
...8847 331e aca1 829c 5829 dabf .{G..G3.....X).. 0x05f0: e13a d216 dc00 f5d5 4adf ecdf 8aab c6c2 .:......J....... 0x0600: 0c7e de3b d3f3 d16d 80a2 79c8 5a91 c52c .~.;...m..y.Z.., 0x0610: e7bb eb30 1343 599b f4f9 affb 8a89 71e6 ...0.CY.......q. 0x0620: c351 80db 869d 2eda 603e 4b0d 6b25 6151 .Q......`>K.k%aQ 0x0630: 703a c8c3 d7a7 54df 431d 5e3a b91e ea43 p:....T.C.^:...C 0x0640: c5fd 294f aa32 8fab 355c 77fc cf8e 9e4a ..)O.2..5\w....J 0x0650: 2db7 91f9 2cc5 a93b c5d7 267e adfe 9615 -...,..;..&~.... 0x0660: 1efc ceb3 38e7 ca78 8759 3459 59d8 537...