From: Nick Piggin <npiggin@kernel.dk>
To: sedat.dilek@gmail.com
Cc: linux-fsdevel@vger.kernel.org, linux-next@vger.kernel.org,
systemd-devel@lists.freedesktop.org,
Nick Piggin <npiggin@kernel.dk>,
eparis@redhat.com
Subject: Re: [patch] cgroup fs: avoid switching ->d_op on live dentry
Date: Tue, 21 Dec 2010 19:55:38 +1100 [thread overview]
Message-ID: <20101221085538.GA9133@amd> (raw)
In-Reply-To: <AANLkTinod+7fDMwh8_XsQe4mnF1P6WoRWyh36yJXM4LO@mail.gmail.com>
On Tue, Dec 21, 2010 at 09:44:40AM +0100, Sedat Dilek wrote:
> Against linux-next (next-20101210) it should look like:
Yep, I'll rebase my tree with the fix shortly.
>
> $ diff -Naur cgroup-fix/cgroup-fs-avoid-switching-d_op-on-live-dentry.patch
> cgroup-fix/cgroup-fs-avoid-switching-d_op-on-live-dentry-v2.patch
> --- cgroup-fix/cgroup-fs-avoid-switching-d_op-on-live-dentry.patch
> 2010-12-21 09:31:38.649601964 +0100
> +++ cgroup-fix/cgroup-fs-avoid-switching-d_op-on-live-dentry-v2.patch
> 2010-12-21 09:40:21.151033232 +0100
> @@ -83,7 +83,7 @@
> inode->i_size = 0;
> inode->i_fop = &cgroup_file_operations;
> }
> -- dentry->d_op = &cgroup_dops;
> +- d_set_d_op(dentry, &cgroup_dops);
> d_instantiate(dentry, inode);
> dget(dentry); /* Extra count - pin the dentry in core */
> return 0;
>
> - Sedat -
next prev parent reply other threads:[~2010-12-21 8:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 8:44 [patch] cgroup fs: avoid switching ->d_op on live dentry Sedat Dilek
2010-12-21 8:55 ` Nick Piggin [this message]
2010-12-21 13:35 ` Sedat Dilek
2010-12-21 18:25 ` Al Viro
2010-12-21 18:57 ` Sedat Dilek
2010-12-22 3:11 ` Nick Piggin
2010-12-22 3:31 ` Sedat Dilek
2010-12-22 4:38 ` Sedat Dilek
2010-12-21 15:12 ` Sedat Dilek
2010-12-21 15:28 ` Sedat Dilek
2010-12-21 17:56 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2010-12-21 7:12 Nick Piggin
2010-12-21 9:04 ` Paul Menage
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=20101221085538.GA9133@amd \
--to=npiggin@kernel.dk \
--cc=eparis@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=systemd-devel@lists.freedesktop.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.