From: Martin Kaiser <martin@kaiser.cx>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>,
David Woodhouse <dwmw2@infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: mxc: remove __init qualifier from mxcnd_probe_dt
Date: Wed, 27 Jun 2018 10:55:11 +0200 [thread overview]
Message-ID: <20180627085511.GA31924@botnar.kaiser.cx> (raw)
In-Reply-To: <20180626093650.5835593b@xps13>
Hi Miquel & Boris,
thanks for your feedback.
Thus wrote Miquel Raynal (miquel.raynal@bootlin.com):
> Hi Boris,
> On Tue, 26 Jun 2018 09:24:13 +0200, Boris Brezillon
> <boris.brezillon@bootlin.com> wrote:
> > On Tue, 26 Jun 2018 09:10:05 +0200
> > Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> > > Hi Martin, Boris,
> > > On Fri, 22 Jun 2018 16:50:25 +0200, Martin Kaiser <martin@kaiser.cx>
> > > wrote:
> > > > mxcnd_probe_dt is called from mxcnd_probe, which is not marked as __init.
> > > I think this line is just a side note and should be at the end of the
> > > commit log.
> > > > Using the sysfs unbind, bind nodes, mxcnd_probe and mxcnd_probe_dt can
> > > > potentially be called at any time. After the __init functions are cleaned,
> > > > mxcnd_probe_dt is no longer available. Calling it anyway causes a crash.
> > > The above paragraph explains the problem and the solution, you can just
> > > add something like "mcvnd_probe is untouched because it is already not
> > > marked as __init" instead of the first line.
> > > > Signed-off-by: Martin Kaiser <martin@kaiser.cx>
> > > Boris, do you think this patch is a good candidate for stable?
> > > If yes, Martin, could you please add a couple of stable/fixes tags above
> > > your SoB?
> > We should at least have a Fixes tag. For the stable one, I'm not so
> > sure because the bug does not exist in practice (the compiler always
> > inline mxcnd_probe_dt()).
> Fine, then a Fixes tag will be enough and I will take it into
> nand/next as it is not urgent at all to have it in the main tree.
I agree that this is not a candidate for stable. I just sent an update
with a Fixes tag and rephrased commit message.
Best regards,
Martin
next prev parent reply other threads:[~2018-06-27 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 14:50 [PATCH] mtd: rawnand: mxc: remove __init qualifier from mxcnd_probe_dt Martin Kaiser
2018-06-26 7:10 ` Miquel Raynal
2018-06-26 7:24 ` Boris Brezillon
2018-06-26 7:36 ` Miquel Raynal
2018-06-27 8:55 ` Martin Kaiser [this message]
2018-06-27 8:52 ` [PATCH v2] " Martin Kaiser
2018-06-27 9:01 ` Miquel Raynal
2018-06-27 20:47 ` [PATCH v3] " Martin Kaiser
2018-06-27 21:35 ` Boris Brezillon
2018-07-01 18:12 ` Miquel Raynal
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=20180627085511.GA31924@botnar.kaiser.cx \
--to=martin@kaiser.cx \
--cc=boris.brezillon@bootlin.com \
--cc=dwmw2@infradead.org \
--cc=fabio.estevam@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=s.hauer@pengutronix.de \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).