linux-kernel - Re: [PATCH, RESEND3] fuse: require /dev/fuse reads to have enough buffer capacity (take 2)

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: <CAJfpegscn7B+TrD5hckXkpHEb_62m6O9-kFOOehWyC89CPFunw@mail.gmail.com>
Date:   Thu, 1 Aug 2019 12:35:03 +0200
From:   Miklos Szeredi <miklos@...redi.hu>
To:     Kirill Smelkov <kirr@...edi.com>
Cc:     Miklos Szeredi <mszeredi@...hat.com>, gluster-devel@...ster.org,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        Sander Eikelenboom <linux@...elenboom.it>,
        Han-Wen Nienhuys <hanwen@...gle.com>,
        Jakob Unterwurzacher <jakobunt@...il.com>
Subject: Re: [PATCH, RESEND3] fuse: require /dev/fuse reads to have enough
 buffer capacity (take 2)

On Wed, Jul 24, 2019 at 11:46 AM Kirill Smelkov <kirr@...edi.com> wrote:
>
> Miklos,
>
> I was sending this patch for ~1.5 month without any feedback from you[1,2,3].
> The patch was tested by Sander Eikelenboom (original GlusterFS problem
> reporter)[4], and you said that it will be ok to retry for next
> cycle[5]. I was hoping for this patch to be picked up for 5.3 and queued
> to Linus's tree, but in despite several resends from me (the same patch;
> just reminders) nothing is happening. v5.3-rc1 came out on last Sunday,
> which, in my understanding, denotes the close of 5.3 merge window. What
> is going on? Could you please pick up the patch and handle it?

Applied.

Thanks,
Miklos