# NTFS in Linux (2024-02-04)

**URL:** <https://pluralist.net/t/ntfs-in-linux-2024-02-04/65>\
**Category:** Code Reading\
**Created:** [February 5, 2024, 6:33am UTC](https://pluralist.net/t/ntfs-in-linux-2024-02-04/65 "2024-02-05T06:33:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![delyan](https://pluralist.net/user_avatar/pluralist.net/delyan/32/245_2.png) [@delyan](https://pluralist.net/u/delyan)\
**Post date:** [February 5, 2024, 6:33am UTC](https://pluralist.net/t/ntfs-in-linux-2024-02-04/65/1 "2024-02-05T06:33:19Z")

</div>

- the Linux Cross Reference is a great resource - currently exploring NTFS as implemented by Paragon Software - [LXR / The Linux Cross Reference](https://lxr.linux.no/#linux+v6.7.1/fs/ntfs3/dir.c)
- learned about [the surrogate tag in NTFS](https://lxr.linux.no/#linux+v6.7.1/fs/ntfs3/ntfs.h#L1034), which indicates whether the given file actually represents some other named entity
- it is interesting to examine [the code Linus Torvards wrote for **Kernel v0.01**](https://lxr.linux.no/#linux+v6.7.1/fs/ntfs3/ntfs.h#L1034) back in 1991.
- here is the Linux Kernel [coding style](https://www.kernel.org/doc/html/v4.10/process/coding-style.html) - I am surprised to see:

> Do not unnecessarily use braces where a single statement will do.

I would have assumed that for safety, the coding style would have recommended one always use curly braces, even unnecessarily when `if` or `for` is followed by a single statement.

Overall - the placement of braces is unsurprising - at the end of the first line of the for/if etc and at the beginning of the last line.

Exception:

> However, there is one special case, namely functions: they have the opening brace at the beginning of the next line, thus:

I would have personally preferred to follow the for/if braces placement for functions too i.e. placing the opening brace as the last character on the line declaring the function.