From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Reg mkdir syscall
Date: 4 Jun 2001 22:02:23 -0700 [thread overview]
Message-ID: <9fhp4v$aad$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10106031716330.3971-100000@blrmail> <Pine.LNX.4.10.10106042157410.10477-100000@blrmail>
Followup to: <Pine.LNX.4.10.10106042157410.10477-100000@blrmail>
By author: "SATHISH.J" <sathish.j@tatainfotech.com>
In newsgroup: linux.dev.kernel
>
> Actually I had written a small file system(on 2.2.14 kernel) similar to
> RAMFS on 2.4 kernel. I am able to mount it but when I try to create
> directory under it, it gives EEXIST error saying" file already exists" but
> when I check the directory again that file gets created. But the link
> count of the parent remains the same. I do not know how this directory
> gets created but with an error message. Please also tell me what all
> functions mkdir passes thro' while creating a directory. One more thing is
> when I took an strace of mkdir command the syscall mkdir fails with
> EEXIST error.
> Please help me with your thoughts.
>
Your code is broken.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-06-05 5:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10106031716330.3971-100000@blrmail>
2001-06-04 16:34 ` Reg mkdir syscall SATHISH.J
2001-06-05 5:02 ` H. Peter Anvin [this message]
2001-06-08 6:26 ` Reg compiling of source code SATHISH.J
2001-06-14 7:52 ` Reg-directory size SATHISH.J
2001-06-14 8:53 ` Daniel Phillips
2001-06-14 10:23 ` RAM filesystem directory size SATHISH.J
2001-06-15 10:22 ` Reg file system hash function SATHISH.J
2001-06-15 10:30 ` Russell King
2001-06-17 8:06 ` Reg:dentry->d_mounts value SATHISH.J
2001-06-17 8:14 ` Reg:magic number of the filesystem SATHISH.J
2001-06-17 8:21 ` Reg:use of file_system_type structure SATHISH.J
2001-06-17 8:21 ` Alexander Viro
2001-06-18 7:56 ` function of getname() function SATHISH.J
2001-06-18 7:42 ` Alexander Viro
2001-06-18 7:47 ` Tigran Aivazian
2001-06-18 8:35 ` Reg:current a pointer to task_struct SATHISH.J
2001-06-18 8:49 ` Reg putname() function SATHISH.J
2001-06-18 9:06 ` Reg:current a pointer to task_struct george anzinger
2001-06-20 9:41 ` filldir() function SATHISH.J
2001-06-20 22:26 ` Jan Kara
2001-06-25 7:11 ` Reg Kernel Debugger kdb SATHISH.J
2001-06-25 7:33 ` siva kumar
2001-06-25 8:36 ` Keith Owens
2001-06-26 4:54 ` Reg Kernel Debugger kgdb SATHISH.J
2001-06-26 10:01 ` using gdb to debug kernel SATHISH.J
2001-06-26 10:57 ` Lars Marowsky-Bree
2001-06-26 11:10 ` Reg installing a patch on linux SATHISH.J
2001-06-26 16:17 ` Reg Kernel Debugger kgdb Timur Tabi
2001-06-21 12:06 ` Reg:use of file_system_type structure Anuradha Ratnaweera
2001-06-17 8:26 ` Reg:magic number of the filesystem Alexander Viro
2001-06-11 4:59 ` exec format error SATHISH.J
2001-06-11 6:08 ` David Woodhouse
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='9fhp4v$aad$1@cesium.transmeta.com' \
--to=hpa@zytor.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.