search for: siocbraddif

...OQUERY 0x8994 /* rtn info about bond state */ #define SIOCBONDCHANGEACTIVE 0x8995 /* update to a new active slave */ +/* bridge calls */ +#define SIOCBRADDBR 0x89a0 /* create new bridge device */ +#define SIOCBRDELBR 0x89a1 /* remove bridge device */ +#define SIOCBRADDIF 0x89a2 /* add interface to bridge */ +#define SIOCBRDELIF 0x89a3 /* remove interface from bridge */ + /* Device private ioctl calls */ /* diff -Nru a/net/bridge/br_ioctl.c b/net/bridge/br_ioctl.c --- a/net/bridge/br_ioctl.c 2004-05-20 14:46:10 -07:00 +++ b/net/bridge/br_ioctl.c 2004-05-2...

1) Example code: old libc headers don't have SIOCBRADDIF, and old zlibs don't have gzdirect() -- it's a sanity check anyway. 2) Some people don't build in their source directories, so .config isn't there (thanks to Tony Breeds <tony@bakeyournoodle.com>). 3) Point out that guest and host kernel are usually the same. 4) Set the...

1) Example code: old libc headers don't have SIOCBRADDIF, and old zlibs don't have gzdirect() -- it's a sanity check anyway. 2) Some people don't build in their source directories, so .config isn't there (thanks to Tony Breeds <tony@bakeyournoodle.com>). 3) Point out that guest and host kernel are usually the same. 4) Set the...

In the bug reported by Syzbot, certain bridge devices would have a leaked reference created by race conditions in dev_ioctl, specifically, under SIOCBRADDIF or SIOCBRDELIF operations. The reference leak would be shown in the periodic unregister_netdevice call, which throws a warning and cause Syzbot to report a crash. Upon inspection of the logic in dev_ioctl, it seems the reference was introduced to ensure proper access to the bridge device after rtnl...

...model name : AMD Duron(tm) procu{s{ Module Size Used by tun 7680 0 lg 54600 0 just started playing with lguest - patching, compiling and booting the host-kernel goes ok - compiling lguest is ok as well after hardcodeing SIOCBRADDIF - but on the first boot attempt of a guest linux I get: root@darkstar:/usr/src/linux-2.6.21# Documentation/lguest/lguest 64m vmlinux --tunnet=192.168.2.1 --block=../root_fs root=/dev/lgba lguest: unhandled trap 6 at 0xc0117903 (0x0) this should be in "c01178db T reserve_top_address" -...

...model name : AMD Duron(tm) procu{s{ Module Size Used by tun 7680 0 lg 54600 0 just started playing with lguest - patching, compiling and booting the host-kernel goes ok - compiling lguest is ok as well after hardcodeing SIOCBRADDIF - but on the first boot attempt of a guest linux I get: root@darkstar:/usr/src/linux-2.6.21# Documentation/lguest/lguest 64m vmlinux --tunnet=192.168.2.1 --block=../root_fs root=/dev/lgba lguest: unhandled trap 6 at 0xc0117903 (0x0) this should be in "c01178db T reserve_top_address" -...

Thanks to everyone who sent bug reports. I've backported all the fixes and tweaks. Changes since last 2.6.21 release (254): 1) Method for building launcher with out-of-tree build (patch from Tony Breeds) 2) SIOCBRADDIF definition for older libc headers (report by Wang Cong) 3) Warning suppression for put_user/get_user (Wang Cong report again) 4) Numerous typo fixes (Jeremy Fitzhardinge's eyes) 5) Rework of networking documentation (Glauber de Oliveira Costa's whining) 6) Block documentation includes new l...

Thanks to everyone who sent bug reports. I've backported all the fixes and tweaks. Changes since last 2.6.21 release (254): 1) Method for building launcher with out-of-tree build (patch from Tony Breeds) 2) SIOCBRADDIF definition for older libc headers (report by Wang Cong) 3) Warning suppression for put_user/get_user (Wang Cong report again) 4) Numerous typo fixes (Jeremy Fitzhardinge's eyes) 5) Rework of networking documentation (Glauber de Oliveira Costa's whining) 6) Block documentation includes new l...

Hi Ziqi, On 8/19/23 11:10, Ziqi Zhao wrote: > In the bug reported by Syzbot, certain bridge devices would have a > leaked reference created by race conditions in dev_ioctl, specifically, > under SIOCBRADDIF or SIOCBRDELIF operations. The reference leak would How would it leak a reference, could you elaborate? The reference is always taken and always released after the call. > be shown in the periodic unregister_netdevice call, which throws a > warning and cause Syzbot to report a crash. Upon i...

...f uint32_t u32; +typedef uint16_t u16; +typedef uint8_t u8; +#include "../../include/linux/lguest_launcher.h" +#include "../../include/asm-i386/e820.h" + +#define PAGE_PRESENT 0x7 /* Present, RW, Execute */ +#define NET_PEERNUM 1 +#define BRIDGE_PFX "bridge:" +#ifndef SIOCBRADDIF +#define SIOCBRADDIF 0x89a2 /* add interface to bridge */ +#endif + +static bool verbose; +#define verbose(args...) \ + do { if (verbose) printf(args); } while(0) + +struct device_list +{ + fd_set infds; + int max_infd; + + struct device *dev; + struct device **lastdev; +}; + +struct device +...

...f uint32_t u32; +typedef uint16_t u16; +typedef uint8_t u8; +#include "../../include/linux/lguest_launcher.h" +#include "../../include/asm-i386/e820.h" + +#define PAGE_PRESENT 0x7 /* Present, RW, Execute */ +#define NET_PEERNUM 1 +#define BRIDGE_PFX "bridge:" +#ifndef SIOCBRADDIF +#define SIOCBRADDIF 0x89a2 /* add interface to bridge */ +#endif + +static bool verbose; +#define verbose(args...) \ + do { if (verbose) printf(args); } while(0) + +struct device_list +{ + fd_set infds; + int max_infd; + + struct device *dev; + struct device **lastdev; +}; + +struct device +...

Hello, syzbot found the following issue on: HEAD commit: 67faabbde36b selftests/bpf: Add missing prototypes for sev.. git tree: bpf-next console+strace: https://syzkaller.appspot.com/x/log.txt?x=1381363b280000 kernel config: https://syzkaller.appspot.com/x/.config?x=5335204dcdecfda dashboard link: https://syzkaller.appspot.com/bug?extid=881d65229ca4f9ae8c84 compiler: gcc (Debian

...fidx; + struct ifreq ifr; + + if (!*br_name) + errx(1, "must specify bridge name"); + + ifidx = if_nametoindex(if_name); + if (!ifidx) + errx(1, "interface %s does not exist!\n", if_name); + + strncpy(ifr.ifr_name, br_name, IFNAMSIZ); + ifr.ifr_ifindex = ifidx; + r = ioctl(fd, SIOCBRADDIF, &ifr); + if (r != -1) + return; + + switch (errno) { + case ENODEV: + errx(1, "bridge %s does not exist!\n", br_name); + case EBUSY: + errx(1, "device %s is already a member of a bridge; " + "can't enslave it to bridge %s.\n", if_name, br_name); + case EL...

...fidx; + struct ifreq ifr; + + if (!*br_name) + errx(1, "must specify bridge name"); + + ifidx = if_nametoindex(if_name); + if (!ifidx) + errx(1, "interface %s does not exist!\n", if_name); + + strncpy(ifr.ifr_name, br_name, IFNAMSIZ); + ifr.ifr_ifindex = ifidx; + r = ioctl(fd, SIOCBRADDIF, &ifr); + if (r != -1) + return; + + switch (errno) { + case ENODEV: + errx(1, "bridge %s does not exist!\n", br_name); + case EBUSY: + errx(1, "device %s is already a member of a bridge; " + "can't enslave it to bridge %s.\n", if_name, br_name); + case EL...

Hi all, These are the patches I'm planning to submit for 2.6.24. Comments gratefully accepted. Along with the usual cleanups and improvements are Jes' de-i386-ification patches, and a new "virtio" mechanism designed to be shared with KVM (and hopefully other hypervisors). Cheers, Rusty. Documentation/lguest/Makefile | 30 Documentation/lguest/lguest.c

Hi all, These are the patches I'm planning to submit for 2.6.24. Comments gratefully accepted. Along with the usual cleanups and improvements are Jes' de-i386-ification patches, and a new "virtio" mechanism designed to be shared with KVM (and hopefully other hypervisors). Cheers, Rusty. Documentation/lguest/Makefile | 30 Documentation/lguest/lguest.c