Re: [patch] fix sys_mknodat breakage from r/o bind mounts

On Wed, 2007-09-26 at 00:58 +0200, Miklos Szeredi wrote:
> From: Miklos Szeredi <[email protected]>
> 
> mknod("foo", 0644) returns EINVAL, even though it should succeed.

Just to clarify, this is for when we use mknod to create normal,
non-device files, right?  Your fix looks very correct to me.

I'm curious, do you have a normal program that uses mknod(2) this way?
I'd like to add it to my test scripts.

Acked-by: Dave Hansen <[email protected]>

-- Dave

-
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] fix sys_mknodat breakage from r/o bind mounts
    • From: Miklos Szeredi <[email protected]>

• References:
  • [patch] fix sys_mknodat breakage from r/o bind mounts
    • From: Miklos Szeredi <[email protected]>

• Prev by Date: Re: subsystem_unregister() breakage in -mm
• Next by Date: missing mnt_drop_write() on open error
• Previous by thread: [patch] fix sys_mknodat breakage from r/o bind mounts
• Next by thread: Re: [patch] fix sys_mknodat breakage from r/o bind mounts
• 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]