Quantcast
Channel: Linux | Kernel
Browsing all 165258 articles
Browse latest View live

[PATCH v3 4/6] dax: give DAX clearing code correct bdev

dax_clear_blocks() needs a valid struct block_device and previously it was using inode->i_sb->s_bdev in all cases. This is correct for normal inodes

View Article



[PATCH v3 5/6] dax: move writeback calls into the filesystems

Previously calls to dax_writeback_mapping_range() for all DAX filesystems (ext2, ext4 & xfs) were centralized in filemap_write_and_wait_range(). dax_w

View Article

[PATCH v3 6/6] block: use dax_do_io() if blkdev_dax_capable()

From: Dan Williams <dan.j.williams@intel.com> Setting S_DAX on an inode requires that the inode participate in the DAX-fsync mechanism which expects

View Article

[PATCH RHEL6.8] x86/mm: Improve AMD Bulldozer ASLR workaround

Fixes bug 1240883 Brew build: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=10506428 RHEL6: code changed around from upstream so the address

View Article

[PATCH v5 3/7] x86: make CONFIG_DEBUG_RODATA non-optional

This removes the CONFIG_DEBUG_RODATA option and makes it always enabled. Suggested-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Kees Cook <keesc

View Article


[PATCH v5 4/7] introduce post-init read-only memory

One of the easiest ways to protect the kernel from attack is to reduce the internal attack surface exposed when a "write" flaw is available. By making

View Article

[PATCH v5 5/7] lkdtm: verify that __ro_after_init works correctly

The new __ro_after_init section should be writable before init, but not after. Validate that it gets updated at init and can't be written to afterward

View Article

[PATCH v5 6/7] x86, vdso: mark vDSO read-only after init

The vDSO does not need to be writable after __init, so mark it as __ro_after_init. The result kills the exploit method of writing to the vDSO from ker

View Article


[PATCH v5 7/7] ARM: vdso: Mark vDSO code as read-only

From: David Brown <david.brown@linaro.org> Although the arm vDSO is cleanly separated by code/data with the code being read-only in userspace mapping

View Article


perf, tools: Refactor and support interval and CSV metrics

Rebased tree and fixed Jiri's last feedback. [.v5: Fix mainly bisect problems. No regressions introduced by one patch and fixed again later. Some min

View Article

[PATCH 1/6] perf, tools, stat: Handled scaled == -1 case for counters

From: Andi Kleen <ak@linux.intel.com> Arnaldo pointed out that the earlier "Move noise/running printing into printout" change changed behavior for no

View Article

[PATCH 2/6] perf, tools, stat: Implement CSV metrics output

From: Andi Kleen <ak@linux.intel.com> Now support CSV output for metrics. With the new output callbacks this is relatively straight forward by creati

View Article

[PATCH 3/6] perf, tools, stat: Support metrics in --per-core/socket mode

From: Andi Kleen <ak@linux.intel.com> Enable metrics printing in --per-core / --per-socket mode. We need to save the shadow metrics in a unique place

View Article


[PATCH 4/6] perf, tools, stat: Document CSV format in manpage

From: Andi Kleen <ak@linux.intel.com> With all the recently added fields in the perf stat CSV output we should finally document them in the man page.

View Article

[PATCH 5/6] perf, tools, stat: Implement --metric-only mode

From: Andi Kleen <ak@linux.intel.com> Add a new mode to only print metrics. Sometimes we don't care about the raw values, just want the computed metr

View Article


[PATCH 6/6] perf, tools, stat: Add --metric-only support for -A

From: Andi Kleen <ak@linux.intel.com> Add metric only support for -A too. This requires a new print function that prints the metrics in the right ord

View Article

[PATCH] perf, tools: Dont stop PMU parsing on alias parse error

From: Andi Kleen <ak@linux.intel.com> When an error happens during alias parsing currently the complete parsing of all attributes of the PMU is stopp

View Article


PROBLEM: lk 4.5 oops on boot with Xeon D-1520

The following commit in 4.5 is causing a general protection fault during early boot: d6980ef32570 ("perf/x86/intel/uncore: Add Broadwell-EP uncore su

View Article

[PATCH] scripts/coccinelle: modernize &

& is no longer allowed in column 0, since Coccinelle 1.0.4. Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr> --- scripts/coccinelle/iterators/use

View Article

Re: Payment Receipt #4002********4390

View Article
Browsing all 165258 articles
Browse latest View live




Latest Images