mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: "João Paredes" <joaommp@yahoo.com>, liaoyuanhong@vivo.com
Cc: jfs-discussion@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] JFS: always load filesystem UUID during mount
Date: Mon, 16 Mar 2026 16:22:43 -0500	[thread overview]
Message-ID: <88cdc52d-101f-4233-96e6-b6de8bed00c7@oracle.com> (raw)
In-Reply-To: <20260302025539.299524-1-joaommp@yahoo.com>

On 3/1/26 8:55PM, João Paredes wrote:
> The filesystem UUID was only being loaded into super_block sb when an
> external journal device was in use. When mounting without an external
> journal, the UUID remained unset, which prevented the computation of
> a filesystem ID (fsid), which could be confirmed via `stat -f -c "%i"`
> and thus user space could not use fanotify correctly.
> 
> A missing filesystem ID causes fanotify to return ENODEV when marking
> the filesystem for events like FAN_CREATE, FAN_DELETE, FAN_MOVED_TO,
> and FAN_MOVED_FROM. As a result, applications relying on fanotify
> could not monitor these events on JFS filesystems without an external
> journal.
> 
> Moved the UUID initialization so it is always performed during mount,
> ensuring the superblock UUID is consistently available.
> 
> Signed-off-by: João Paredes <joaommp@yahoo.com>

Applied to jfs-next.

Thanks!
Shaggy

> ---
>   fs/jfs/jfs_mount.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/jfs/jfs_mount.c b/fs/jfs/jfs_mount.c
> index 52e6b58c5dbd..dac822f15070 100644
> --- a/fs/jfs/jfs_mount.c
> +++ b/fs/jfs/jfs_mount.c
> @@ -378,11 +378,12 @@ static int chkSuper(struct super_block *sb)
>   	sbi->nbperpage = PSIZE >> sbi->l2bsize;
>   	sbi->l2nbperpage = L2PSIZE - sbi->l2bsize;
>   	sbi->l2niperblk = sbi->l2bsize - L2DISIZE;
> +	uuid_copy(&sbi->uuid, &j_sb->s_uuid);
> +
>   	if (sbi->mntflag & JFS_INLINELOG)
>   		sbi->logpxd = j_sb->s_logpxd;
>   	else {
>   		sbi->logdev = new_decode_dev(le32_to_cpu(j_sb->s_logdev));
> -		uuid_copy(&sbi->uuid, &j_sb->s_uuid);
>   		uuid_copy(&sbi->loguuid, &j_sb->s_loguuid);
>   	}
>   	sbi->fsckpxd = j_sb->s_fsckpxd;


      reply	other threads:[~2026-03-16 21:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260302025539.299524-1-joaommp.ref@yahoo.com>
2026-03-02  2:55 ` João Paredes
2026-03-16 21:22   ` Dave Kleikamp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=88cdc52d-101f-4233-96e6-b6de8bed00c7@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=joaommp@yahoo.com \
    --cc=liaoyuanhong@vivo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®