Re: [Cluster-devel] [PATCH] dlm/recoverd: recheck kthread_should_stop() before schedule()

On Mon, Sep 25, 2017 at 03:47:50PM +0800, Guoqing Jiang wrote: > Call schedule() here could make the thread miss wake > up from kthread_stop(), so it is better to recheck > kthread_should_stop() before call schedule(), a symptom > happened when I run indefinite test (which mostly created >

[Cluster-devel] GFS2: Please pull patch tagged gfs2-for-linus-4.14-rc3

Hi Linus, Would you please pull this one-off patch from Andreas Gruenbacher that fixes a GFS2 regression? Thanks. Bob Peterson --- The following changes since commit 46c1e79fee417f151547aa46fae04ab06cb666f4: Merge branch 'perf-urgent-for-linus' of

Re: [Cluster-devel] [PATCH] gfs2: Always update inode ctime in set_acl

- Original Message - | Three-entry POSIX ACLs can be stored in the file mode permission bits, | with no need to store them in extended attributes. When a process sets | such a minimal ACL, the kernel updates the file mode like chmod does, | and removes any existing extended attributes for

Re: [Cluster-devel] [PATCH] gfs2: Clarify gfs2_block_map

- Original Message - | Add a comment about the logical block size for directories. Rename | "bsize" in gfs2_block_map to "factor". Fix a typo in the description of | metaptr1. | | Signed-off-by: Andreas Gruenbacher | --- | fs/gfs2/bmap.c | 14 ++ | 1

Re: [Cluster-devel] [PATCH] gfs2: Support negative atimes

- Original Message - | When inodes are read from disk, GFS2 will only update in-memory atimes | older than the on-disk atimes; this prevents atimes from going | backwards. The atimes of newly allocated inodes are initialized to 0. | This means that when an atime is explicitly set to a

Re: [Cluster-devel] [PATCH] gfs2: Update ctime in setflags ioctl

- Original Message - | The FS_IOC_SETFLAGS ioctl is supposed to update the inode ctime. | Fixes xfstests generic/277. | | Signed-off-by: Andreas Gruenbacher | --- | fs/gfs2/file.c | 1 + | 1 file changed, 1 insertion(+) Hi, Thanks. This is now pushed to the

[Cluster-devel] [PATCH] dlm/recoverd: recheck kthread_should_stop() before schedule()

Call schedule() here could make the thread miss wake up from kthread_stop(), so it is better to recheck kthread_should_stop() before call schedule(), a symptom happened when I run indefinite test (which mostly created clustered raid1, assemble it in other nodes, then stop them) of clustered raid.