Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <brauner@kernel.org>,
	Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
	David Howells <dhowells@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Steve French <stfrench@microsoft.com>
Subject: Re: linux-next: manual merge of the vfs-brauner tree with the cifs tree
Date: Fri, 6 Sep 2024 09:38:21 +1000	[thread overview]
Message-ID: <20240906093821.30c5114e@canb.auug.org.au> (raw)
In-Reply-To: <20240906084637.295241d1@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]

Hi all,

On Fri, 6 Sep 2024 08:46:37 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the vfs-brauner tree got a conflict in:
> 
>   fs/smb/client/cifssmb.c
> 
> between commit:
> 
>   a68c74865f51 ("cifs: Fix SMB1 readv/writev callback in the same way as SMB2/3")
> 
> from the cifs tree and commit:
> 
>   0fda1f8c6bf8 ("netfs: Speed up buffered reading")
> 
> from the vfs-brauner tree.
> 
> I fixed it up (I used the former as it is (supposedly) a much newer patch)
> 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.

The fixup ended up being as below.

-- 
Cheers,
Stephen Rothwell

diff --cc fs/smb/client/cifssmb.c
index cfae2e918209,04f2a5441a89..790b3f5ea64b
--- a/fs/smb/client/cifssmb.c
+++ b/fs/smb/client/cifssmb.c
@@@ -1261,16 -1261,6 +1261,15 @@@ openRetry
  	return rc;
  }
  
 +static void cifs_readv_worker(struct work_struct *work)
 +{
 +	struct cifs_io_subrequest *rdata =
 +		container_of(work, struct cifs_io_subrequest, subreq.work);
 +
- 	netfs_subreq_terminated(&rdata->subreq,
- 				(rdata->result == 0 || rdata->result == -EAGAIN) ?
- 				rdata->got_bytes : rdata->result, true);
++	rdata->subreq.transferred += rdata->got_bytes;
++	netfs_read_subreq_terminated(&rdata->subreq, rdata->result, true);
 +}
 +
  static void
  cifs_readv_callback(struct mid_q_entry *mid)
  {

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-09-05 23:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 22:46 linux-next: manual merge of the vfs-brauner tree with the cifs tree Stephen Rothwell
2024-09-05 23:38 ` Stephen Rothwell [this message]
2024-09-06  1:48   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-09-12 22:59 Stephen Rothwell
2024-09-06  1:18 Stephen Rothwell
2024-02-26  0:03 Stephen Rothwell
2024-03-12  4:00 ` Stephen Rothwell
2024-02-07 22:59 Stephen Rothwell

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=20240906093821.30c5114e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --cc=stfrench@microsoft.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