[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1cbb69d83188424e99b2d2482848ae64@AcuMS.aculab.com>
Date: Thu, 8 Oct 2020 15:59:28 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Taehee Yoo' <ap420073@...il.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"wil6210@....qualcomm.com" <wil6210@....qualcomm.com>,
"brcm80211-dev-list@...ress.com" <brcm80211-dev-list@...ress.com>,
"b43-dev@...ts.infradead.org" <b43-dev@...ts.infradead.org>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>
Subject: RE: [PATCH net 000/117] net: avoid to remove module when its debugfs
is being used
From: Taehee Yoo
> Sent: 08 October 2020 16:49
>
> When debugfs file is opened, its module should not be removed until
> it's closed.
> Because debugfs internally uses the module's data.
> So, it could access freed memory.
>
> In order to avoid panic, it just sets .owner to THIS_MODULE.
> So that all modules will be held when its debugfs file is opened.
Can't you fix it in common code?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists