All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "Isaman, Fred" <Fred.Isaman@netapp.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] SUNRPC: fix use-after-free of rpc pipes
Date: Mon, 27 Feb 2012 17:55:26 +0400	[thread overview]
Message-ID: <4F4B8B4E.7090307@parallels.com> (raw)
In-Reply-To: <1330350288.5541.3.camel@lade.trondhjem.org>

27.02.2012 17:44, Myklebust, Trond пишет:
> On Mon, 2012-02-27 at 16:51 +0400, Stanislav Kinsbursky wrote:
>> Frankly, I don't like the idea of put'ing pipe data on dentry unlink. IOW, I
>> don't like that this data will be controlled somehow in PipeFS.
>> I'll send my version soon.
>>
>
> I don't understand that objection. The lifetime of that data needs to be
> bounded by the lifetime of the pipe itself, which means that it _has_ to
> be controlled by the pipefs.
>
> BTW: it isn't being put on dentry unlink. It is being put on dentry
> _destruction_. Those are two different events (which is why we have a
> problem today).
>

Please, have a look at "SUNRPC: several fixes around PipeFS objects" patch set.
Briefly, pipe data is created on some kernel event (mount or module install), 
while PipeFS dentry/inode is created on user-space event (PipeFS mount/umount 
request). Thus this two objects are created independently.
And I believe, that they have to be destroyed independently too.

-- 
Best regards,
Stanislav Kinsbursky

  reply	other threads:[~2012-02-27 13:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 17:48 [PATCH] SUNRPC: fix use-after-free of rpc pipes Fred Isaman
2012-02-24 11:03 ` Stanislav Kinsbursky
2012-02-24 13:11   ` Fred Isaman
2012-02-24 11:47 ` Stanislav Kinsbursky
2012-02-24 13:17   ` Fred Isaman
2012-02-24 14:01     ` Stanislav Kinsbursky
2012-02-24 18:14 ` Stanislav Kinsbursky
2012-02-26 23:52   ` Myklebust, Trond
2012-02-27 12:51     ` Stanislav Kinsbursky
2012-02-27 13:44       ` Myklebust, Trond
2012-02-27 13:55         ` Stanislav Kinsbursky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-22 18:44 Fred Isaman

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=4F4B8B4E.7090307@parallels.com \
    --to=skinsbursky@parallels.com \
    --cc=Fred.Isaman@netapp.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-nfs@vger.kernel.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 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.