[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG48ez1O2Nt2eiJ6ZbV8q+XSsg+Co4GhdaLxi-aNF4PRm5R+mg@mail.gmail.com>
Date: Tue, 1 Feb 2022 19:35:12 +0100
From: Jann Horn <jannh@...gle.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Matthew Wilcox <willy@...radead.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
Denys Vlasenko <vda.linux@...glemail.com>,
Kees Cook <keescook@...omium.org>,
Vlastimil Babka <vbabka@...e.cz>,
"Liam R . Howlett" <liam.howlett@...cle.com>
Subject: Re: [PATCH 3/5] coredump: Remove the WARN_ON in dump_vma_snapshot
On Mon, Jan 31, 2022 at 7:46 PM Eric W. Biederman <ebiederm@...ssion.com> wrote:
> The condition is impossible and to the best of my knowledge has never
> triggered.
>
> We are in deep trouble if that conditions happens and we walk past
> the end of our allocated array.
>
> So delete the WARN_ON and the code that makes it look like the kernel
> can handle the case of walking past the end of it's vma_meta array.
>
> Signed-off-by: "Eric W. Biederman" <ebiederm@...ssion.com>
Reviewed-by: Jann Horn <jannh@...gle.com>
Powered by blists - more mailing lists