From: Greg KH <gregkh@linuxfoundation.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v1] fs:dlm:Fix potential null pointer dereference on pointer
Date: Fri, 16 Jun 2023 08:15:35 +0200 [thread overview]
Message-ID: <2023061623-goofiness-composed-8806@gregkh> (raw)
In-Reply-To: <20230616024836.577-1-machel@vivo.com>
On Fri, Jun 16, 2023 at 10:48:24AM +0800, Wang Ming wrote:
> ________________________________
> ????????????????/??????????????????????????????????????????????????????????????????????????????????????????????????????????
> The contents of this message and any attachments may contain confidential and/or privileged information and are intended exclusively for the addressee(s). If you are not the intended recipient of this message or their agent, please note that any use, dissemination, copying, or storage of this message or its attachments is not allowed. If you receive this message in error, please notify the sender by reply the message or phone and delete this message, any attachments and any copies immediately.
> Thank you
Now deleted.
prev parent reply other threads:[~2023-06-16 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 2:48 [Cluster-devel] [PATCH v1] fs:dlm:Fix potential null pointer dereference on pointer Wang Ming
2023-06-16 6:15 ` Greg KH [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:
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=2023061623-goofiness-composed-8806@gregkh \
--to=gregkh@linuxfoundation.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).