mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Yangtao Li <frank.li@vivo.com>,
	axboe@kernel.dk, aivazian.tigran@gmail.com,
		viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
	linkinjeon@kernel.org, 	sj1557.seo@samsung.com,
	yuezhang.mo@sony.com, glaubitz@physik.fu-berlin.de,
		shaggy@kernel.org, konishi.ryusuke@gmail.com,
		almaz.alexandrovich@paragon-software.com, me@bobcopeland.com,
		willy@infradead.org, josef@toxicpanda.com, kovalev@altlinux.org,
	dave@stgolabs.net, 	mhocko@suse.com, chentaotao@didiglobal.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	 jfs-discussion@lists.sourceforge.net,
	linux-nilfs@vger.kernel.org,  ntfs3@lists.linux.dev,
	linux-karma-devel@lists.sourceforge.net,  bpf@vger.kernel.org
Subject: Re: [PATCH 3/4] hfsplus: enable uncached buffer io support
Date: Fri, 04 Jul 2025 10:45:27 -0700	[thread overview]
Message-ID: <3c4ac1ab5f7afbbd745f88c595ee1465fc2e9ac6.camel@dubeyko.com> (raw)
In-Reply-To: <20250626173023.2702554-4-frank.li@vivo.com>

On Thu, 2025-06-26 at 11:30 -0600, Yangtao Li wrote:
> Now cont_write_begin() support DONTCACHE mode, let's set
> FOP_DONTCACHE
> flag to enable uncached buffer io support for hfsplus.
> 
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
>  fs/hfsplus/inode.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/fs/hfsplus/inode.c b/fs/hfsplus/inode.c
> index 26cc150856b9..b790ffe92019 100644
> --- a/fs/hfsplus/inode.c
> +++ b/fs/hfsplus/inode.c
> @@ -372,6 +372,7 @@ static const struct file_operations
> hfsplus_file_operations = {
>  	.open		= hfsplus_file_open,
>  	.release	= hfsplus_file_release,
>  	.unlocked_ioctl = hfsplus_ioctl,
> +	.fop_flags	= FOP_DONTCACHE,
>  };
>  
>  struct inode *hfsplus_new_inode(struct super_block *sb, struct inode
> *dir,

The same question for HFS+. Because, it is again old and pretty
obsolete file system. :) The main use-case is simply support the
capability to mount HFS+ volume is created under Mac OS X, for example,
and to access the data there. What is the point to support this feature
in HFS+? Currently, around 200 xfstests fails in HFS/HFS+. We even
cannot test any new functionality properly. And guys reports bugs in
existing functionality. We need to be focused on this right now. Sorry,
HFS/HFS+ is not so good ground for implementing new features. :)
We really need to stabilize the existing functionality right now. And
we have a lot of work yet. :) 

Thanks,
Slava. 

  reply	other threads:[~2025-07-04 17:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26 17:30 [PATCH 0/4] hfs/hfsplus: add " Yangtao Li
2025-06-26 17:30 ` [PATCH 1/4] block: Add struct kiocb pointer to block_write_begin() Yangtao Li
2025-06-26 17:30 ` [PATCH 2/4] fs/buffer: parse IOCB_DONTCACHE flag in block_write_begin() Yangtao Li
2025-07-04 17:29   ` Viacheslav Dubeyko
2025-06-26 17:30 ` [PATCH 3/4] hfsplus: enable uncached buffer io support Yangtao Li
2025-07-04 17:45   ` Viacheslav Dubeyko [this message]
2025-06-26 17:30 ` [PATCH 4/4] hfs: " Yangtao Li
2025-07-04 17:37   ` Viacheslav Dubeyko

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=3c4ac1ab5f7afbbd745f88c595ee1465fc2e9ac6.camel@dubeyko.com \
    --to=slava@dubeyko.com \
    --cc=aivazian.tigran@gmail.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=axboe@kernel.dk \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=chentaotao@didiglobal.com \
    --cc=dave@stgolabs.net \
    --cc=frank.li@vivo.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=jack@suse.cz \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=josef@toxicpanda.com \
    --cc=konishi.ryusuke@gmail.com \
    --cc=kovalev@altlinux.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-karma-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=mhocko@suse.com \
    --cc=ntfs3@lists.linux.dev \
    --cc=shaggy@kernel.org \
    --cc=sj1557.seo@samsung.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=yuezhang.mo@sony.com \
    /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®