[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <566f206c-f133-6f68-c257-2c0b3ec462fa@iogearbox.net>
Date: Mon, 16 Dec 2019 12:17:50 +0100
From: Daniel Borkmann <daniel@...earbox.net>
To: Yonghong Song <yhs@...com>, Aditya Pakki <pakki001@....edu>
Cc: "kjlu@....edu" <kjlu@....edu>, Alexei Starovoitov <ast@...nel.org>,
Martin Lau <kafai@...com>, Song Liu <songliubraving@...com>,
Andrii Nakryiko <andriin@...com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"bpf@...r.kernel.org" <bpf@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] bpf: Replace BUG_ON when fp_old is NULL
On 12/15/19 11:08 PM, Yonghong Song wrote:
> On 12/15/19 7:44 AM, Aditya Pakki wrote:
>> If fp_old is NULL in bpf_prog_realloc, the program does an assertion
>> and crashes. However, we can continue execution by returning NULL to
>> the upper callers. The patch fixes this issue.
>
> Could you share how to reproduce the assertion and crash? I would
> like to understand the problem first before making changes in the code.
> Thanks!
Fully agree, Aditya, please elaborate if you have seen a crash!
Powered by blists - more mailing lists