netdev - Re: [PATCH linux-stable-4.14] tcp: reset sk_send_head in tcp_write_queue

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: <CAGqmi75+g+p1myK9=kK8XURtOWAK7QmP4tbrVnVzRYgxOEDbrQ@mail.gmail.com>
Date:   Thu, 29 Mar 2018 13:00:03 +0300
From:   Timofey Titovets <nefelim4ag@...il.com>
To:     Willy Tarreau <w@....eu>
Cc:     davem@...emloft.net, yongjian xu <yongjianchn@...il.com>,
        Soheil Hassas Yeganeh <soheil.kdev@...il.com>,
        netdev@...r.kernel.org, ycheng@...gle.com, ncardwell@...gle.com,
        Soheil Hassas Yeganeh <soheil@...gle.com>,
        Eric Dumazet <edumazet@...gle.com>
Subject: Re: [PATCH linux-stable-4.14] tcp: reset sk_send_head in tcp_write_queue_purge

Hi,
any progress here?

I didn't find that patch applied for any 4.14.27-4.14.31

Patch rejected?

2018-03-20 19:13 GMT+03:00 Willy Tarreau <w@....eu>:
> Hi David,
>
> regarding the patch below, I'm not certain whether you planned to take
> it since it's marked "not applicable" on patchwork, but I suspect it's
> only because it doesn't apply to mainline.
>
> However, please note that there are two typos in commit IDs referenced in
> the commit message that might be nice to fix before merging :
>
>> > For example, after 27fid7a8ed38 (tcp: purge write queue upon RST),
>
> - here it's "a27fd7a8ed38" (missing 'a' and extra 'i' in the middle)
>
> - and lower in the fixes tag there's the extra 'i' as well :
>
>> > Fixes: a27fid7a8ed38 (tcp: purge write queue upon RST)
>
> There was another report today on the stable list for a similar crash
> on 4.14.28 and I suspect it's the one I saw this week-end on my firewall
> after upgrading from 4.14.10 to 4.14.27 though I didn't have the symbols
> to confirm.
>
> Thanks,
> Willy



-- 
Have a nice day,
Timofey.