Re: [PATCH 1/3] NEW VERSION: *at syscalls: Implementation

Does sys_mkdirat() work?  I applied Ken's patch to hook up the calls for
ia64, but when I tried:

long sys_mkdirat(int dfd, const char *pathname, int mode)
{
        return syscall(__NR_mknodat, dfd, pathname, mode);
}

...

   sys_mkdirat(AT_FDCWD, "xxx", 0777);

I ended up with a regular file named "xxx", not a directory.
$ ls -l xxx
-rwsrwxr-x  1 aegl aegl 0 Feb  6 12:23 xxx

Hmmm, setuid too!

-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 1/3] NEW VERSION: *at syscalls: Implementation
    • From: Tony Luck <[email protected]>
  • Re: [PATCH 1/3] NEW VERSION: *at syscalls: Implementation
    • From: Tony Luck <[email protected]>

• Prev by Date: Re: DMA in PCI chipset -- module vs. compiled-in
• Next by Date: Re: DMA in PCI chipset -- module vs. compiled-in
• Previous by thread: [GIT PATCH] I2C and hwmon patches for 2.6.16-rc2
• Next by thread: Re: [PATCH 1/3] NEW VERSION: *at syscalls: Implementation
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]