From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: HexRabbit <h3xrabbit@gmail.com>,
sfrench@samba.org, senozhatsky@chromium.org, tom@talpey.com,
linux-cifs@vger.kernel.org
Subject: Re: [PATCH] ksmbd: fix slab-out-of-bounds read in smb2_handle_negotiate
Date: Wed, 17 May 2023 20:02:12 +0900 [thread overview]
Message-ID: <20230517110212.GA20467@google.com> (raw)
In-Reply-To: <CAKYAXd_V2RgWTHzrG-1A8kX+rpyyQ06=hX2s5AqwW8ERWaaE1w@mail.gmail.com>
On (23/05/17 19:17), Namjae Jeon wrote:
> > Signed-off-by: HexRabbit <h3xrabbit@gmail.com>
> Acked-by: Namjae Jeon <linkinjeon@kernel.org>
>
> Sergey will say, "Do we still have a requirement that there should be
> a real name in SoB?"
:) Thanks!
next prev parent reply other threads:[~2023-05-17 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 9:59 [PATCH] ksmbd: fix slab-out-of-bounds read in smb2_handle_negotiate HexRabbit
2023-05-17 10:17 ` Namjae Jeon
2023-05-17 11:02 ` Sergey Senozhatsky [this message]
2023-05-17 11:05 ` Sergey Senozhatsky
2023-05-17 11:13 ` Sergey Senozhatsky
[not found] ` <CAF3ZFef4gmEVZR5riwdB1bkB4CccziGw3g18cyz7Sim4xw+ZDw@mail.gmail.com>
2023-05-18 0:33 ` Sergey Senozhatsky
2023-05-18 8:43 ` Hex Rabbit
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=20230517110212.GA20467@google.com \
--to=senozhatsky@chromium.org \
--cc=h3xrabbit@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=sfrench@samba.org \
--cc=tom@talpey.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