From: Jens Axboe <jens.axboe@oracle.com>
To: Louis Rilling <louis.rilling@kerlabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] block: io_context refcount fixes
Date: Fri, 4 Dec 2009 16:34:43 +0100 [thread overview]
Message-ID: <20091204153443.GH8742@kernel.dk> (raw)
In-Reply-To: <1259934762-16920-1-git-send-email-louis.rilling@kerlabs.com>
On Fri, Dec 04 2009, Louis Rilling wrote:
>
> Hi,
>
> When reading copy_io() I found probable refcounting issues with shared
> io_context. IIUC, the following two patches could fix those issues.
> If I am correct, then those fixes should go to stable too.
>
> Based on v2.6.32 and compile-tested only.
Thanks, those both look correct. I will apply them, but please also do
whatever testing that caused you to find this in the first place (or was
it code inspection)?
--
Jens Axboe
next prev parent reply other threads:[~2009-12-04 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 13:52 Louis Rilling
2009-12-04 13:52 ` [PATCH 1/2] block: Fix io_context leak after clone with CLONE_IO Louis Rilling
2009-12-04 13:52 ` [PATCH 2/2] block: Fix io_context leak after failure of " Louis Rilling
2009-12-04 15:34 ` Jens Axboe [this message]
2009-12-04 16:03 ` [RFC] block: io_context refcount fixes Louis Rilling
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=20091204153443.GH8742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.rilling@kerlabs.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
all inboxes | Powered by JetHome®