brctl setportprio fails silently

Bug #988374 reported by ecip
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bridge-utils (Debian)
Fix Released
Unknown
bridge-utils (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Hi, when I issue a brctl setportprio command specifying priorities highen than 63 the command fails silently, thus the priority of the port is not changed:

brctl setportprio BRVAL VALSEV 32768

it gives no output and the priority is not changed. If we analyze the command using strace:

 strace brctl setportprio BRVAL VALSEV 32768
execve("/usr/sbin/brctl", ["brctl", "setportprio", "BRVAL", "VALSEV", "32768"], [/* 17 vars */]) = 0
brk(0) = 0xac6000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fe953afb000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=17295, ...}) = 0
mmap(NULL, 17295, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fe953af6000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\355\1\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1572232, ...}) = 0
mmap(NULL, 3680296, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fe95355b000
mprotect(0x7fe9536d5000, 2093056, PROT_NONE) = 0
mmap(0x7fe9538d4000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x179000) = 0x7fe9538d4000
mmap(0x7fe9538d9000, 18472, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fe9538d9000
close(3) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fe953af5000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fe953af4000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fe953af3000
arch_prctl(ARCH_SET_FS, 0x7fe953af4700) = 0
mprotect(0x7fe9538d4000, 16384, PROT_READ) = 0
mprotect(0x606000, 4096, PROT_READ) = 0
mprotect(0x7fe953afd000, 4096, PROT_READ) = 0
munmap(0x7fe953af6000, 17295) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 3
brk(0) = 0xac6000
brk(0xae7000) = 0xae7000
open("/sys/class/net/VALSEV/brport/priority", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=4096, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fe953afa000
write(4, "32768\n", 6) = -1 ERANGE (Numerical result out of range)
close(4) = 0
munmap(0x7fe953afa000, 4096) = 0
exit_group(0) = ?

The release is Ubuntu 10.04 LTS and bridge-utils is 1.4-5ubuntu2.

Regards.

Eduardo

Revision history for this message
ecip (ecip) wrote :

Hi, I have realized this bug is already filed in Debian as bug number 574363.

Regards,

Eduardo

Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

This bug is marked as fixed in the Debian bug you linked, in version 1.5-1. Ubuntu will have carried this change since Oneiric, in version 1.5-2ubuntu1. Thus this bug is already fixed in the current development release, so I'm marking it as Fix Released.

I don't think that this is a high-impact bug and thus does not warrant fixing in any previous stable release (see https://wiki.ubuntu.com/StableReleaseUpdates#When).

Changed in bridge-utils (Ubuntu):
status: New → Fix Released
importance: Undecided → Low
Changed in bridge-utils (Debian):
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.