From: Petr Mladek <pmladek@suse.com>
To: "chengjian (D)" <cj.chengjian@huawei.com>
Cc: Jiri Kosina <jikos@kernel.org>,
"chenzefeng (A)" <chenzefeng2@huawei.com>,
"hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"jpoimboe@redhat.com" <jpoimboe@redhat.com>,
"sjenning@redhat.com" <sjenning@redhat.com>,
"vojtech@suse.com" <vojtech@suse.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"x86@kernel.org" <x86@kernel.org>,
"live-patching@vger.kernel.org" <live-patching@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Xiexiuqi (Xie XiuQi)" <xiexiuqi@huawei.com>
Subject: Re: [PATCH] x86: livepatch: Treat R_X86_64_PLT32 as R_X86_64_PC32
Date: Mon, 18 Feb 2019 10:22:18 +0100 [thread overview]
Message-ID: <20190218092218.3ltqt5uhvy4z23ny@pathway.suse.cz> (raw)
In-Reply-To: <d137b1a4-ae46-f529-15a0-cdc8fbfc6bbe@huawei.com>
On Mon 2019-02-18 13:29:11, chengjian (D) wrote:
> Hi,Jiri
>
>
> This patch should be merged into 4.4 stable,
>
> which still use klp_write_module_reloc.
>
>
> https://elixir.bootlin.com/linux/v4.4.174/source/arch/x86/kernel/livepatch.c
>
>
> ZeFeng may have sent a stable(4.4-y) patch to the wrong mail-list(mainline).
ZeFeng or Chengjian, please, send the patch once again with
stable@vger.kernel.org in CC and explanation that it is needed
only for 4.4 and why.
This thread is already too long and messed to be proceed
by stable people effectively.
Best Regards,
Petr
next prev parent reply other threads:[~2019-02-18 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 2:01 chenzefeng (A)
2019-02-15 7:28 ` Jiri Kosina
2019-02-15 8:17 ` 答复: " chenzefeng (A)
2019-02-15 9:05 ` Petr Mladek
2019-02-18 5:29 ` chengjian (D)
2019-02-18 9:22 ` Petr Mladek [this message]
2019-02-18 11:47 ` gregkh
2019-02-19 8:16 chenzefeng (A)
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=20190218092218.3ltqt5uhvy4z23ny@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=chenzefeng2@huawei.com \
--cc=cj.chengjian@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sjenning@redhat.com \
--cc=tglx@linutronix.de \
--cc=vojtech@suse.com \
--cc=x86@kernel.org \
--cc=xiexiuqi@huawei.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
all inboxes | Powered by JetHome®