Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi, > Once a version uploaded to sid, migrates to testing, it can be > prepared for stable-backports based on that. > > So what will need to happen here: upload of 4.19.13-2 to unstable > (actually possibly only >= 4.19.14-1 if we do not have pressure to > upload 4.19.13-2), then wait it migrates

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi Ralf, On Fri, Jan 04, 2019 at 11:42:26AM +0100, Ralf Jung wrote: > Hi, > > > On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote: > >> Package: linux-image-4.18.0-0.bpo.3-amd64 > >> Version: 4.18.20-2~bpo9+1 > >> Severity: normal > >> Tags: upstream > >> > >> Dear Maintainer, > >> > >> I

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi, > On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote: >> Package: linux-image-4.18.0-0.bpo.3-amd64 >> Version: 4.18.20-2~bpo9+1 >> Severity: normal >> Tags: upstream >> >> Dear Maintainer, >> >> I reported an upstream bug at >>

Processed: Re: Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Processing control commands: > tags -1 + fixed-upstream pending patch Bug #918103 [src:linux] ipv6: Consider sk_bound_dev_if when binding a socket to an address Added tag(s) pending and patch. -- 918103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918103 Debian Bug Tracking System Contact

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Control: tags -1 + fixed-upstream pending patch Hi Ralf, On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote: > Package: linux-image-4.18.0-0.bpo.3-amd64 > Version: 4.18.20-2~bpo9+1 > Severity: normal > Tags: upstream > > Dear Maintainer, > > I reported an upstream bug at >

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Package: linux-image-4.18.0-0.bpo.3-amd64 Version: 4.18.20-2~bpo9+1 Severity: normal Tags: upstream Dear Maintainer, I reported an upstream bug at that got a patch submitted with .