public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: "Greenman\, Gregory" <gregory.greenman@intel.com>,
	"linux\@roeck-us.net" <linux@roeck-us.net>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>,
	"rostedt\@goodmis.org" <rostedt@goodmis.org>, "Berg\,
	Johannes" <johannes.berg@intel.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev\@vger.kernel.org" <netdev@vger.kernel.org>, "Coelho\,
	Luciano" <luciano.coelho@intel.com>
Subject: Re: [PATCH] iwlwifi: iwl-dbg: Use del_timer_sync() before freeing
Date: Sat, 23 Apr 2022 09:35:16 +0300	[thread overview]
Message-ID: <87fsm4mhnf.fsf@kernel.org> (raw)
In-Reply-To: <CA+icZUVEfKcGi7ME3hoyinz2VQxLKhCXgwDA2K3AB7MEK-bveQ@mail.gmail.com> (Sedat Dilek's message of "Wed, 13 Apr 2022 17:06:26 +0200")

Sedat Dilek <sedat.dilek@gmail.com> writes:

> On Wed, Apr 13, 2022 at 11:56 AM Greenman, Gregory
> <gregory.greenman@intel.com> wrote:
>>
>>
>> On Mon, 2022-04-11 at 08:42 -0700, Guenter Roeck wrote:
>> > In Chrome OS, a large number of crashes is observed due to corrupted
>> > timer
>> > lists. Steven Rostedt pointed out that this usually happens when a
>> > timer
>> > is freed while still active, and that the problem is often triggered
>> > by code calling del_timer() instead of del_timer_sync() just before
>> > freeing.
>> >
>> > Steven also identified the iwlwifi driver as one of the possible
>> > culprits
>> > since it does exactly that.
>> >
>> > Reported-by: Steven Rostedt <rostedt@goodmis.org>
>> > Cc: Steven Rostedt <rostedt@goodmis.org>
>> > Cc: Johannes Berg <johannes.berg@intel.com>
>> > Cc: Gregory Greenman <gregory.greenman@intel.com>
>> > Fixes: 60e8abd9d3e91 ("iwlwifi: dbg_ini: add periodic trigger new API
>> > support")
>> > Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>> > ---
>> > v1 (from RFC):
>> >     Removed Shahar S Matityahu from Cc: and added Gregory Greenman.
>> >     No functional change.
>> >
>> > I thought about the need to add a mutex to protect the timer list,
>> > but
>> > I convinced myself that it is not necessary because the code adding
>> > the timer list and the code removing it should never be never
>> > executed
>> > in parallel.
>> >
>> >  drivers/net/wireless/intel/iwlwifi/iwl-dbg-tlv.c | 2 +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/net/wireless/intel/iwlwifi/iwl-dbg-tlv.c
>> > b/drivers/net/wireless/intel/iwlwifi/iwl-dbg-tlv.c
>> > index 866a33f49915..3237d4b528b5 100644
>> > --- a/drivers/net/wireless/intel/iwlwifi/iwl-dbg-tlv.c
>> > +++ b/drivers/net/wireless/intel/iwlwifi/iwl-dbg-tlv.c
>> > @@ -371,7 +371,7 @@ void iwl_dbg_tlv_del_timers(struct iwl_trans
>> > *trans)
>> >         struct iwl_dbg_tlv_timer_node *node, *tmp;
>> >
>> >         list_for_each_entry_safe(node, tmp, timer_list, list) {
>> > -               del_timer(&node->timer);
>> > +               del_timer_sync(&node->timer);
>> >                 list_del(&node->list);
>> >                 kfree(node);
>> >         }
>>
>> Hi Kalle,
>>
>> Can you please pick it up to wireless-drivers for the next rc?
>> It is an important fix.
>> Luca has already assigned it to you in patchwork.
>>
>> Thanks!
>>
>> Acked-by: Gregory Greenman <gregory.greenman@intel.com>
>
> I have tested this on top of Linux v5.17.3-rc1.
>
> Feel free to add my...
>
> Tested-by: Sedat Dilek <sedat.dilek@gmail.com> # Linux v5.17.3-rc1 and
> Debian LLVM-14

Please keep the Tested-by in one line, otherwise patchwork cannot parse
it correctly. I fixed this manually during commit.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2022-04-23  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 15:42 [PATCH] iwlwifi: iwl-dbg: Use del_timer_sync() before freeing Guenter Roeck
2022-04-13  9:56 ` Greenman, Gregory
2022-04-13 15:06   ` Sedat Dilek
2022-04-23  6:35     ` Kalle Valo [this message]
2022-04-23  6:33 ` Kalle Valo

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=87fsm4mhnf.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=gregory.greenman@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=luciano.coelho@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sedat.dilek@gmail.com \
    /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