bridge-utils: version 1.0.4 needs 2.6 kernel

[Debian Bug Importer]

Automatically imported from Debian bug report #271144 http://bugs.debian.org/271144

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #271144 http://bugs.debian.org/271144

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 11 Sep 2004 16:47:51 +0200
From: <email address hidden> (Geert Stappers)
To: <email address hidden>
Subject: bridge-utils: version 1.0.4 needs 2.6 kernel

--WVXkb2QE2eH0aWe4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Package: bridge-utils
Version: 1.0.4
Severity: grave
Justification: package is unusable on 2.4 kernel systems

Hello,

AFAICT needs bridge-utils 1.0.4 for Debian a 2.6 kernel.
In bridge-utils_1.0.4-1.diff.gz is debian/include/linux/sockios.h
which defines SIOCBRADDBR, but that ioctl is _not_ 2.4 kernels.

For details visit http://lists.osdl.org/pipermail/bridge/2004-September/000641.html

Cheers
Geert Stappers

--WVXkb2QE2eH0aWe4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBQxAWOSINbgwa/7sRAuQpAJ93yDUvr75OUzv7jiuJ0+dIDnkgtQCgmZPd
P2z6F9hX6SHHhVMD0Y57AmQ=
=rJ+U
-----END PGP SIGNATURE-----

--WVXkb2QE2eH0aWe4--

[Geert Stappers (stappers)]

Hello,

Here an update.

AFAICT it is a problem that needs fixing upstream.

Simply remove the definition of SIOCBRADDBR
from debian/include/linux/sockios.h was not enough
to get brctl 1.0.4 working.

Cheers
Geert Stappers

[Matt Zimmerman (mdz)]

We only ship kernel 2.6

[Santiago Garcia Mantinan (manty)]

> AFAICT needs bridge-utils 1.0.4 for Debian a 2.6 kernel.
> In bridge-utils_1.0.4-1.diff.gz is debian/include/linux/sockios.h
> which defines SIOCBRADDBR, but that ioctl is _not_ 2.4 kernels.

I know that, and upstream knows that, however, it works ok in all arches
except for sparc64, this bug has been opened before (see
http://bugs.debian.org/263375 to follow previous discusion) and I wanted
upstream to fix this behaviour in sparc64, but it seems that upstream
doesn't want to fix it, as the previous bugreporter says on the previous
discusion, so, he closed the bug.

However I still think we should do something about this, either we add a
patch for sparc64 (may be ugly, but it is better for it to work being ugly
than not to work) or add a note explaining what happens for sparc64, can you
provide a patch for this problem on sparc64?

> For details visit http://lists.osdl.org/pipermail/bridge/2004-September/000641.html

Let's see if upstream replies to you.

Regards...
--
Manty/BestiaTester -> http://manty.net

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 11 Sep 2004 21:02:05 +0200
From: <email address hidden> (Geert Stappers)
To: <email address hidden>
Subject: could be a upstream issue

--v15hXiddb3kq3Bam
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hello,

Here an update.

AFAICT it is a problem that needs fixing upstream.

Simply remove the definition of SIOCBRADDBR
from debian/include/linux/sockios.h was not enough
to get brctl 1.0.4 working.

Cheers
Geert Stappers

--v15hXiddb3kq3Bam
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBQ0utOSINbgwa/7sRAjpvAJ93O9Ixf9nyaYiRwtuQ6F94ZA7KgQCgu8mY
YTICdZw4hB8EKEVk7JDdd60=
=TVxW
-----END PGP SIGNATURE-----

--v15hXiddb3kq3Bam--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 11 Sep 2004 21:25:06 +0200
From: Santiago Garcia Mantinan <email address hidden>
To: Geert Stappers <email address hidden>, <email address hidden>
Subject: Re: Bug#271144: bridge-utils: version 1.0.4 needs 2.6 kernel

> AFAICT needs bridge-utils 1.0.4 for Debian a 2.6 kernel.
> In bridge-utils_1.0.4-1.diff.gz is debian/include/linux/sockios.h
> which defines SIOCBRADDBR, but that ioctl is _not_ 2.4 kernels.

I know that, and upstream knows that, however, it works ok in all arches
except for sparc64, this bug has been opened before (see
http://bugs.debian.org/263375 to follow previous discusion) and I wanted
upstream to fix this behaviour in sparc64, but it seems that upstream
doesn't want to fix it, as the previous bugreporter says on the previous
discusion, so, he closed the bug.

However I still think we should do something about this, either we add a
patch for sparc64 (may be ugly, but it is better for it to work being ugly
than not to work) or add a note explaining what happens for sparc64, can you
provide a patch for this problem on sparc64?

> For details visit http://lists.osdl.org/pipermail/bridge/2004-September/000641.html

Let's see if upstream replies to you.

Regards...
--
Manty/BestiaTester -> http://manty.net

[Geert Stappers (stappers)]

severity 271144 normal
thanks mate!

No reason to prevent brigde-utils going in the next Debian
(sarge will ship with 2.6 kernels)

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 12 Sep 2004 14:34:35 +0200
From: <email address hidden> (Geert Stappers)
To: <email address hidden>
Subject: allow release (lowering severity)

severity 271144 normal
thanks mate!

No reason to prevent brigde-utils going in the next Debian
(sarge will ship with 2.6 kernels)

[Geert Stappers (stappers)]

From the upstream mailinglist:
| On Mon, Sep 13, 2004 at 09:28:59AM -0700, Stephen Hemminger wrote:
| > On Sun, 12 Sep 2004 17:19:52 +0200
| > <email address hidden> (Geert Stappers) wrote:
| > > > > > My questions are:
| > > > > >
| > > > > > * Are there succesfull reported sparc64 systems doing bridging?
| > > sparc64 seems indeed be some what special on the bridging aspect ...
| > >
| > > > > > * What should I do to get that sparc64 acting as a bridge?
| > > > > A recompile with gcc-2.95 did not show improvement.
| > > > AFAICT it is brctl 1.0.4 that needs a 2.6 kernel.
| > >
| > > Installing kernel 2.6.8 allowed me to do bridging on a sparc64
| >
| > Yes, the cross 32/64 bit environment is not supported on 2.4.
| > In order to get size independence it meant changing the API to use sysfs which
| > is not available on 2.4

For non sparc64 users there are compile options in libbrigde/libbridge_if.c
like this

 #ifdef SIOCBRADDBR
        ret = ioctl(br_socket_fd, SIOCBRADDBR, brname);
        if (ret < 0)
 #endif

As the Debian version is compiled where that 2.6 definition is used,
it will not run on none 2.6 kernels.

I suggest to mark this bugreport with WONTFIX

Cheers
Geert Stappers

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 14 Sep 2004 13:38:26 +0200
From: <email address hidden> (Geert Stappers)
To: <email address hidden>, <email address hidden>
Subject: epiloog bridge-utils 1.0.4 needs 2.6 kernel

--P9SDCAjI7+EA+Yxm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

=46rom the upstream mailinglist:
| On Mon, Sep 13, 2004 at 09:28:59AM -0700, Stephen Hemminger wrote:
| > On Sun, 12 Sep 2004 17:19:52 +0200
| > <email address hidden> (Geert Stappers) wrote:
| > > > > > My questions are:
| > > > > >=20
| > > > > > * Are there succesfull reported sparc64 systems doing bridging?
| > > sparc64 seems indeed be some what special on the bridging aspect ...
| > >=20
| > > > > > * What should I do to get that sparc64 acting as a bridge?
| > > > > A recompile with gcc-2.95 did not show improvement.
| > > > AFAICT it is brctl 1.0.4 that needs a 2.6 kernel.
| > >=20
| > > Installing kernel 2.6.8 allowed me to do bridging on a sparc64
| >=20
| > Yes, the cross 32/64 bit environment is not supported on 2.4.
| > In order to get size independence it meant changing the API to use sysf=
s which
| > is not available on 2.4

For non sparc64 users there are compile options in libbrigde/libbridge_if.c
like this

 #ifdef SIOCBRADDBR
        ret =3D ioctl(br_socket_fd, SIOCBRADDBR, brname);
        if (ret < 0)
 #endif

As the Debian version is compiled where that 2.6 definition is used,
it will not run on none 2.6 kernels.

I suggest to mark this bugreport with WONTFIX

Cheers
Geert Stappers

--P9SDCAjI7+EA+Yxm
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBRtgyOSINbgwa/7sRAhnCAJ0fVdhHpddhq096H+GcVY6Jwky6sgCdFVCB
aqsVb1QHoO6fCgkuKnOzwFE=
=vQir
-----END PGP SIGNATURE-----

--P9SDCAjI7+EA+Yxm--

[Santiago Garcia Mantinan (manty)]

tags 271144 wontfix
stop

We'll keep this bug opened so that people knows what's up with this problem
and we don't get yet another bug report of the same issue.

If somebody comes with a solution to it that maybe hasn't been considered
till now, we still can see if we accept it and fix this :-)

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 15 Sep 2004 18:16:07 +0200
From: Santiago Garcia Mantinan <email address hidden>
To: <email address hidden>
Subject: tag wontfix

tags 271144 wontfix
stop

We'll keep this bug opened so that people knows what's up with this problem
and we don't get yet another bug report of the same issue.

If somebody comes with a solution to it that maybe hasn't been considered
till now, we still can see if we accept it and fix this :-)