netdev - Re: [PATCH] ss: Fix wrong filter behaviour

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150430072655.GA689@angus-think.wlc.globallogic.com>
Date:	Thu, 30 Apr 2015 10:26:55 +0300
From:	Vadim Kochan <vadim4j@...il.com>
To:	Mihai Moldovan <ionic@...ic.de>
Cc:	Vadim Kochan <vadim4j@...il.com>, netdev@...r.kernel.org
Subject: Re: [PATCH] ss: Fix wrong filter behaviour

On Wed, Apr 29, 2015 at 11:22:13PM +0200, Mihai Moldovan wrote:
> On 28.04.2015 03:37 PM, Vadim Kochan wrote:
> > On Tue, Apr 28, 2015 at 04:16:48PM +0300, Vadim Kochan wrote:
> >> From: Vadim Kochan <vadim4j@...il.com>
> >>
> >> Fixed applying family & socket type filters.
> >> It was not possible to select UDP & UNIX sockets together.
> >>
> >> Now selected families are ORed.
> >>
> >> The problem was that filters were combined by AND.
> >>
> >> Signed-off-by: Vadim Kochan <vadim4j@...il.com>
> >> Reported-By: Mihai Moldovan <ionic@...ic.de>
> >> ---
> >>  misc/ss.c | 91 ++++++++++++++++++++++++++++++++++-----------------------------
> >>  1 file changed, 49 insertions(+), 42 deletions(-)
> >>
> >> diff --git a/misc/ss.c b/misc/ss.c
> >> index 954a30b..46dbb39 100644
> >> [...]
> > 
> > Would you please respond if you received this patch ?
> > I am just checking, in case if it was get into 'Spam' list.
> > 
> > Regards,
> 
> I finally came around to testing this, sorry it took me so long.
> 
> Using that patch, the output looks much better. It works for my use case.
> 
> What do we do with the "broken" versions, though? Even if that patch hits 4.1.0,
> older versions like 4.0.0, 3.19.0 etc. will still be broken?
> 
> 
> 
> Mihai
> 

Hi Mihai,

I think it depends on distro package maintainers, usually they track the
upstream fixes and uses them in their stable versions, may be I should
grep some maintainers emails (LARTC mailing list ?) and broadcast to them ?

Regards,
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html