All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Metzmacher <metze-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 00/10] SMB2 brlocks, leases and multicredit io
Date: Tue, 21 Aug 2012 11:10:48 +0200	[thread overview]
Message-ID: <k0vjao$hck$1@ger.gmane.org> (raw)
In-Reply-To: <1345488180-5942-1-git-send-email-pshilovsky-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>

Hi Pavel,

> This is a patchset that includes the rest of SMB2 changes: brlocks, leases and multicredit io.
> 
> The changes are applied on top of Jeff's recent patchset and can be found here:
> http://git.altlinux.org/people/piastry/public/?p=cifs-2.6.git;a=shortlog;h=refs/heads/smb2-dev-cork
> 
> Pavel Shilovsky (10):
>   CIFS: Improve byte-range locks handling
>   CIFS: Handle SMB2 lock flags
>   CIFS: Move brlock code to ops struct
>   CIFS: Add brlock support for SMB2
>   CIFS: Request SMB2.1 leases
>   CIFS: Add SMB2.1 lease break support
>   CIFS: Fix cache coherency for read oplock case
>   CIFS: Make use of multicredit write for SMB2
>   CIFS: Make use of multicredit reads for SMB2

Leases and multi-credit support are negotiated features in the capabilities
bits of the server. You should not rely on the dialect before you use them,
as there're servers which support SMB 2.1, but do not support leases or
multi-credit.

I think smb2_get_credit_size() should return 1 if the value in the header
is 0.

Regarding
+       /* random value */
+       req->ClientGUID[0] = req->ClientGUID[3] = req->ClientGUID[7] = 7;

I think you should use a random value here as the server uses this field
to detect if requests come from the same client. This should be a global
in the cifs.ok, which can change on reboot/module reload.

metze

  parent reply	other threads:[~2012-08-21  9:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20 18:42 [PATCH 00/10] SMB2 brlocks, leases and multicredit io Pavel Shilovsky
     [not found] ` <1345488180-5942-1-git-send-email-pshilovsky-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
2012-08-20 18:42   ` [PATCH 01/10] CIFS: Improve byte-range locks handling Pavel Shilovsky
2012-08-20 18:42   ` [PATCH 02/10] CIFS: Handle SMB2 lock flags Pavel Shilovsky
2012-08-20 18:42   ` [PATCH 03/10] CIFS: Move brlock code to ops struct Pavel Shilovsky
2012-08-20 18:42   ` [PATCH 04/10] CIFS: Add brlock support for SMB2 Pavel Shilovsky
2012-08-20 18:42   ` [PATCH 05/10] CIFS: Request SMB2.1 leases Pavel Shilovsky
2012-08-20 18:42   ` [PATCH 06/10] CIFS: Add SMB2.1 lease break support Pavel Shilovsky
2012-08-20 18:42   ` [PATCH 07/10] CIFS: Fix cache coherency for read oplock case Pavel Shilovsky
2012-08-20 18:42   ` [PATCH 08/10] CIFS: Make use of multicredit write for SMB2 Pavel Shilovsky
2012-08-20 18:42   ` [PATCH 09/10] CIFS: Make use of multicredit reads " Pavel Shilovsky
2012-08-20 18:43   ` [PATCH 10/10] CIFS: Add NTLMSSP sec type to defaults Pavel Shilovsky
2012-08-21  9:10   ` Stefan Metzmacher [this message]
2012-08-21 14:08     ` [PATCH 00/10] SMB2 brlocks, leases and multicredit io Pavel Shilovsky
     [not found]       ` <CAKywueRsBYRyCFMjWEhtTS5GP2PWqv4Y_W49q+Q+egBo-xCY3w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-22 13:47         ` Stefan (metze) Metzmacher

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='k0vjao$hck$1@ger.gmane.org' \
    --to=metze-eunubhrolfbytjvyw6ydsg@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.