mirror of
https://github.com/linux-apfs/linux-apfs.git
synced 2026-08-18 02:22:47 -07:00
Ernesto A. Fernández
652bc7e61e
Having separate code to deal with inode numbers in 32-bit architectures has proved unwise; there is no verified performance benefit from this and now, after several commits with no testing, the 32-bit code won't even build. Fix this with a new const qualifier in the argument to APFS_I(), and from now on just use the 32-bit version of everything. It's important to always read the inode number with apfs_ino(), to avoid getting confused and working with the potentially overflowing i_ino; remove a few remaining instances of this bug. Also start setting the number by means of apfs_set_inode(), but don't touch the hacky code for private-dir; I intend to turn it into a real inode in the future. Finally, deal with the TODO regarding insert_inode_locked(): define apfs_insert_inode_locked() as a wrapper to insert_inode_locked4(), implementing the same functionality as insert_inode_locked() but with full support for 32-bit architectures. Signed-off-by: Ernesto A. Fernández <ernesto.mnd.fernandez@gmail.com>
Linux kernel
============
There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.
In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``. The formatted documentation can also be read online at:
https://www.kernel.org/doc/html/latest/
There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.
Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.