From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, dmonakhov@openvz.org
Subject: Re: [PATCH 1/2] quota: merge __dquot_transfer into dquot_transfer
Date: Mon, 8 Mar 2010 18:39:28 +0100 [thread overview]
Message-ID: <20100308173928.GG5644@quack.suse.cz> (raw)
In-Reply-To: <20100308171308.GA28427@infradead.org>
On Mon 08-03-10 12:13:08, Christoph Hellwig wrote:
> On Mon, Mar 08, 2010 at 06:11:34PM +0100, Jan Kara wrote:
> > On Sat 06-03-10 08:17:53, Christoph Hellwig wrote:
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > Christoph, I see that you have removed the 'mask' argument of
> > dquot_transfer. Actually, this has been added a short time ago as
> > a preparation for the project_id patches of Dmitry. Since his patches
> > seem to be getting in a good shape, I'd prefer not to make his life
> > harder and leave __dquot_transfer as is for now so that he can hook
> > into it.
>
> Dmitri will have to add code to grab the project ID somewhere. His
> patch made that easier when the two functions were split over an
> indirect call boundary, but now that this is gone it's not needed
> anymore. One line still needs to be added, and that's in the ne
> dquot_transfer.
Hmm, but dquot_transfer gets new uid/gid from struct iattr. So either
we have to extend struct iattr to accompany also project_id changes (fine
with me) or we have to keep interface similar to __dquot_transfer. Do
you have any preference?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2010-03-08 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 13:17 [PATCH 1/2] quota: merge __dquot_transfer into dquot_transfer Christoph Hellwig
2010-03-08 17:11 ` Jan Kara
2010-03-08 17:13 ` Christoph Hellwig
2010-03-08 17:39 ` Jan Kara [this message]
2010-03-08 17:42 ` Christoph Hellwig
2010-03-08 18:04 ` Jan Kara
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=20100308173928.GG5644@quack.suse.cz \
--to=jack@suse.cz \
--cc=dmonakhov@openvz.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@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 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).