diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2025-06-02 12:49:16 -0700 | 
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2025-06-02 12:49:16 -0700 | 
| commit | fcd0bb8e99f7f5fbe6979b8633ed86502d822203 (patch) | |
| tree | 5e157a817c881c0b7cdfddabc76de24b0b34df71 /rust/helpers/task.c | |
| parent | 7f9039c524a351c684149ecf1b3c5145a0dff2fe (diff) | |
| parent | 5402c4d4d2000a9baa30c1157c97152ec6383733 (diff) | |
Merge tag 'vfs-6.16-rc2.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs
Pull vfs fixes from Christian Brauner:
 - Fix the AT_HANDLE_CONNECTABLE option so filesystems that don't know
   how to decode a connected non-dir dentry fail the request
 - Use repr(transparent) to ensure identical layout between the C and
   Rust implementation of struct file
 - Add a missing xas_pause() into the dax code employing
   wait_entry_unlocked_exclusive()
 - Fix FOP_DONTCACHE which we disabled for v6.15.
   A folio could get redirtied and/or scheduled for writeback after the
   initial dropbehind test. Change the test accordingly to handle these
   cases so we can re-enable FOP_DONTCACHE again
* tag 'vfs-6.16-rc2.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs:
  exportfs: require ->fh_to_parent() to encode connectable file handles
  rust: file: improve safety comments
  rust: file: mark `LocalFile` as `repr(transparent)`
  fs/dax: Fix "don't skip locked entries when scanning entries"
  iomap: don't lose folio dropbehind state for overwrites
  mm/filemap: unify dropbehind flag testing and clearing
  mm/filemap: unify read/write dropbehind naming
  Revert "Disable FOP_DONTCACHE for now due to bugs"
  mm/filemap: use filemap_end_dropbehind() for read invalidation
  mm/filemap: gate dropbehind invalidate on folio !dirty && !writeback
Diffstat (limited to 'rust/helpers/task.c')
0 files changed, 0 insertions, 0 deletions
