archive mirror
 help / color / mirror / Atom feed
From: Paulo Alcantara <>
To: Steve French <>, CIFS <>
Subject: Re: [PATCH][CIFS] Clarify SMB1 code for POSIX Lock
Date: Wed, 07 Jul 2021 18:16:03 -0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Steve French <> writes:

> Another trivial (Coverity reported issue) patch ...
> Coverity also complains about the way we calculate the offset
> (starting from the address of a 4 byte array within the
> header structure rather than from the beginning of the struct
> plus 4 bytes) for SMB1 PosixLock. This changeset
> doesn't change the address but makes it slightly clearer.
> Addresses-Coverity: 711520 ("Out of bounds write")
> Signed-off-by: Steve French <>
> ---
>  fs/cifs/cifssmb.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

Reviewed-by: Paulo Alcantara (SUSE) <>

      reply	other threads:[~2021-07-07 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 19:07 [PATCH][CIFS] Clarify SMB1 code for POSIX Lock Steve French
2021-07-07 21:16 ` Paulo Alcantara [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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