From: Mike Snitzer <snitzer@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, "Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: [PATCH v2] Re: dm: wait until kobject is destroyed
Date: Mon, 13 Jan 2014 22:02:02 -0500 [thread overview]
Message-ID: <20140114030202.GB5816@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1401131932130.30362@file01.intranet.prod.int.rdu2.redhat.com>
On Mon, Jan 13 2014 at 7:37pm -0500,
Mikulas Patocka <mpatocka@redhat.com> wrote:
> Here I'm sending the updated patch. (it reverts the patch that is already
> in git and applies the new patch). The patch is untested, because I don't
> use that git branch, but the same code was tested on Linus' 3.13-rc7.
>
> Mikulas
>
>
>
> From: Mikulas Patocka <mpatocka@redhat.com>
>
> dm-sysfs: fix a module unload race
>
> The code that calls the completion must be placed in non-module file,
> otherwise there is a module unload race (if the process is preempted and
> module unloaded after the completion is triggered, but before the function
> returns).
>
> To fix this race, this patch moves the completion code to dm-builtin.c
> that is always compiled directly to the kernel.
>
> The patch introduces a new structure struct dm_kobject_holder, its purpose
> is to keep the completion and the kobject at one place, so that it can be
> accessed from non-module code without the need to export the layout of
> struct mapped_device to that code.
Thanks for this v2 patch and updated header, I'll get it queued up.
prev parent reply other threads:[~2014-01-14 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 1:53 [PATCH] dm: wait until kobject is destroyed Mikulas Patocka
2014-01-10 21:03 ` Mike Snitzer
2014-01-14 0:37 ` [PATCH v2] " Mikulas Patocka
2014-01-14 3:02 ` Mike Snitzer [this message]
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=20140114030202.GB5816@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.