From: Nikita Danilov <Nikita@Namesys.COM>
To: Nir Tzachar <tzachar@cs.bgu.ac.il>
Cc: viro@parcelfarce.linux.theplanet.co.uk, linux-fsdevel@vger.kernel.org
Subject: Re: inode->i_op->rename semantics .
Date: Tue, 13 May 2003 19:48:18 +0400 [thread overview]
Message-ID: <16065.5058.892020.773612@laputa.namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44_heb2.09.0305131820570.14327-100000@tapuz1.cs.bgu.ac.il>
Nir Tzachar writes:
> > > can someone please clarify what am i supposed to do in the rename
> > > function??
> >
> > Er...rename the damn thing?
>
> duh....
>
> but be a bit serious: all the "renaming" __stuff__ is done at the vfs layer.
> so what the specific f/s is expected to implement?
>
Update persistent data. Take a look at fs/ext2/namei.c:ext2_rename()
>
>
> ========================================================================
> nir.
>
Nikita.
next prev parent reply other threads:[~2003-05-13 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 9:29 inode->i_op->rename semantics Nir Tzachar
2003-05-13 10:06 ` viro
2003-05-13 15:23 ` Nir Tzachar
2003-05-13 15:48 ` Nikita Danilov [this message]
2003-05-13 19:28 ` Charles Manning
2003-05-14 5:54 ` Nir Tzachar
2003-05-14 15:33 ` viro
2003-05-15 7:46 ` Nir Tzachar
2003-05-15 22:20 ` Charles Manning
2003-05-16 1:09 ` viro
2003-05-16 7:39 ` Nir Tzachar
2003-05-25 17:54 ` David Chow
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=16065.5058.892020.773612@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tzachar@cs.bgu.ac.il \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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