Linux-Fsdevel Archive on lore.kernel.org
 help / color / Atom feed
[PATCH 0/3] Large pages in the page cache
 2019-09-09  1:12 UTC  (16+ messages) - mbox.gz / Atom
` [PATCH 2/3] mm: Allow large pages to be added to "
` [PATCH 3/3] mm: Allow find_get_page to be used for large pages
      ` [kbuild-all] "
` [PATCH 4/3] Prepare transhuge pages properly

[PATCH v2 0/5] Add support for O_MAYEXEC
 2019-09-09  0:16 UTC  (34+ messages) - mbox.gz / Atom
` [PATCH v2 1/5] fs: Add support for an O_MAYEXEC flag on sys_open()
` [PATCH v2 2/5] fs: Add a MAY_EXECMOUNT flag to infer the noexec mount propertie
` [PATCH v2 3/5] fs: Enable to enforce noexec mounts or file exec through O_MAYEXEC
` [PATCH v2 4/5] selftest/exec: Add tests for O_MAYEXEC enforcing
` [PATCH v2 5/5] doc: Add documentation for the fs.open_mayexec_enforce sysctl

[PATCH erofs-utils v2] build: cure compiler warnings
 2019-09-08 23:54 UTC  (2+ messages) - mbox.gz / Atom

[vfs] 8bb3c61baf: vm-scalability.median -23.7% regression
 2019-09-08 23:47 UTC  (2+ messages) - mbox.gz / Atom

[PATCH v2 0/6] ext4: port direct IO to iomap infrastructure
 2019-09-08 23:32 UTC  (8+ messages) - mbox.gz / Atom
` [PATCH v2 1/6] ext4: introduce direct IO read path using "
` [PATCH v2 2/6] ext4: move inode extension/truncate code out from ext4_iomap_end()
` [PATCH v2 3/6] iomap: modify ->end_io() calling convention
` [PATCH v2 4/6] ext4: reorder map.m_flags checks in ext4_iomap_begin()
` [PATCH v2 5/6] ext4: introduce direct IO write path using iomap infrastructure
` [PATCH v2 6/6] ext4: cleanup legacy buffer_head direct IO code

[PATCH bpf-next v10 00/10] Landlock LSM: Toward unprivileged sandboxing
 2019-09-08 22:19 UTC  (6+ messages) - mbox.gz / Atom
` [PATCH bpf-next v10 06/10] bpf,landlock: Add a new map type: inode

[PATCH v12 00/12] namei: openat2(2) path resolution restrictions
 2019-09-08 16:24 UTC  (19+ messages) - mbox.gz / Atom
` [PATCH v12 01/12] lib: introduce copy_struct_{to,from}_user helpers
` [PATCH v12 11/12] open: openat2(2) syscall

[PATCH erofs-utils] build: cure compiler warnings
 2019-09-08 15:53 UTC  - mbox.gz / Atom

[PATCH 00/18] virtiofs: Fix various races and cleanups round 1
 2019-09-08 11:53 UTC  (55+ messages) - mbox.gz / Atom
` [PATCH 01/18] virtiofs: Remove request from processing list before calling end
` [PATCH 02/18] virtiofs: Check whether hiprio queue is connected at submission time
` [PATCH 03/18] virtiofs: Pass fsvq instead of vq as parameter to virtio_fs_enqueue_req
` [PATCH 04/18] virtiofs: Check connected state for VQ_REQUEST queue as well
` [PATCH 05/18] Maintain count of in flight requests for VQ_REQUEST queue
` [PATCH 06/18] virtiofs: ->remove should not clean virtiofs fuse devices
` [PATCH 07/18] virtiofs: Stop virtiofs queues when device is being removed
` [PATCH 08/18] virtiofs: Drain all pending requests during ->remove time
  ` [Virtio-fs] "
` [PATCH 09/18] virtiofs: Add an helper to start all the queues
` [PATCH 10/18] virtiofs: Do not use device managed mem for virtio_fs and virtio_fs_vq
` [PATCH 11/18] virtiofs: stop and drain queues after sending DESTROY
` [PATCH 12/18] virtiofs: Use virtio_fs_free_devs() in error path
` [PATCH 13/18] virtiofs: Do not access virtqueue in request submission path
` [PATCH 14/18] virtiofs: Add a fuse_iqueue operation to put() reference
` [PATCH 15/18] virtiofs: Make virtio_fs object refcounted
  ` [Virtio-fs] "
` [PATCH 16/18] virtiofs: Use virtio_fs_mutex for races w.r.t ->remove and mount path
  ` [Virtio-fs] "
` [PATCH 17/18] virtiofs: Remove TODO to quiesce/end_requests
` [PATCH 18/18] virtiofs: Remove TODO item from virtio_fs_free_devs()
      ` [Virtio-fs] [PATCH 00/18] virtiofs: Fix various races and cleanups round 1

[PATCH] drivers/staging/exfat - by default, prohibit mount of fat/vfat
 2019-09-08 10:50 UTC  (10+ messages) - mbox.gz / Atom

[PATCH v3] ceph: Convert ceph to use the new mount API
 2019-09-07 15:07 UTC  (4+ messages) - mbox.gz / Atom

[PATCH] FS: timerfd: Fix unexpected return value of timerfd_read function. 'hrtimer_forward_now()' returns zero due to bigger backward time drift. This causes timerfd_read to return 0. As per man page, read on timerfd is not expected to return 0. This patch fixes this problem. Signed-off-by: Arul Jeniston <arul.jeniston@gmail.com>
 2019-09-07 14:38 UTC  (15+ messages) - mbox.gz / Atom
  ` [PATCH] FS: timerfd: Fix unexpected return value of timerfd_read function

[PATCH v8 00/13] nvmet: add target passthru commands support
 2019-09-07  0:00 UTC  (23+ messages) - mbox.gz / Atom
` [PATCH v8 01/13] nvme-core: introduce nvme_ctrl_get_by_path()
` [PATCH v8 02/13] nvme-core: export existing ctrl and ns interfaces
` [PATCH v8 03/13] nvmet: add return value to nvmet_add_async_event()
` [PATCH v8 04/13] nvmet: make nvmet_copy_ns_identifier() non-static
` [PATCH v8 05/13] nvmet-passthru: update KConfig with config passthru option
` [PATCH v8 08/13] nvmet-core: don't check the data len for pt-ctrl
` [PATCH v8 09/13] nvmet-tcp: don't check data_len in nvmet_tcp_map_data()
` [PATCH v8 10/13] nvmet-configfs: introduce passthru configfs interface
` [PATCH v8 11/13] block: don't check blk_rq_is_passthrough() in blk_do_io_stat()
` [PATCH v8 12/13] block: call blk_account_io_start() in blk_execute_rq_nowait()
` [PATCH v8 13/13] nvmet-passthru: support block accounting

[PATCH v4 0/15] CoW support for iomap
 2019-09-06 23:28 UTC  (16+ messages) - mbox.gz / Atom
` [PATCH 01/15] iomap: Use a srcmap for a read-modify-write I/O
` [PATCH 02/15] iomap: Read page from srcmap if IOMAP_F_COW is set
` [PATCH 04/15] btrfs: Add a simple buffered iomap write
` [PATCH 11/15] iomap: use a function pointer for dio submits
` [PATCH 15/15] xfs: Use the new iomap infrastructure for CoW

[Q] gfs2: mmap write vs. punch_hole consistency
 2019-09-06 23:15 UTC  (4+ messages) - mbox.gz / Atom

[PATCH 0/2] Btrfs: add interface for writing compressed extents directly
 2019-09-06 21:27 UTC  (8+ messages) - mbox.gz / Atom
` [PATCH 2/2] btrfs: add ioctl for directly writing compressed data

[PATCH 00/11] Keyrings, Block and USB notifications [ver #8]
 2019-09-06 21:19 UTC  (24+ messages) - mbox.gz / Atom
  ` Why add the general notification queue and its sources

fuse / work,mount coordination
 2019-09-06 20:24 UTC  (3+ messages) - mbox.gz / Atom

[GIT PULL] configfs fixes for 5.3
 2019-09-06 20:00 UTC  (2+ messages) - mbox.gz / Atom

[PATCH] init/do_mounts.c: add virtiofs root fs support
 2019-09-06 19:16 UTC  (2+ messages) - mbox.gz / Atom

[PATCH] unicode: make array 'token' static const, makes object smaller
 2019-09-06 15:31 UTC  (2+ messages) - mbox.gz / Atom

[PATCH 1/1] vfs: Really check for inode ptr in lookup_fast
 2019-09-06 13:56 UTC  - mbox.gz / Atom

[PATCH v4 00/16] virtio-fs: shared file system for virtual machines
 2019-09-06 13:52 UTC  (6+ messages) - mbox.gz / Atom
` [PATCH v4 15/16] virtio-fs: add virtiofs filesystem

[PATCH] fs: fs_parser: remove fs_parameter_description name field
 2019-09-06 13:01 UTC  (5+ messages) - mbox.gz / Atom

[PATCH 01/13] vfs: verify param type in vfs_parse_sb_flag()
 2019-09-06  7:28 UTC  (4+ messages) - mbox.gz / Atom

possible deadlock in io_submit_one (2)
 2019-09-06  6:58 UTC  (6+ messages) - mbox.gz / Atom
  ` [PATCH] fuse: disable irqs for fuse_iqueue::waitq.lock

[PATCH V2] proc: fix ubsan warning in mem_lseek
 2019-09-06  5:48 UTC  (2+ messages) - mbox.gz / Atom

[RFC] - vfs: Null pointer dereference issue with symlink create and read of symlink
 2019-09-06  5:17 UTC  (5+ messages) - mbox.gz / Atom

[PATCH vfs/for-next] vfs: fix vfs_get_single_reconf_super error handling
 2019-09-06  3:01 UTC  (2+ messages) - mbox.gz / Atom

[PATCH] vfs: set fs_context::user_ns for reconfigure
 2019-09-06  2:59 UTC  (3+ messages) - mbox.gz / Atom

Possible FS race condition between iterate_dir and d_alloc_parallel
 2019-09-06  2:32 UTC  (8+ messages) - mbox.gz / Atom

[PATCH 2/9] cachefiles: drop direct usage of ->bmap method
 2019-09-05 22:44 UTC  (10+ messages) - mbox.gz / Atom
    ` [PATCH 0/9 V5] New ->fiemap infrastructure and ->bmap removal

[PATCH v2] ceph: Convert ceph to use the new mount API
 2019-09-05 21:05 UTC  (2+ messages) - mbox.gz / Atom

page:   latest

Linux-Fsdevel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-fsdevel/0 linux-fsdevel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-fsdevel linux-fsdevel/ https://lore.kernel.org/linux-fsdevel \
		linux-fsdevel@vger.kernel.org linux-fsdevel@archiver.kernel.org
	public-inbox-index linux-fsdevel


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-fsdevel


AGPL code for this site: git clone https://public-inbox.org/ public-inbox