From: Rob Herring <robh+dt@kernel.org> To: Frank Rowand <frowand.list@gmail.com> Cc: Michael Ellerman <mpe@ellerman.id.au>, mwb@linux.vnet.ibm.com, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, Tyrel Datwyler <tyreld@linux.vnet.ibm.com>, tlfalcon@linux.vnet.ibm.com, minkim@us.ibm.com, devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v2 2/2] of: __of_detach_node() - remove node from phandle cache Date: Tue, 18 Dec 2018 14:58:55 -0600 [thread overview] Message-ID: <CAL_JsqLjhc4LSVKLVm7d+T+74xLK5kYNN0NLZySv1zV0tg5ibQ@mail.gmail.com> (raw) In-Reply-To: <6b6a3d11-e60a-f55c-04fa-deafdd58ccec@gmail.com> On Tue, Dec 18, 2018 at 2:33 PM Frank Rowand <frowand.list@gmail.com> wrote: > > On 12/18/18 12:09 PM, Frank Rowand wrote: > > On 12/18/18 12:01 PM, Rob Herring wrote: > >> On Tue, Dec 18, 2018 at 12:57 PM Frank Rowand <frowand.list@gmail.com> wrote: > >>> > >>> On 12/17/18 2:52 AM, Michael Ellerman wrote: > >>>> Hi Frank, > >>>> > >>>> frowand.list@gmail.com writes: > >>>>> From: Frank Rowand <frank.rowand@sony.com> > >>>>> > >>>>> Non-overlay dynamic devicetree node removal may leave the node in > >>>>> the phandle cache. Subsequent calls to of_find_node_by_phandle() > >>>>> will incorrectly find the stale entry. Remove the node from the > >>>>> cache. > >>>>> > >>>>> Add paranoia checks in of_find_node_by_phandle() as a second level > >>>>> of defense (do not return cached node if detached, do not add node > >>>>> to cache if detached). > >>>>> > >>>>> Reported-by: Michael Bringmann <mwb@linux.vnet.ibm.com> > >>>>> Signed-off-by: Frank Rowand <frank.rowand@sony.com> > >>>>> --- > >>>> > >>>> Similarly here can we add: > >>>> > >>>> Fixes: 0b3ce78e90fc ("of: cache phandle nodes to reduce cost of of_find_node_by_phandle()") > >>> > >>> Yes, thanks. > >>> > >>> > >>>> Cc: stable@vger.kernel.org # v4.17+ > >>> > >>> Nope, 0b3ce78e90fc does not belong in stable (it is a feature, not a bug > >>> fix). So the bug will not be in stable. > >> > >> 0b3ce78e90fc landed in v4.17, so Michael's line above is correct. > >> Annotating it with 4.17 only saves Greg from trying and then emailing > >> us to backport this patch as it wouldn't apply. > > > > Thanks for the correction. I was both under-thinking and over-thinking, > > ending up with an incorrect answer. > > > > Can you add the Cc: to version 3 patch comments (both 1/2 and 2/2) or do > > you want me to re-spin? > > Now that my thinking has been straightened out, a little bit more checking > for the other pre-requisite patches show: > > v4.18: commit b9952b5218ad ("of: overlay: update phandle cache on overlay apply and remove") > v4.19: commit e54192b48da7 ("of: fix phandle cache creation for DTs with no phandles") > > These can be addressed by changing the "Cc:" to ... # v4.19+ > because stable v4.17.* and v4.18.* are end of life. EOL shouldn't factor into it. There's always the possibility someone else picks any kernel version. > Or the pre-requisites can be listed: > > # v4.17: b9952b5218ad of: overlay: update phandle cache > # v4.17: e54192b48da7 of: fix phandle cache creation > # v4.17 > > # v4.18: e54192b48da7 of: fix phandle cache creation > # v4.18 > > # v4.19+ > > Do you have a preference? I think we just list v4.17 and be done with it. Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh+dt@kernel.org> To: Frank Rowand <frowand.list@gmail.com> Cc: devicetree@vger.kernel.org, tlfalcon@linux.vnet.ibm.com, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, mwb@linux.vnet.ibm.com, minkim@us.ibm.com, Tyrel Datwyler <tyreld@linux.vnet.ibm.com>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org> Subject: Re: [PATCH v2 2/2] of: __of_detach_node() - remove node from phandle cache Date: Tue, 18 Dec 2018 14:58:55 -0600 [thread overview] Message-ID: <CAL_JsqLjhc4LSVKLVm7d+T+74xLK5kYNN0NLZySv1zV0tg5ibQ@mail.gmail.com> (raw) In-Reply-To: <6b6a3d11-e60a-f55c-04fa-deafdd58ccec@gmail.com> On Tue, Dec 18, 2018 at 2:33 PM Frank Rowand <frowand.list@gmail.com> wrote: > > On 12/18/18 12:09 PM, Frank Rowand wrote: > > On 12/18/18 12:01 PM, Rob Herring wrote: > >> On Tue, Dec 18, 2018 at 12:57 PM Frank Rowand <frowand.list@gmail.com> wrote: > >>> > >>> On 12/17/18 2:52 AM, Michael Ellerman wrote: > >>>> Hi Frank, > >>>> > >>>> frowand.list@gmail.com writes: > >>>>> From: Frank Rowand <frank.rowand@sony.com> > >>>>> > >>>>> Non-overlay dynamic devicetree node removal may leave the node in > >>>>> the phandle cache. Subsequent calls to of_find_node_by_phandle() > >>>>> will incorrectly find the stale entry. Remove the node from the > >>>>> cache. > >>>>> > >>>>> Add paranoia checks in of_find_node_by_phandle() as a second level > >>>>> of defense (do not return cached node if detached, do not add node > >>>>> to cache if detached). > >>>>> > >>>>> Reported-by: Michael Bringmann <mwb@linux.vnet.ibm.com> > >>>>> Signed-off-by: Frank Rowand <frank.rowand@sony.com> > >>>>> --- > >>>> > >>>> Similarly here can we add: > >>>> > >>>> Fixes: 0b3ce78e90fc ("of: cache phandle nodes to reduce cost of of_find_node_by_phandle()") > >>> > >>> Yes, thanks. > >>> > >>> > >>>> Cc: stable@vger.kernel.org # v4.17+ > >>> > >>> Nope, 0b3ce78e90fc does not belong in stable (it is a feature, not a bug > >>> fix). So the bug will not be in stable. > >> > >> 0b3ce78e90fc landed in v4.17, so Michael's line above is correct. > >> Annotating it with 4.17 only saves Greg from trying and then emailing > >> us to backport this patch as it wouldn't apply. > > > > Thanks for the correction. I was both under-thinking and over-thinking, > > ending up with an incorrect answer. > > > > Can you add the Cc: to version 3 patch comments (both 1/2 and 2/2) or do > > you want me to re-spin? > > Now that my thinking has been straightened out, a little bit more checking > for the other pre-requisite patches show: > > v4.18: commit b9952b5218ad ("of: overlay: update phandle cache on overlay apply and remove") > v4.19: commit e54192b48da7 ("of: fix phandle cache creation for DTs with no phandles") > > These can be addressed by changing the "Cc:" to ... # v4.19+ > because stable v4.17.* and v4.18.* are end of life. EOL shouldn't factor into it. There's always the possibility someone else picks any kernel version. > Or the pre-requisites can be listed: > > # v4.17: b9952b5218ad of: overlay: update phandle cache > # v4.17: e54192b48da7 of: fix phandle cache creation > # v4.17 > > # v4.18: e54192b48da7 of: fix phandle cache creation > # v4.18 > > # v4.19+ > > Do you have a preference? I think we just list v4.17 and be done with it. Rob
next prev parent reply other threads:[~2018-12-18 20:59 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-17 7:56 [PATCH v2 0/2] of: phandle_cache, fix refcounts, remove stale entry frowand.list 2018-12-17 7:56 ` frowand.list 2018-12-17 7:56 ` [PATCH v2 1/2] of: of_node_get()/of_node_put() nodes held in phandle cache frowand.list 2018-12-17 7:56 ` frowand.list 2018-12-17 10:43 ` Michael Ellerman 2018-12-17 10:43 ` Michael Ellerman 2018-12-17 7:56 ` [PATCH v2 2/2] of: __of_detach_node() - remove node from " frowand.list 2018-12-17 7:56 ` frowand.list 2018-12-17 10:52 ` Michael Ellerman 2018-12-17 10:52 ` Michael Ellerman 2018-12-18 18:57 ` Frank Rowand 2018-12-18 18:57 ` Frank Rowand 2018-12-18 20:01 ` Rob Herring 2018-12-18 20:01 ` Rob Herring 2018-12-18 20:09 ` Frank Rowand 2018-12-18 20:09 ` Frank Rowand 2018-12-18 20:33 ` Frank Rowand 2018-12-18 20:33 ` Frank Rowand 2018-12-18 20:58 ` Rob Herring [this message] 2018-12-18 20:58 ` Rob Herring 2018-12-18 23:44 ` Michael Ellerman 2018-12-18 23:44 ` Michael Ellerman 2018-12-18 23:44 ` Michael Ellerman 2018-12-18 15:43 ` [PATCH v2 0/2] of: phandle_cache, fix refcounts, remove stale entry Rob Herring 2018-12-18 15:43 ` Rob Herring 2018-12-18 23:46 ` Michael Ellerman 2018-12-18 23:46 ` Michael Ellerman 2018-12-18 23:46 ` Michael Ellerman
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAL_JsqLjhc4LSVKLVm7d+T+74xLK5kYNN0NLZySv1zV0tg5ibQ@mail.gmail.com \ --to=robh+dt@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=frowand.list@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=minkim@us.ibm.com \ --cc=mpe@ellerman.id.au \ --cc=mwb@linux.vnet.ibm.com \ --cc=tlfalcon@linux.vnet.ibm.com \ --cc=tyreld@linux.vnet.ibm.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.