On 4 May 2020, at 20:43, Andrii Nakryiko wrote:
On Mon, May 4, 2020 at 2:13 AM Eelco Chaudron
wrote:
When the probe code was failing for any reason ENOTSUP was returned,
even
if this was due to no having enough lock space. This patch fixes this
by
returning EPERM to the user application,
On Tue, May 5, 2020 at 3:07 AM Toke Høiland-Jørgensen wrote:
>
> Andrii Nakryiko writes:
>
> > On Mon, May 4, 2020 at 2:13 AM Eelco Chaudron wrote:
> >>
> >> When the probe code was failing for any reason ENOTSUP was returned, even
> >> if this was due to no having enough lock space. This patch
Andrii Nakryiko writes:
> On Mon, May 4, 2020 at 2:13 AM Eelco Chaudron wrote:
>>
>> When the probe code was failing for any reason ENOTSUP was returned, even
>> if this was due to no having enough lock space. This patch fixes this by
>> returning EPERM to the user application, so it can respond
On Mon, May 4, 2020 at 2:13 AM Eelco Chaudron wrote:
>
> When the probe code was failing for any reason ENOTSUP was returned, even
> if this was due to no having enough lock space. This patch fixes this by
> returning EPERM to the user application, so it can respond and increase
> the RLIMIT_MEMLO
When the probe code was failing for any reason ENOTSUP was returned, even
if this was due to no having enough lock space. This patch fixes this by
returning EPERM to the user application, so it can respond and increase
the RLIMIT_MEMLOCK size.
Signed-off-by: Eelco Chaudron
---
v2: Split bpf_objec
