do_coredump and O_NOFOLLOW

Hi All,

I found that O_NOFOLLOW is used for opened core file in Linux 2.6.10. This means the core file couldn't be a symbolic link. However, I want to use symbolic link for core file, So I plan to remove O_NOFOLLOW as follows, but I'm not sure there are any impacts introduced by the change?

file = filp_open(corename, O_CREAT | 2 | O_NOFOLLOW | O_LARGEFILE, 0600);

TO

file = filp_open(corename, O_CREAT | 2 /*| O_NOFOLLOW*/ | O_LARGEFILE, 0600);

Thanks,
Gavin
-
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: do_coredump and O_NOFOLLOW
    • From: Andy Isaacson <[email protected]>
  • Re: do_coredump and O_NOFOLLOW
    • From: Bernd Eckenfels <[email protected]>

• Prev by Date: Re: QUESTION: RT & SCHED & fork: ?MISSING EQUIV of task_new_fair for RT tasks.
• Next by Date: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
• Previous by thread: 2.6.23-rc3: sysfs_remove_bin_file: bad dentry or inode or no such file: "descriptors"
• Next by thread: Re: do_coredump and O_NOFOLLOW
• 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]