mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Christian Brauner <brauner@kernel.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	 "linux-kernel@vger.kernel.org"	 <linux-kernel@vger.kernel.org>,
	Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>,
	 "frank.li@vivo.com"	 <frank.li@vivo.com>,
	"glaubitz@physik.fu-berlin.de"	 <glaubitz@physik.fu-berlin.de>,
	"viro@zeniv.linux.org.uk"	 <viro@zeniv.linux.org.uk>,
	"kees@kernel.org" <kees@kernel.org>
Subject: Re:  [PATCH 1/2] hfsplus: make splice write available again
Date: Fri, 06 Jun 2025 16:04:46 -0700	[thread overview]
Message-ID: <415dae31e51263864612eadfc5ce5699575ad2d8.camel@dubeyko.com> (raw)
In-Reply-To: <fa46baccde906c7e52b1d84264d284be1072ffcf.camel@ibm.com>

Hi Christian,

Could you please pick up the patch?

Thanks,
Slava.

On Thu, 2025-05-29 at 18:27 +0000, Viacheslav Dubeyko wrote:
> On Thu, 2025-05-29 at 08:00 -0600, Yangtao Li wrote:
> > Since 5.10, splice() or sendfile() return EINVAL. This was
> > caused by commit 36e2c7421f02 ("fs: don't allow splice read/write
> > without explicit ops").
> > 
> > This patch initializes the splice_write field in file_operations,
> > like
> > most file systems do, to restore the functionality.
> > 
> > Fixes: 36e2c7421f02 ("fs: don't allow splice read/write without
> > explicit ops")
> > 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 f331e9574217..c85b5802ec0f 100644
> > --- a/fs/hfsplus/inode.c
> > +++ b/fs/hfsplus/inode.c
> > @@ -368,6 +368,7 @@ static const struct file_operations
> > hfsplus_file_operations = {
> >  	.write_iter	= generic_file_write_iter,
> >  	.mmap		= generic_file_mmap,
> >  	.splice_read	= filemap_splice_read,
> > +	.splice_write	= iter_file_splice_write,
> >  	.fsync		= hfsplus_file_fsync,
> >  	.open		= hfsplus_file_open,
> >  	.release	= hfsplus_file_release,
> 
> Makes sense.
> 
> Reviewed-by: Viacheslav Dubeyko <slava@dubeyko.com>
> 
> Thanks,
> Slava.

      reply	other threads:[~2025-06-06 23:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 14:00 Yangtao Li
2025-05-29 14:00 ` [PATCH 2/2] hfs: " Yangtao Li
2025-05-29 18:28   ` Viacheslav Dubeyko
2025-06-06 23:04     ` Viacheslav Dubeyko
2025-05-29 18:27 ` [PATCH 1/2] hfsplus: " Viacheslav Dubeyko
2025-06-06 23:04   ` Viacheslav Dubeyko [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=415dae31e51263864612eadfc5ce5699575ad2d8.camel@dubeyko.com \
    --to=slava@dubeyko.com \
    --cc=Slava.Dubeyko@ibm.com \
    --cc=brauner@kernel.org \
    --cc=frank.li@vivo.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=kees@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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®