[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANn89iLHd+Y=7xqx0OqfHXmqnUhhRycTARGfgq-y79Xhy5OQew@mail.gmail.com>
Date: Fri, 18 Feb 2022 05:05:25 -0800
From: Eric Dumazet <edumazet@...gle.com>
To: Andrzej Hajda <andrzej.hajda@...el.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
netdev <netdev@...r.kernel.org>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Daniel Vetter <daniel@...ll.ch>,
Lucas De Marchi <lucas.demarchi@...el.com>,
Chris Wilson <chris.p.wilson@...el.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Jakub Kicinski <kuba@...nel.org>
Subject: Re: [PATCH 5/9] lib/ref_tracker: improve allocation flags
On Fri, Feb 18, 2022 at 2:28 AM Andrzej Hajda <andrzej.hajda@...el.com> wrote:
> > git log --oneline 5740d0689096..4d449bdc5b26 --no-merges -- lib/ref_tracker.c
> > c2d1e3df4af59261777b39c2e47476acd4d1cbeb ref_tracker: remove
> > filter_irq_stacks() call
> > 8fd5522f44dcd7f05454ddc4f16d0f821b676cd9 ref_tracker: add a count of
> > untracked references
> > e3ececfe668facd87d920b608349a32607060e66 ref_tracker: implement
> > use-after-free detection
>
>
> So I will cherry-pick these patches into next version of patchset, with
> "NO MERGE" annotation (to allow testing), and if my ref_track patches
> will be accepted then they can go via net-dev tree and intel patches
> will wait till update of drm-tip.
> Is this scenario OK?
One possibility would be to split your patch series in two, to merge
the ref_tracker changes directly in net-next asap.
But I have no strong opinion, maybe Jakub/David have some guidance.
Powered by blists - more mailing lists