Thanks!
Jason
From: "Jason A. Donenfeld"
Date: Wed, 21 Feb 2018 04:41:59 +0100
> Before, if cb->start() failed, the module reference would never be put,
> because cb->cb_running is intentionally false at this point. Users are
> generally annoyed by this because they can no longer unload modules that
> leak ref
Hi,
On Wed, Feb 21, 2018 at 04:41:05PM +0100, Jason A. Donenfeld wrote:
Fixes: 41c87425a1ac ("netlink: do not set cb_running if dump's start() errs")
I think you Would better to resend it.
Bo,
Fixes: 41c87425a1ac ("netlink: do not set cb_running if dump's start() errs")
On Wed, 2018-02-21 at 15:54 +0100, Jason A. Donenfeld wrote:
> On Wed, Feb 21, 2018 at 6:47 AM, Eric Dumazet wrote:
> > > This probably should be queued up for stable.
> >
> > When was the bug added ? This would help a lot stable teams ...
>
> This needs to be backported to 4.16-rc0+, 4.15+, 4.1
On Wed, Feb 21, 2018 at 6:47 AM, Eric Dumazet wrote:
>> This probably should be queued up for stable.
>
> When was the bug added ? This would help a lot stable teams ...
This needs to be backported to 4.16-rc0+, 4.15+, 4.14+, 4.13.14+, and 4.9.63+.
On Wed, 2018-02-21 at 04:41 +0100, Jason A. Donenfeld wrote:
> Before, if cb->start() failed, the module reference would never be put,
> because cb->cb_running is intentionally false at this point. Users are
> generally annoyed by this because they can no longer unload modules that
> leak reference
Before, if cb->start() failed, the module reference would never be put,
because cb->cb_running is intentionally false at this point. Users are
generally annoyed by this because they can no longer unload modules that
leak references. Also, it may be possible to tediously wrap a reference
counter bac
8 matches
Mail list logo