linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the vfs tree with the origin tree
@ 2022-08-03 12:18 broonie
  2022-08-03 14:14 ` Jens Axboe
  0 siblings, 1 reply; 2+ messages in thread
From: broonie @ 2022-08-03 12:18 UTC (permalink / raw)
  Cc: Al Viro, Jens Axboe, Linux Kernel Mailing List, Linux Next Mailing List

Hi all,

Today's linux-next merge of the vfs tree got a conflict in:

  fs/io_uring.c

between commit:

  ed29b0b4fd835 ("io_uring: move to separate directory")

from the origin tree and commit:

  164f4064ca81e ("keep iocb_flags() result cached in struct file")

from the vfs tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --git a/io_uring/rw.c b/io_uring/rw.c
index 2b784795103cc..b20ba87e4926f 100644
--- a/io_uring/rw.c
+++ b/io_uring/rw.c
@@ -661,7 +661,7 @@ static int io_rw_init_file(struct io_kiocb *req, fmode_t mode)
 	if (!io_req_ffs_set(req))
 		req->flags |= io_file_get_flags(file) << REQ_F_SUPPORT_NOWAIT_BIT;
 
-	kiocb->ki_flags = iocb_flags(file);
+	kiocb->ki_flags = file->f_iocb_flags;
 	ret = kiocb_set_rw_flags(kiocb, rw->flags);
 	if (unlikely(ret))
 		return ret;

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: linux-next: manual merge of the vfs tree with the origin tree
  2022-08-03 12:18 linux-next: manual merge of the vfs tree with the origin tree broonie
@ 2022-08-03 14:14 ` Jens Axboe
  0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2022-08-03 14:14 UTC (permalink / raw)
  To: broonie; +Cc: Al Viro, Linux Kernel Mailing List, Linux Next Mailing List

On 8/3/22 6:18 AM, broonie@kernel.org wrote:
> Hi all,
> 
> Today's linux-next merge of the vfs tree got a conflict in:
> 
>   fs/io_uring.c
> 
> between commit:
> 
>   ed29b0b4fd835 ("io_uring: move to separate directory")
> 
> from the origin tree and commit:
> 
>   164f4064ca81e ("keep iocb_flags() result cached in struct file")
> 
> from the vfs tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
> 
> diff --git a/io_uring/rw.c b/io_uring/rw.c
> index 2b784795103cc..b20ba87e4926f 100644
> --- a/io_uring/rw.c
> +++ b/io_uring/rw.c
> @@ -661,7 +661,7 @@ static int io_rw_init_file(struct io_kiocb *req, fmode_t mode)
>  	if (!io_req_ffs_set(req))
>  		req->flags |= io_file_get_flags(file) << REQ_F_SUPPORT_NOWAIT_BIT;
>  
> -	kiocb->ki_flags = iocb_flags(file);
> +	kiocb->ki_flags = file->f_iocb_flags;
>  	ret = kiocb_set_rw_flags(kiocb, rw->flags);
>  	if (unlikely(ret))
>  		return ret;

That's the right resolution, mentioned that in my pull request as well.

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-08-03 14:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-03 12:18 linux-next: manual merge of the vfs tree with the origin tree broonie
2022-08-03 14:14 ` Jens Axboe

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).