similar to: [PATCH] ocfs2: reduce ioctl stack usage

On Tue, Apr 18, 2023 at 05:37:06PM +0800, Joseph Qi wrote: > Andrew picked ocfs2 patches into -mm tree before. Yup and that's fine obviously, but this belongs to fs/ and we're aiming to take fs/ stuff through the dedicated fs trees going forward. Thanks! Christian > > Thanks, > Joseph > > On 4/18/23 5:17 PM, Christian Brauner wrote: > > > > On Mon, 17

On Thu, Apr 20, 2023 at 2:34?AM Christian Brauner <brauner at kernel.org> wrote: > I think I might not have communicated as clearly as I should have. > Simply because I naively assumed that this is unproblematic. > > By "we" I mean people responsible for "fs/" which now happens to also > include me. So the goal of this is for patches falling under fs/ to

On Wed, Apr 19, 2023 at 02:21:59PM -0700, Andrew Morton wrote: > On Wed, 19 Apr 2023 10:00:15 +0800 Joseph Qi <joseph.qi at linux.alibaba.com> wrote: > > > > > > > On 4/18/23 8:56 PM, Christian Brauner wrote: > > > On Tue, Apr 18, 2023 at 05:37:06PM +0800, Joseph Qi wrote: > > >> Andrew picked ocfs2 patches into -mm tree before. > > >

On 4/18/23 8:56 PM, Christian Brauner wrote: > On Tue, Apr 18, 2023 at 05:37:06PM +0800, Joseph Qi wrote: >> Andrew picked ocfs2 patches into -mm tree before. > Yup and that's fine obviously, but this belongs to fs/ and we're aiming > to take fs/ stuff through the dedicated fs trees going forward. Either is fine for me. Hi Andrew, what's your opinion? Thanks, Joseph

On Wed, 19 Apr 2023 10:00:15 +0800 Joseph Qi <joseph.qi at linux.alibaba.com> wrote: > > > On 4/18/23 8:56 PM, Christian Brauner wrote: > > On Tue, Apr 18, 2023 at 05:37:06PM +0800, Joseph Qi wrote: > >> Andrew picked ocfs2 patches into -mm tree before. > > Yup and that's fine obviously, but this belongs to fs/ and we're aiming > > to take fs/

On Tue, Apr 18, 2023 at 02:56:38PM +0200, Christian Brauner wrote: > On Tue, Apr 18, 2023 at 05:37:06PM +0800, Joseph Qi wrote: > > Andrew picked ocfs2 patches into -mm tree before. > > Yup and that's fine obviously, but this belongs to fs/ and we're aiming > to take fs/ stuff through the dedicated fs trees going forward. Er... Assuming that there *is* an active fs

The new code is dedicated to calculate free inodes number of all inode_allocs, then return the info to userpace in terms of an array. Specially, flag 'OCFS2_INFO_FL_NON_COHERENT', manipulated by '--cluster-coherent' from userspace, is now going to be involved. setting the flag on means no cluster coherency considered, usually, userspace tools choose none-coherency strategy by

On Thu, Mar 23, 2023 at 12:50:49PM +0100, Christian Brauner wrote: > On Thu, Mar 23, 2023 at 07:43:04AM -0400, Michael S. Tsirkin wrote: > > On Thu, Mar 23, 2023 at 11:44:45AM +0100, Christian Brauner wrote: > > > On Thu, Mar 23, 2023 at 03:37:19AM -0400, Michael S. Tsirkin wrote: > > > > On Wed, Mar 22, 2023 at 01:56:05PM -0500, Mike Christie wrote: > > >

We're currently support two paths from VFS to preallocate unwritten extents(from FS_IOC_RESVSP, or fallocate()), likewise, behavior of punching-hole should be treated as the same, this patch tries to teach file_ioctl() to handle FS_IOC_UNRESVSP, underlying filesystem like ocfs2 is wise enough to do the rest of work;-) Signed-off-by: Tristan Ye <tristan.ye at oracle.com> --- fs/ioctl.c

We're currently support two paths from VFS to preallocate unwritten extents(from FS_IOC_RESVSP, or fallocate()), likewise, behavior of punching-hole should be treated as the same, this patch tries to teach file_ioctl() to handle FS_IOC_UNRESVSP, underlying filesystem like ocfs2 is wise enough to do the rest of work;-) Signed-off-by: Tristan Ye <tristan.ye at oracle.com> --- fs/ioctl.c

Some people contribute to someone specific fs testing mostly, record some of them as Reviewer. Signed-off-by: Zorro Lang <zlang at kernel.org> --- If someone doesn't want to be in cc list of related fstests patch, please reply this email, I'll remove that reviewer line. Or if someone else (who contribute to fstests very much) would like to a specific reviewer, nominate yourself to

Hey everyone, after we finished the introduction of the new posix acl api last cycle we still left the generic POSIX ACL xattr handler around for two reasons. First, because a few filesystems relied on the ->list() method of the generic POSIX ACL xattr handlers in their ->listxattr() inode operation. Second, during inode initalization in inode_init_always() the registered xattr handlers in

On Mon, Jan 30, 2023 at 10:10:52AM +0100, Christian Brauner wrote: > However, a few filesystems still rely on the ->list() method of the > generix POSIX ACL xattr handlers in their ->listxattr() inode operation. > This is a very limited set of filesystems. For most of them there is no > dependence on the generic POSIX ACL xattr handler in any way. > > In addition, during

On 3/11/23 2:53 AM, Christian Brauner wrote: > On Fri, Mar 10, 2023 at 04:03:24PM -0600, Mike Christie wrote: >> This has us pass in the thread's name during creation in kernel_thread. >> >> Signed-off-by: Mike Christie <michael.christie at oracle.com> >> --- >> kernel/kthread.c | 35 ++++++++++++++--------------------- >> 1 file changed, 14

On 01.06.23 12:47, Christian Brauner wrote: > On Thu, Jun 01, 2023 at 09:58:38AM +0200, Thorsten Leemhuis wrote: >> On 19.05.23 14:15, Christian Brauner wrote: >>> On Thu, May 18, 2023 at 10:25:11AM +0200, Christian Brauner wrote: >>>> On Wed, May 17, 2023 at 07:09:12PM -0500, Mike Christie wrote: >>>>> This patch allows the vhost and vhost_task code to

On 6/1/23 5:47 AM, Christian Brauner wrote: > On Thu, Jun 01, 2023 at 09:58:38AM +0200, Thorsten Leemhuis wrote: >> On 19.05.23 14:15, Christian Brauner wrote: >>> On Thu, May 18, 2023 at 10:25:11AM +0200, Christian Brauner wrote: >>>> On Wed, May 17, 2023 at 07:09:12PM -0500, Mike Christie wrote: >>>>> This patch allows the vhost and vhost_task code to

On 19.05.23 14:15, Christian Brauner wrote: > On Thu, May 18, 2023 at 10:25:11AM +0200, Christian Brauner wrote: >> On Wed, May 17, 2023 at 07:09:12PM -0500, Mike Christie wrote: >>> This patch allows the vhost and vhost_task code to use CLONE_THREAD, >>> CLONE_SIGHAND and CLONE_FILES. It's a RFC because I didn't do all the >>> normal testing,

On Thu, Jun 1, 2023 at 6:47?AM Christian Brauner <brauner at kernel.org> wrote: > > @Mike, do you want to prepare an updated version of the temporary fix. > If @Linus prefers to just apply it directly he can just grab it from the > list rather than delaying it. Make sure to grab a Co-developed-by line > on this, @Mike. Yeah, let's apply the known "fix the immediate

The patch titled Subject: fs-buffer-clean-up-block_commit_write-fix has been added to the -mm mm-unstable branch. Its filename is fs-buffer-clean-up-block_commit_write-fix.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/fs-buffer-clean-up-block_commit_write-fix.patch This patch will later appear in the

Signed-off-by: Dave Kleikamp <dave.kleikamp at oracle.com> Acked-by: Joel Becker <jlbec at evilplan.org> Cc: Zach Brown <zab at zabbo.net> Cc: Mark Fasheh <mfasheh at suse.com> Cc: ocfs2-devel at oss.oracle.com --- fs/ocfs2/aops.h | 2 +- fs/ocfs2/file.c | 55 ++++++++++++++++++++++---------------------------- fs/ocfs2/ocfs2_trace.h | 6 +++--- 3 files