From: Carl Spalletta <cspalletta@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: dbehman@hotmail.com
Subject: Re: 2.6: marking individual directories as synchronous?
Date: Tue, 22 Jul 2003 06:20:19 -0700 (PDT) [thread overview]
Message-ID: <20030722132019.42790.qmail@web41504.mail.yahoo.com> (raw)
Grepping around in 2.6.0-test1 src I found:
include/linux/fs.h:
105 #define MS_DIRSYNC 128 /* Directory modifications are synchronous */
138 #define S_DIRSYNC 128 /* Directory modifications are synchronous */
Therefore, study the definitions and uses of those flags as well as
IS_DIRSYNC(), EXT3_DIRSYNC_FL, ext3_ioctl() & ext3_set_inode_flags().
For example:
[linux-2.6.0-test1]$ cscope -d -L -3 IS_DIRSYNC
...
fs/ext2/dir.c ext2_commit_chunk 71 if (IS_DIRSYNC(dir))
fs/ext3/ialloc.c ext3_new_inode 585 if (IS_DIRSYNC(inode))
fs/ext3/namei.c ext3_create 1638 if (IS_DIRSYNC(dir))
fs/ext3/namei.c ext3_mknod 1665 if (IS_DIRSYNC(dir))
fs/ext3/namei.c ext3_mkdir 1697 if (IS_DIRSYNC(dir))
fs/ext3/namei.c ext3_rmdir 1981 if (IS_DIRSYNC(dir))
fs/ext3/namei.c ext3_unlink 2033 if (IS_DIRSYNC(dir))
fs/ext3/namei.c ext3_symlink 2089 if (IS_DIRSYNC(dir))
fs/ext3/namei.c ext3_link 2139 if (IS_DIRSYNC(dir))
fs/minix/dir.c dir_commit_chunk 53 if (IS_DIRSYNC(dir))
fs/sysv/dir.c dir_commit_chunk 46 if (IS_DIRSYNC(dir))
fs/ufs/dir.c ufs_set_link 359 if (IS_DIRSYNC(dir))
fs/ufs/dir.c ufs_add_link 458 if (IS_DIRSYNC(dir))
fs/ufs/dir.c ufs_delete_entry 507 if (IS_DIRSYNC(inode))
...
I haven't actually played with the application of this, but it would appear
to be some combination of ioctl's and/or mount flags. Check the source for
chattr(1) to see if and how it uses the ioctl.
next reply other threads:[~2003-07-22 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 13:20 Carl Spalletta [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-22 18:57 2.6: marking individual directories as synchronous? Carl Spalletta
2003-07-17 20:59 Dan Behman
2003-07-20 0:31 ` Theodore Ts'o
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=20030722132019.42790.qmail@web41504.mail.yahoo.com \
--to=cspalletta@yahoo.com \
--cc=dbehman@hotmail.com \
--cc=linux-kernel@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.