All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Zheng Hacker <hackerzheng666@gmail.com>
Cc: Zheng Wang <zyytlz.wz@163.com>,
	dimitri.sivanich@hpe.com, arnd@arndb.de,
	linux-kernel@vger.kernel.org, alex000young@gmail.com,
	security@kernel.org
Subject: Re: [PATCH] misc: sgi-gru: fix use-after-free error in gru_set_context_option, gru_fault and gru_handle_user_call_os
Date: Tue, 27 Sep 2022 18:36:55 +0200	[thread overview]
Message-ID: <YzMmp9llFUN1yUDH@kroah.com> (raw)
In-Reply-To: <CAJedcCxGkz6i2LeCGWcHgU7P2n1TeB9gKVZCzmjPPJK=hhsfLA@mail.gmail.com>

Please do not top-post.

On Tue, Sep 27, 2022 at 10:12:58PM +0800, Zheng Hacker wrote:
> Hi Greg,
> 
> I've resent the patch. Could you please review it and apply if there
> is no more problem?

I do not see any new submission, please provide the lore.kernel.org link
of it.

thanks,

greg k-h

  reply	other threads:[~2022-09-27 16:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26  4:36 [PATCH] misc: sgi-gru: fix use-after-free error in gru_set_context_option, gru_fault and gru_handle_user_call_os Zheng Wang
2022-09-26  8:36 ` Greg KH
2022-09-27 14:12   ` Zheng Hacker
2022-09-27 16:36     ` Greg KH [this message]
2022-09-28  3:03       ` Zheng Hacker
2022-10-02 11:25         ` Zheng Hacker
2022-10-02 14:14           ` Greg KH
2022-10-03  4:35             ` Zheng Hacker
  -- strict thread matches above, loose matches on Subject: below --
2022-09-26  4:31 Zheng Wang
2022-09-19 14:32 Zheng Wang
2022-09-22  3:00 ` Zheng Hacker
2022-09-24 12:54 ` Greg KH
2022-09-26  2:41   ` Zheng Hacker
     [not found] <tencent_45DC133D0F8DBD599F40D6E228B9305B240A@qq.com>
2022-09-16 10:02 ` Greg KH
     [not found] <tencent_48738CD5589B4162E0D0B9D85B84DCD33C0A@qq.com>
2022-09-16  8:15 ` Greg KH
2022-09-16 15:18   ` Zheng Hacker
2022-09-16 15:20   ` Zheng Hacker
2022-09-16 15:33   ` Zheng Hacker

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=YzMmp9llFUN1yUDH@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alex000young@gmail.com \
    --cc=arnd@arndb.de \
    --cc=dimitri.sivanich@hpe.com \
    --cc=hackerzheng666@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@kernel.org \
    --cc=zyytlz.wz@163.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 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.