From: Chanwoo Choi <cw00.choi@samsung.com>
To: Hans de Goede <hdegoede@redhat.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] extcon: intel-int3496: Fix oops on probe
Date: Mon, 12 Feb 2018 08:36:13 +0900 [thread overview]
Message-ID: <5A80D36D.9050206@samsung.com> (raw)
In-Reply-To: <20180211232633.13565-1-hdegoede@redhat.com>
On 2018년 02월 12일 08:26, Hans de Goede wrote:
> Commit 41d600274fbf ("extcon: int3496: process id-pin first so that we
> start with the right status") starts the work on the workqueue before
> registration to make sure we've a valid cable state directly after
> registration.
>
> But that commit moves the queuing of the work to before we even alloc the
> extcon, causing a NULL pointer deref in the worker.
>
> This commit moves the queuing of the work to after we alloc the extcon,
> fixing the NULL pointer deref.
>
> Fixes: 41d600274fbf ("extcon: int3496: process id-pin first ...")
> Cc: stable@vger.kernel.org
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> drivers/extcon/extcon-intel-int3496.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/extcon/extcon-intel-int3496.c b/drivers/extcon/extcon-intel-int3496.c
> index b23ee9d993a3..673bb26a9a2a 100644
> --- a/drivers/extcon/extcon-intel-int3496.c
> +++ b/drivers/extcon/extcon-intel-int3496.c
> @@ -131,15 +131,15 @@ static int int3496_probe(struct platform_device *pdev)
> if (IS_ERR(data->gpio_usb_mux))
> dev_info(dev, "can't request USB MUX GPIO\n");
>
> + data->edev = devm_extcon_dev_allocate(dev, int3496_cable);
> + if (IS_ERR(data->edev))
> + return -ENOMEM;
> +
> /* process id-pin first so that we start with the right status */
> queue_delayed_work(system_wq, &data->work, 0);
> flush_delayed_work(&data->work);
>
> /* register extcon device */
> - data->edev = devm_extcon_dev_allocate(dev, int3496_cable);
> - if (IS_ERR(data->edev))
> - return -ENOMEM;
> -
> ret = devm_extcon_dev_register(dev, data->edev);
> if (ret < 0) {
> dev_err(dev, "can't register extcon device: %d\n", ret);
>
Instead, You better to send v3 after merging your patch[1] and this patch.
[1] extcon: int3496: process id-pin first so that we start with the right status
--
Best Regards,
Chanwoo Choi
Samsung Electronics
next prev parent reply other threads:[~2018-02-11 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180211232639epcas2p4495c006e2063cde1ce86710767cd8e97@epcas2p4.samsung.com>
2018-02-11 23:26 ` Hans de Goede
2018-02-11 23:36 ` Chanwoo Choi [this message]
2018-02-12 19:46 ` Hans de Goede
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=5A80D36D.9050206@samsung.com \
--to=cw00.choi@samsung.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=stable@vger.kernel.org \
/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
Powered by JetHome