[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e422d90e7e2d5a2c326de9c12aa70f8d3f82b96.camel@sipsolutions.net>
Date: Mon, 23 May 2022 15:43:34 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Kalle Valo <kvalo@...nel.org>, duoming@....edu.cn
Cc: Greg KH <gregkh@...uxfoundation.org>,
linux-wireless@...r.kernel.org, amitkarwar@...il.com,
ganapathi017@...il.com, sharvari.harisangam@....com,
huxinming820@...il.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, rafael@...nel.org
Subject: Re: [PATCH v3] mwifiex: fix sleep in atomic context bugs caused by
dev_coredumpv
On Mon, 2022-05-23 at 14:31 +0300, Kalle Valo wrote:
>
> In a way it would be nice to be able to call dev_coredump from atomic
> contexts, though I don't know how practical it actually is. Is there any
> other option? What about adding a gfp_t parameter to dev_set_name()? Or
> is there an alternative for dev_set_name() which can be called in atomic
> contexts?
>
> Johannes&Greg, any ideas?
If you need to, I guess you can collect the data into some area and then
provide it to devcoredump later? Not sure it's a good idea though since
collecting data can take a while.
johannes
Powered by blists - more mailing lists