summaryrefslogtreecommitdiff
path: root/open_issues/open_symlink.mdwn
blob: 663bfcbdc5d8b9b1a4fd51cf6d8cd24b300e4b43 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]]

[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]

[[!tag open_issue_glibc]]


# IRC, freenode, #hurd, 2012-01-02

    <pinotree> hm, is it a known issue that open("somesymlink", O_RDONLY |
      O_NOFOLLOW) does not fail with ELOOP?
    <youpi> pinotree: iirc there is code for it, maybe not the same behavior as
      on linux


## IRC, OFTC, #debian-hurd, 2013-05-08

    <pinotree> the hurd issue is that O_NOFOLLOW seems broken on symlinks, and
      thus open(symlink, O_NOFOLLOW) doesn't fail with ELOOP
    <youpi> I don't really see why it should fail
    <youpi> since NOFOLLOW says not to follow the symlink
    <pinotree> yeah, but you cannot open a symlink
    <youpi> ah right ok
    <youpi> interesting :)