target-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>,
	 Josef Bacik <josef@toxicpanda.com>,
	David Howells <dhowells@redhat.com>,
	 Miklos Szeredi <miklos@szeredi.hu>,
	Al Viro <viro@zeniv.linux.org.uk>,
	 linux-fsdevel@vger.kernel.org, linux-scsi@vger.kernel.org,
	 target-devel@vger.kernel.org, stable@vger.kernel.org,
	 Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] scsi: target: core: add missing file_{start,end}_write()
Date: Fri, 24 Nov 2023 09:54:49 +0200	[thread overview]
Message-ID: <CAOQ4uxj6BBSgGKWQn=2ocsL_rd-PbjPAiK2w9rsqnxpNamxr9g@mail.gmail.com> (raw)
In-Reply-To: <2f3bf38b-a803-43e5-a9b9-54a88f837125@kernel.dk>

On Thu, Nov 23, 2023 at 10:04 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> On 11/23/23 2:20 AM, Amir Goldstein wrote:
> > The callers of vfs_iter_write() are required to hold file_start_write().
> > file_start_write() is a no-op for the S_ISBLK() case, but it is really
> > needed when the backing file is a regular file.
> >
> > We are going to move file_{start,end}_write() into vfs_iter_write(), but
> > we need to fix this first, so that the fix could be backported to stable
> > kernels.
>
> Reviewed-by: Jens Axboe <axboe@kernel.dk>
>

Christian,

Shall we just stash this at the bottom of vfs.rw and fixup
"move file_{start,end}_write() into vfs_iter_write()" patch?

I see no strong reason to expedite a fix for something rare
that has been broken for a long time.

If Martin decides to expedite it, we can alway rebase vfs.rw
once the fix is merged to master.

Thanks,
Amir.

  reply	other threads:[~2023-11-24  7:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23  9:20 [PATCH] scsi: target: core: add missing file_{start,end}_write() Amir Goldstein
2023-11-23 15:16 ` Christoph Hellwig
2023-11-23 20:04 ` Jens Axboe
2023-11-24  7:54   ` Amir Goldstein [this message]
2023-11-24  8:24     ` Christian Brauner
2023-11-24 22:46       ` Martin K. Petersen
2023-11-24  8:23 ` Christian Brauner

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='CAOQ4uxj6BBSgGKWQn=2ocsL_rd-PbjPAiK2w9rsqnxpNamxr9g@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=miklos@szeredi.hu \
    --cc=stable@vger.kernel.org \
    --cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).