netdev - Re: Bad checksum on bridge with IP options

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: <5370A6FF.3040902@davidnewall.com>
Date:	Mon, 12 May 2014 20:18:31 +0930
From:	David Newall <davidn@...idnewall.com>
To:	Lukas Tribus <luky-37@...mail.com>, Netdev <netdev@...r.kernel.org>
Subject: Re: Bad checksum on bridge with IP options

On 12/05/14 20:01, Lukas Tribus wrote:
>> >I don't suppose it's so old that anyone would be unsure about
>> >a change which might have fixed the problem since then.
> I disagree.

Oh, excellent.  You must know about a very recent patch that would fix 
the problem.  Please, point me in the right direction.

>> >This is a bug. Let's not stand on ceremony. Let's fix it.
> So you are not willing to test latest kernels, but expect the
> developers here to fix the bug?

Yes, I do expect developers to look at the bug even though I haven't 
checked the absolutely, positively, hottest-off-the-press, latest 
kernel.  That's what developers of serious software do: they treat 
serious bug reports seriously and with respect.  They don't engage in 
bloody-mindedness.  They don't grasp for excuses to ignore problems.  
Not unless they don't care about what they develop, and I happen to know 
that Linux developers care very passionately about the software.

Developers aren't going to take my word that the problem exists, but 
will try to reproduce it for themselves.  The purpose of trying vanilla 
kernels is to pre-qualify bugs, so that they don't waste their time 
chasing phantoms.  I've done that.  I've pre-qualified it; there's a bug.

Do you have an actual reason to think that this bug, which clearly has 
been undiagnosed for quite some time, has been fixed.  Because that 
would justify telling me to try a newer kernel.  If you don't, you're 
just being officious.
--
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