Go to file
Linus Torvalds 0965549d6f vfs-6.17-rc1.super
-----BEGIN PGP SIGNATURE-----
 
 iHUEABYKAB0WIQRAhzRXHqcMeLMyaSiRxhvAZXjcogUCaINCsAAKCRCRxhvAZXjc
 op1/AQCYRmE6MsFclZ/6Qhpd8Xxl6jYaw0VuSIGneh/HA5EmqQEAiE3/Q0paC1HB
 PHryCsVau1yOfJtE1P05/3JLA73hWA4=
 =MBdP
 -----END PGP SIGNATURE-----

Merge tag 'vfs-6.17-rc1.super' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs

Pull superblock callback update from Christian Brauner:
 "Currently all filesystems which implement super_operations::shutdown()
  can not afford losing a device.

  Thus fs_bdev_mark_dead() will just call the ->shutdown() callback for
  the involved filesystem.

  But it will no longer be the case, as multi-device filesystems like
  btrfs can handle certain device loss without the need to shutdown the
  whole filesystem.

  To allow those multi-device filesystems to be integrated to use
  fs_holder_ops:

   - Add a new super_operations::remove_bdev() callback

   - Try ->remove_bdev() callback first inside fs_bdev_mark_dead().

     If the callback returned 0, meaning the fs can handling the device
     loss, then exit without doing anything else.

     If there is no such callback or the callback returned non-zero
     value, continue to shutdown the filesystem as usual.

  This means the new remove_bdev() should only do the check on whether
  the operation can continue, and if so do the fs specific handlings.
  The shutdown handling should still be handled by the existing
  ->shutdown() callback.

  For all existing filesystems with shutdown callback, there is no
  change to the code nor behavior.

  Btrfs is going to implement both the ->remove_bdev() and ->shutdown()
  callbacks soon"

* tag 'vfs-6.17-rc1.super' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs:
  fs: add a new remove_bdev() callback
2025-07-28 15:50:15 -07:00
Documentation vfs-6.17-rc1.fileattr 2025-07-28 15:24:14 -07:00
LICENSES
arch vfs-6.17-rc1.fileattr 2025-07-28 15:24:14 -07:00
block vfs-6.17-rc1.integrity 2025-07-28 15:12:00 -07:00
certs
crypto
drivers vfs-6.17-rc1.integrity 2025-07-28 15:12:00 -07:00
fs vfs-6.17-rc1.super 2025-07-28 15:50:15 -07:00
include vfs-6.17-rc1.super 2025-07-28 15:50:15 -07:00
init
io_uring
ipc
kernel
lib
mm vfs-6.17-rc1.fileattr 2025-07-28 15:24:14 -07:00
net
rust vfs-6.17-rc1.rust 2025-07-28 14:44:43 -07:00
samples
scripts vfs-6.17-rc1.fileattr 2025-07-28 15:24:14 -07:00
security vfs-6.17-rc1.fileattr 2025-07-28 15:24:14 -07:00
sound
tools
usr
virt
.clang-format
.clippy.toml
.cocciconfig
.editorconfig
.get_maintainer.ignore
.gitattributes
.gitignore
.mailmap
.pylintrc
.rustfmt.toml
COPYING
CREDITS
Kbuild
Kconfig
MAINTAINERS vfs-6.17-rc1.rust 2025-07-28 14:44:43 -07:00
Makefile
README

README

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 reStructuredText 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.