From: "'Chanho Min'" <chanho.min@lge.com>
To: 'Wu Fengguang' <fengguang.wu@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
'Jens Axboe' <axboe@kernel.dk>,
'Andrew Morton' <akpm@linux-foundation.org>
Subject: RE: [PATCH] mm/backing-dev.c: fix crash when USB/SCSI device is detached
Date: Tue, 3 Jan 2012 12:47:23 +0900 [thread overview]
Message-ID: <003001ccc9ca$66dbf650$3493e2f0$@min@lge.com> (raw)
>On Mon, Jan 02, 2012 at 06:38:21PM +0900, ȣ wrote:
>> from Chanho Min <chanho.min@lge.com>
>>
>> System may crash in backing-dev.c when removal SCSI device is detached.
>> bdi task is killed by bdi_unregister()/'khubd', but task's point remains.
>> Shortly afterward, If 'wb->wakeup_timer' is expired before
>> del_timer()/bdi_forker_thread,
>> wakeup_timer_fn() may wake up the dead thread which cause the crash.
>> 'bdi->wb.task' should be NULL as this patch.
>
>Is it some race condition between del_timer() and del_timer_sync()?
>
>bdi_unregister() calls
>
> del_timer_sync
> bdi_wb_shutdown
> kthread_stop
>
>in turn, and del_timer_sync() should guarantee wakeup_timer_fn() is no
>longer called to access the stopped task.
>
It is not race condition. This happens when USB is removed during write-access.
bdi_wakeup_thread_delayed is called after kthread_stop, and timer is activated again.
bdi_unregister
kthread_stop
bdi_wakeup_thread_delayed (sys_write mostly calls this)
timer fires
Anyway,Is this safeguard to prevent from waking up killed thread?
Thanks,
Chanho
>Thanks,
>Fengguang
>
>
>> Signed-off-by: Chanho Min <chanho.min@lge.com>
>> ---
>> mm/backing-dev.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/mm/backing-dev.c b/mm/backing-dev.c index
>> 71034f4..4378a5e 100644
>> --- a/mm/backing-dev.c
>> +++ b/mm/backing-dev.c
>> @@ -607,6 +607,7 @@ static void bdi_wb_shutdown(struct
>> backing_dev_info
>> *bdi)
>> if (bdi->wb.task) {
>> thaw_process(bdi->wb.task);
>> kthread_stop(bdi->wb.task);
>> + bdi->wb.task = NULL;
>> }
>> }
>>
>> --
>> 1.7.0.4
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2012-01-03 3:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 3:47 'Chanho Min' [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-03 3:47 [PATCH] mm/backing-dev.c: fix crash when USB/SCSI device is detached 'Chanho Min'
2012-01-02 9:38 민찬호
2012-01-02 9:38 민찬호
2012-01-02 9:57 ` Wu Fengguang
2012-01-03 3:23 ` Chanho Min
2012-01-03 4:49 ` Wu Fengguang
2012-01-03 11:22 ` Chanho Min
2012-01-03 11:22 ` Chanho Min
2012-01-03 3:23 ` Chanho Min
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='003001ccc9ca$66dbf650$3493e2f0$@min@lge.com' \
--to=chanho.min@lge.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).