Sinan Kaya 於 2019年7月15日週一 下午12:17寫道：
>
> On 7/14/2019 11:17 PM, Fuqian Huang wrote:
> > In commit 518a2f1925c3
> > ("dma-mapping: zero memory returned from dma_alloc_*"),
> > dma_alloc_coherent has already zeroed the memory.
> > So memset is not needed.
> >
> > Signed-off-by: Fuqian Huang
>
> I
On 7/14/19 5:45 AM, Xiaoming Ni wrote:
> On 2019/7/12 22:07, gre...@linuxfoundation.org wrote:
>> On Fri, Jul 12, 2019 at 09:11:57PM +0800, Xiaoming Ni wrote:
>>> On 2019/7/11 21:57, Vasily Averin wrote:
On 7/11/19 4:55 AM, Nixiaoming wrote:
> On Wed, July 10, 2019 1:49 PM Vasily Averin
Ping ...
> From: Fugang Duan
>
> iMX8 fuse word index represent as one 4-bytes word, it should not be divided
> by 4.
>
> Exp:
> - MAC0 address layout in fuse:
> offset 708: MAC[3] MAC[2] MAC[1] MAC[0]
> offset 709: XX xx MAC[5] MAC[4]
>
> Signed-off-by: Fugang Duan
> ---
>
Ping...
> From: Fugang Duan
>
> i.MX8QM efuse table has some difference with i.MX8QXP platform, so add
> i.MX8QM platform support.
>
> Signed-off-by: Fugang Duan
> ---
> drivers/nvmem/imx-ocotp-scu.c | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git
Add following function-graph tracer related options
- fgraph-filters : string array of filter
- fgraph-notraces : string array of notrace-filter
- fgraph-max-depth : u32 value of max depth
Note that these properties are available on ftrace root node
only, because these filters are globally
Add function tracer filter properties which includes
- ftrace-filters : string array of filter rules
- ftrace-notraces : string array of notrace rules
These properties are available on ftrace root node and
instance node.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_of.c | 36
Add cpumask property for tracing. Note that this property accepts
a string cpumask, not a digit number.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace.c| 41 -
kernel/trace/trace_of.c | 14 ++
2 files changed, 42 insertions(+),
Add synthetic event node support. The synthetic event node must be
a child node of ftrace node, and the node must start with "synth@"
prefix. The synth node requires fields string (not string array),
which defines the fields as same as tracing/synth_events interface.
Signed-off-by: Masami
Add kprobe event support in event node. User can add probe definitions
by "probes" property as a string array.
Signed-off-by: Masami Hiramatsu
---
Changes in v2:
- Make probes property avaiable if CONFIG_KPROBE_EVENTS=y.
---
kernel/trace/trace_kprobe.c |5 +++
kernel/trace/trace_of.c
Add per-event settings, which includes filter and actions.
Signed-off-by: Masami Hiramatsu
---
Changes in v2:
- Make event node available only if CONFIG_EVENT_TRACING=y
---
kernel/trace/trace_events_trigger.c |2 -
kernel/trace/trace_of.c | 82
Add instance node support to devicetree ftrace binding.
User can set some options and event nodes in instance node.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_of.c | 67 +++
1 file changed, 55 insertions(+), 12 deletions(-)
diff --git
Setup tracing options by devicetree instead of kernel parameters.
Since the kernel parameter is limited length, sometimes there is
no space to setup the tracing options. This will read the tracing
options from devicetree "ftrace" node and setup tracers at boot.
Note that this is not replacing
Register kprobe event to dynevent in subsys_initcall level.
This will allow kernel to register new kprobe events in
fs_initcall level via trace_run_command.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_kprobe.c | 19 +++
1 file changed, 15 insertions(+), 4
Add NULL trace-array check in print_synth_event(), because
if we enable tp_printk option, iter->tr can be NULL.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_events_hist.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_events_hist.c
Since ftrace_set_clr_event is already exported by EXPORT_SYMBOL_GPL,
it should not be static.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_events.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
index
Make the synthetic event accepts a different type field to record.
However, the size and signed flag must be same.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_events_hist.c |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/kernel/trace/trace_events_hist.c
Add a devicetree binding document for ftrace node.
Signed-off-by: Masami Hiramatsu
---
Changes in v2:
- Add cpumask, ftrace-filters, ftrace-notraces, fgraph-filters,
fgraph-notraces, fgraph-max-depth and instance node.
- Remove compatible and move file to
Since kprobe-events use event_trigger_unlock_commit_regs() directly,
that events doesn't show up in printk buffer if "tp_printk" is set.
Use trace_event_buffer_commit() in kprobe events so that it can
invoke output_printk() as same as other trace events.
Signed-off-by: Masami Hiramatsu
---
Hello,
Here is the 2nd version of RFC series to add boot-time tracing using
devicetree. Previous thread is here.
https://lkml.kernel.org/r/156113387975.28344.16009584175308192243.stgit@devnote2
In this version, I moved the ftrace node under /chosen/linux,ftrace
and remove compatible property,
Apply soft-disabled and the filter rule of the trace events to
the printk output of tracepoints (a.k.a. tp_printk kernel parameter)
as same as trace buffer output.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace.c |7 +++
1 file changed, 7 insertions(+)
diff --git
On 2019/7/12 22:06, Andrew Cooper wrote:
On 11/07/2019 03:15, Zhenzhong Duan wrote:
Commit 7457c0da024b ("x86/alternatives: Add int3_emulate_call()
selftest") is used to ensure there is a gap setup in exception stack
which could be used for inserting call return address.
This gap is missed
On Thu, Jul 11, 2019 at 11:48 PM kernel test robot
wrote:
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 509e56b37cc32c9b5fc2be585c25d1e60d6a1d73 ("blackhole_dev: add a
> selftest")
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
> master
Hi Paolo,
Would you help to review this patch, plz?
Many thanks.
---
Best wishes
Yi Wang
> 在 2019年7月6日，01:08，Yi Wang 写道：
>
> The ioapic_debug and apic_debug have been not used
> for years, and kvm tracepoints are enough for debugging,
> so remove them as Paolo suggested.
>
> However, there
On 15.07.19 02:36, Josh Poimboeuf wrote:
The __raw_callee_save_*() functions have an ELF symbol size of zero,
which confuses objtool and other tools.
Fixes a bunch of warnings like the following:
arch/x86/xen/mmu_pv.o: warning: objtool: __raw_callee_save_xen_pte_val() is
missing an ELF
On 7/13/19 8:53 PM, Hillf Danton wrote:
On Wed, 10 Jul 2019 14:43:28 -0700 (PDT) Qian Cai wrote:
Running LTP oom01 test case with swap triggers a crash below. Revert the series
"Make deferred split shrinker memcg aware" [1] seems fix the issue.
aefde94195ca mm: thp: make deferred split
Hi Paolo,
Would you help to review this patch, plz?
Many thanks.
---
Best wishes
Yi Wang
> 在 2019年7月6日，01:10，Yi Wang 写道：
>
> There are some pr_debug in TSC code, which may have
> been no use, so remove them as Paolo suggested.
>
> Signed-off-by: Yi Wang
> ---
> arch/x86/kvm/x86.c | 8
Hi all,
Please do not add v5.4 material to your linux-next included branches
until after v5.3-rc1 has been released.
Changes since 20190712:
The pm tree gained a build failure for which I applied a fix patch.
Non-merge commits (relative to Linus' tree): 5001
4262 files changed, 599496
This fixes the following coccinelle warning:
WARNING: return of 0/1 in function 'vmx_need_emulation_on_page_fault'
with return type bool
Return false instead of 0.
Signed-off-by: Yi Wang
---
arch/x86/kvm/vmx/vmx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 7/14/2019 11:17 PM, Fuqian Huang wrote:
> In commit 518a2f1925c3
> ("dma-mapping: zero memory returned from dma_alloc_*"),
> dma_alloc_coherent has already zeroed the memory.
> So memset is not needed.
>
> Signed-off-by: Fuqian Huang
I don't see SWIO or ARM64 IOMMU drivers getting impacted
On 7/13/19 12:39 PM, David Rientjes wrote:
On Sat, 13 Jul 2019, Yang Shi wrote:
When running ltp's oom test with kmemleak enabled, the below warning was
triggerred since kernel detects __GFP_NOFAIL & ~__GFP_DIRECT_RECLAIM is
passed in:
WARNING: CPU: 105 PID: 2138 at mm/page_alloc.c:4608
On 7/13/19 2:25 PM, Matthew Wilcox wrote:
On Sat, Jul 13, 2019 at 04:49:04AM +0800, Yang Shi wrote:
When running ltp's oom test with kmemleak enabled, the below warning was
triggerred since kernel detects __GFP_NOFAIL & ~__GFP_DIRECT_RECLAIM is
passed in:
There are lots of places where
Based on reverse engineering and original patch by
Paul Pawlowski
This adds support for Apple weird implementation of NVME in their
2018 or later machines. It accounts for the twice-as-big SQ entries
for the IO queues, and the fact that only interrupt vector 0 appears
to function properly.
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
pci_alloc_consistent calls dma_alloc_coherent directly.
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the
kcalloc already zeros the memory during allocation.
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So the memset after these functions is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual
pci_alloc_consistent calls dma_alloc_coherent directly.
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the
kvzalloc already zeroes the memory during the allocation.
pci_alloc_consistent calls dma_alloc_coherent directly.
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So the memset after these function is not needed.
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
vzalloc has already zeroed the memory during the allocation.
So memset is unneeded.
Signed-off-by: Fuqian Huang
---
drivers/infiniband/ulp/ipoib/ipoib_cm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/infiniband/ulp/ipoib/ipoib_cm.c
b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
index
pci_alloc_consistent calls dma_alloc_coherent directly.
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the
pci_alloc_consitent calls dma_alloc_coherent directly.
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the
pci_alloc_consistent calls dma_alloc_coherent directly.
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Acked-by: Neil Horman
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
In commit 518a2f1925c3
("dma-mapping: zero memory returned from dma_alloc_*"),
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Fuqian Huang
---
Changes in v3:
- Use actual commit rather than the merge commit in the commit message
On Sun, Jul 14, 2019 at 12:29:51PM -0700, Paul E. McKenney wrote:
> On Sun, Jul 14, 2019 at 03:05:22PM -0400, Theodore Ts'o wrote:
> > On Sun, Jul 14, 2019 at 05:48:00PM +0300, Dmitry Vyukov wrote:
> > > But short term I don't see any other solution than stop testing
> > > sched_setattr because it
On Fri, 2019-07-12 at 13:52 +0300, Andrey Ryabinin wrote:
>
> On 7/11/19 1:06 PM, Walter Wu wrote:
> > On Wed, 2019-07-10 at 21:24 +0300, Andrey Ryabinin wrote:
> >>
> >> On 7/9/19 5:53 AM, Walter Wu wrote:
> >>> On Mon, 2019-07-08 at 19:33 +0300, Andrey Ryabinin wrote:
>
> On 7/5/19
From: Peng Fan
The AUDIO PLL max support 650M, so the original clk settings violate
spec. This patch makes the output 786432000 -> 393216000,
and 722534400 -> 361267200 to aligned with NXP vendor kernel without any
impact on audio functionality and go within 650MHz PLL limit.
Cc:
Fixes:
This fixes the following coccinelle warning:
./arch/x86/kernel/e820.c:89:9-10: WARNING: return of 0/1 in function
'_e820__mapped_any' with return type bool
Return type bool instead of 0/1.
Signed-off-by: Yi Wang
---
arch/x86/kernel/e820.c | 4 ++--
1 file changed, 2 insertions(+), 2
This fixes the following coccinelle warning:
./kernel/sched/fair.c:8688:9-10: WARNING: return of 0/1 in function
'voluntary_active_balance' with return type bool
Return type bool instead of 0/1.
Signed-off-by: Yi Wang
---
kernel/sched/fair.c | 8
1 file changed, 4 insertions(+), 4
Hi Paolo,
Thanks for your reviewing! There also has Qemu patch sent here,
https://www.mail-archive.com/qemu-devel@nongnu.org/msg630359.html
Could you please review that? Thanks very much!
Jing
On 7/13/2019 6:37 PM, Paolo Bonzini wrote:
On 11/07/19 07:49, Jing Liu wrote:
AVX512 BFLOAT16
The pull request you sent on Mon, 15 Jul 2019 01:08:43 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git
> tags/ecryptfs-5.3-rc1-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fa6e951a2a440babd7a7310d0f4713e618061767
Thank you!
--
On 7/14/19 1:08 PM, Bharath Vedartham wrote:
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 4ef62a4..b4a4549 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -2694,10 +2694,9 @@ static int io_sqe_buffer_register(struct io_ring_ctx
> *ctx, void __user *arg,
>*
On (07/13/19 17:03), Konstantin Khlebnikov wrote:
> > We call kmsg_dump(KMSG_DUMP_PANIC) after smp_send_stop() and after
> > printk_safe_flush_on_panic(). printk_safe_flush_on_panic() resets
> > the state of logbuf_lock, so logbuf_lock, in general case, should
> > be unlocked by the time we call
On Fri, 12 Jul 2019, at 22:41, Maxime Ripard wrote:
> Hi,
>
> On Fri, Jul 12, 2019 at 01:02:13PM +0930, Andrew Jeffery wrote:
> > The ASPEED SD/SDIO/eMMC controller exposes two slots implementing the
> > SDIO Host Specification v2.00, with 1 or 4 bit data buses, or an 8 bit
> > data bus if
Hello Hongwei,
On Sat, 13 Jul 2019, at 05:44, Hongwei Zhang wrote:
> Add bindings to support SGPIO on AST2400 or AST2500.
>
> Signed-off-by: Hongwei Zhang
> ---
> .../devicetree/bindings/gpio/sgpio-aspeed.txt | 43
> ++
> 1 file changed, 43 insertions(+)
> create
On 2019/7/12 下午6:10, 王贇 wrote:
[snip]
>>
>> Documentation/cgroup-v1/cpusets.txt
>>
>> Look for mems_allowed.
>
> This is the attribute belong to cpuset cgroup isn't it?
>
> Forgive me but I have no idea on how to combined this
> with memory cgroup's locality hierarchical update...
> parent
From: Wanpeng Li
Allow guest reads CORE cstate when exposing host CPU power management
capabilities
to the guest. PKG cstate is restricted to avoid a guest to get the whole
package
information in multi-tenant scenario.
Cc: Eduardo Habkost
Cc: Paolo Bonzini
Cc: Radim Krčmář
Signed-off-by:
On 7/12/2019 11:52 PM, Sean Christopherson wrote:
On Fri, Jul 12, 2019 at 04:29:06PM +0800, Tao Xu wrote:
diff --git a/arch/x86/kernel/cpu/umwait.c b/arch/x86/kernel/cpu/umwait.c
index 6a204e7336c1..631152a67c6e 100644
--- a/arch/x86/kernel/cpu/umwait.c
+++ b/arch/x86/kernel/cpu/umwait.c
@@
On 7/12/2019 11:13 PM, Sean Christopherson wrote:
On Fri, Jul 12, 2019 at 04:29:05PM +0800, Tao Xu wrote:
diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
index 46af3a5e9209..a4d5da34b306 100644
--- a/arch/x86/kvm/vmx/nested.c
+++ b/arch/x86/kvm/vmx/nested.c
@@ -2048,6 +2048,7
Hi Linus,
The following changes since commit 5ded5871030eb75017639148da0a58931dfbfc25:
Merge tag 'scsi-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2019-02-15 13:36:43
-0800)
are available in the git repository at:
--
Dear Friend (Assalamu Alaikum),
I came across your e-mail contact prior a private search while in need of
your assistance. My name is Aisha Al-Qaddafi a single Mother and a Widow
with three Children. I am the only biological Daughter of late Libyan
President (Late Colonel Muammar Gaddafi).
After an objtool improvement, it's reporting that __memcpy_mcsafe() is
calling mcsafe_handle_tail() with AC=1:
arch/x86/lib/memcpy_64.o: warning: objtool: .fixup+0x13: call to
mcsafe_handle_tail() with UACCESS enabled
arch/x86/lib/memcpy_64.o: warning: objtool: __memcpy_mcsafe()+0x34:
- Add an alias check in validate_functions(). With this change, aliases
no longer need uaccess_safe set.
- Add an alias check in decode_instructions(). With this change, the
"if (!insn->func)" check is no longer needed.
- Don't create aliases for zero-length functions, as it can have
If 'insn->func' is NULL, objtool skips some important checks, including
sibling call validation. So if some .fixup code does an invalid sibling
call, objtool ignores it.
Treat all code branches (including alts) as part of the original
function by keeping track of the original func value from
After adding mcsafe_handle_tail() to the objtool uaccess safe list,
objtool reports:
arch/x86/lib/usercopy_64.o: warning: objtool: mcsafe_handle_tail()+0x0: call
to __fentry__() with UACCESS enabled
With SMAP, this function is called with AC=1, so it needs to be careful
about which functions
With CONFIG_FRAME_POINTER, vmx_vmenter() needs to do frame pointer setup
before calling kvm_spurious_fault().
Fixes the following warning:
arch/x86/kvm/vmx/vmenter.o: warning: objtool: vmx_vmenter()+0x14: call
without frame pointer save/setup
Signed-off-by: Josh Poimboeuf
---
Cc: Paolo
This makes it easier to add new instruction types. Also it's hopefully
more robust since the compiler should warn about out-of-range enums.
Signed-off-by: Josh Poimboeuf
---
tools/objtool/arch.h| 35 +
tools/objtool/arch/x86/decode.c | 2 +-
Simplify the sibling call detection logic a bit.
Signed-off-by: Josh Poimboeuf
---
tools/objtool/check.c | 65 ++-
1 file changed, 33 insertions(+), 32 deletions(-)
diff --git a/tools/objtool/check.c b/tools/objtool/check.c
index
A Clang-built kernel is showing the following warning:
arch/x86/kernel/platform-quirks.o: warning: objtool:
x86_early_init_platform_quirks()+0x84: unreachable instruction
That corresponds to this code:
7e: 0f 85 00 00 00 00 jne84
80: R_X86_64_PC32
The same getuser/putuser error paths are used regardless of whether AC
is set. In non-exception failure cases, this results in an unnecessary
CLAC.
Fixes the following warnings:
arch/x86/lib/getuser.o: warning: objtool: .altinstr_replacement+0x18:
redundant UACCESS disable
After making a change to improve objtool's sibling call detection, it
started showing the following warning:
arch/x86/kvm/vmx/nested.o: warning: objtool: .fixup+0x15: sibling call from
callable instruction with modified stack frame
The problem is the kvm_handle_fault_on_reboot() macro.
From: Jann Horn
This fixes objtool for both a GCC issue and a Clang issue:
1) GCC issue:
kernel/bpf/core.o: warning: objtool: ___bpf_prog_run()+0x8d5: sibling call
from callable instruction with modified stack frame
With CONFIG_RETPOLINE=n, GCC is doing the following optimization in
After an objtool improvement, it's complaining about the CLAC in
copy_user_handle_tail():
arch/x86/lib/copy_user_64.o: warning: objtool: .altinstr_replacement+0x12:
redundant UACCESS disable
arch/x86/lib/copy_user_64.o: warning: objtool: copy_user_handle_tail()+0x6:
(alt)
Now that C jump tables are supported, call them "jump tables" instead of
"switch tables". Also rename some other variables, add comments, and
simplify the code flow a bit.
Signed-off-by: Josh Poimboeuf
---
tools/objtool/check.c | 82 +++
All callable functions should have an ELF size.
Signed-off-by: Josh Poimboeuf
---
tools/objtool/check.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tools/objtool/check.c b/tools/objtool/check.c
index 9bf4844d9226..16454cbca679 100644
--- a/tools/objtool/check.c
+++
Even calls to __noreturn functions need the frame pointer setup first.
Such functions often dump the stack.
Signed-off-by: Josh Poimboeuf
---
tools/objtool/check.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/tools/objtool/check.c
After an objtool improvement, it complains about the fact that
start_cpu0() jumps to code which has an LRET instruction.
arch/x86/kernel/head_64.o: warning: objtool: .head.text+0xe4: unsupported
instruction in callable function
Technically, start_cpu0() is callable, but it acts nothing like a
In one rare case, Clang generated the following code:
5ca: 83 e0 21and$0x21,%eax
5cd: b9 04 00 00 00 mov$0x4,%ecx
5d2: ff 24 c5 00 00 00 00jmpq *0x0(,%rax,8)
5d5: R_X86_64_32S .rodata+0x38
which uses the
There have been a lot of objtool bug reports lately, mainly related to
Clang and BPF. As part of fixing those bugs, I added some improvements
to objtool which uncovered yet more bugs (some kernel, some objtool).
I've given these patches a lot of testing with both GCC and Clang. More
compile
Fix the following warnings:
arch/x86/entry/thunk_64.o: warning: objtool: trace_hardirqs_on_thunk() is
missing an ELF size annotation
arch/x86/entry/thunk_64.o: warning: objtool: trace_hardirqs_off_thunk() is
missing an ELF size annotation
arch/x86/entry/thunk_64.o: warning: objtool:
Some of the fastop functions, e.g. em_setcc(), are actually just used as
global labels which point to blocks of functions. The global labels are
incorrectly annotated as functions. Also the functions themselves don't
have size annotations.
Fixes a bunch of warnings like the following:
On x86-64, with CONFIG_RETPOLINE=n, GCC's "global common subexpression
elimination" optimization results in ___bpf_prog_run()'s jumptable code
changing from this:
select_insn:
jmp *jumptable(, %rax, 8)
...
ALU64_ADD_X:
...
dead_end_function() can no longer return an error. Simplify its
interface by making it return boolean.
Signed-off-by: Josh Poimboeuf
---
tools/objtool/check.c | 36 ++--
1 file changed, 14 insertions(+), 22 deletions(-)
diff --git a/tools/objtool/check.c
The __raw_callee_save_*() functions have an ELF symbol size of zero,
which confuses objtool and other tools.
Fixes a bunch of warnings like the following:
arch/x86/xen/mmu_pv.o: warning: objtool: __raw_callee_save_xen_pte_val() is
missing an ELF size annotation
arch/x86/xen/mmu_pv.o:
The pull request you sent on Sun, 14 Jul 2019 17:53:37 +0300:
> git://git.infradead.org/linux-platform-drivers-x86.git
> tags/platform-drivers-x86-v5.3-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/55167453111d3a1e600e29ba6c8e63906bb4821b
Thank you!
--
The pull request you sent on Sun, 14 Jul 2019 21:02:00 +0200 (CEST):
> git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git
> tags/for-linus-5.3-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f2772a0e4833d1af1901b6f1a38136fb71d1350c
Thank you!
--
Add me as a maintainer for pidfd stuff so people know who to yell at and
to easily keep track of incoming changes.
Signed-off-by: Christian Brauner
---
v1:
- Joe Perches :
- remove N: pidfd line
---
MAINTAINERS | 11 +++
1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS
The pull request you sent on Sun, 14 Jul 2019 21:02:09 +0200 (CEST):
> git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git
> tags/upstream-5.3-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a318423b61e8c67aa5c0a428540c58439a20baac
Thank you!
--
The pull request you sent on Sat, 13 Jul 2019 18:41:55 -0500:
> git://git.linaro.org/landing-teams/working/fujitsu/integration.git
> tags/mailbox-v5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fde7dc63b1caa6dedf9af7cbf79895589629bc95
Thank you!
--
The pull request you sent on Sat, 13 Jul 2019 00:17:33 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/dennis/percpu.git for-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a1240cf74e8228f7c80d44af17914c0ffc5633fb
Thank you!
--
Deet-doot-dot, I am a bot.
Good morning from Singapore,
What are the differences between cointelpro and coamdpro?
-BEGIN EMAIL SIGNATURE-
The Gospel for all Targeted Individuals (TIs):
[The New York Times] Microwave Weapons Are Prime Suspect in Ills of
U.S. Embassy Workers
Link:
Hi all,
Fetching the dlm tree fails like this:
fatal: Couldn't find remote ref refs/heads/next
--
Cheers,
Stephen Rothwell
pgpoUcmYnAA9S.pgp
Description: OpenPGP digital signature
1 - 100 of 278 matches
Mail list logo
