linux-kernel - RE: [PATCH V1] extcon: modify extcon device to be created after driver data is set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <002701d85a98$04baa7e0$0e2ff7a0$@samsung.com>
Date:   Thu, 28 Apr 2022 09:36:36 +0900
From:   "Bumwoo Lee" <bw365.lee@...sung.com>
To:     "'Chanwoo Choi'" <cwchoi00@...il.com>,
        "'MyungJoo Ham'" <myungjoo.ham@...sung.com>,
        "'Chanwoo Choi'" <cw00.choi@...sung.com>,
        <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH V1] extcon: modify extcon device to be created after
 driver data is set

Hi Chanwoo,

Thank you for your kind detail guidance and example.

Best Regards,
Bumwoo Lee.
-----Original Message-----
From: Chanwoo Choi <cwchoi00@...il.com> 
Sent: Thursday, April 28, 2022 8:16 AM
To: bumwoo lee <bw365.lee@...sung.com>; MyungJoo Ham <myungjoo.ham@...sung.com>; Chanwoo Choi <cw00.choi@...sung.com>; linux-kernel@...r.kernel.org
Subject: Re: [PATCH V1] extcon: modify extcon device to be created after driver data is set

Hi bumwoo,

On 22. 4. 27. 12:00, bumwoo lee wrote:
> Currently, someone can invoke the sysfs such as state_show() 
> intermittently before dev_set_drvdata() is done.
> And it can be a cause of kernel Oops because of edev is Null at that time.
> So modified the driver registration to after setting drviver data.
> 
> - Oops's backtrace.
> 
> Backtrace:
> [<c067865c>] (state_show) from [<c05222e8>] (dev_attr_show) 
> [<c05222c0>] (dev_attr_show) from [<c02c66e0>] (sysfs_kf_seq_show) 
> [<c02c6648>] (sysfs_kf_seq_show) from [<c02c496c>] (kernfs_seq_show) 
> [<c02c4938>] (kernfs_seq_show) from [<c025e2a0>] (seq_read) 
> [<c025e11c>] (seq_read) from [<c02c50a0>] (kernfs_fop_read) 
> [<c02c5064>] (kernfs_fop_read) from [<c0231cac>] (__vfs_read) 
> [<c0231c5c>] (__vfs_read) from [<c0231ee0>] (vfs_read) [<c0231e34>] 
> (vfs_read) from [<c0232464>] (ksys_read) [<c02323f0>] (ksys_read) from 
> [<c02324fc>] (sys_read) [<c02324e4>] (sys_read) from [<c00091d0>] 
> (__sys_trace_return)
> 
> Signed-off-by: bumwoo lee <bw365.lee@...sung.com>
> ---
>   drivers/extcon/extcon.c | 29 +++++++++++++++++------------
>   1 file changed, 17 insertions(+), 12 deletions(-)
(snip)

Applied it on extcon-fixes. Thanks for your work.
I change the first letter to capital letter as  following:
- extcon: Modify extcon device to be created after driver data is set


And better to use the correct version on patch title on next and then add the changes according to version as following:
If you describe changes under '---', it is no problem when git apply with git am command.

For example.
[PATCH v2] extcon: Modify extcon device to be created after driver data ...

Signed-off-by: bumwoo lee <bw365.lee@...sung.com>
---

Changes from v1:
- explain what are changes


--
Best Regards,
Samsung Electronics
Chanwoo Choi