ftrace needs to modify the kernel text in order to enable function tracing.
For security reasons, the kernel text is marked to read-only (ro) at the end
of system bootup. When enabling function tracing after that, ftrace calls
arch specific code that needs to enable the modification of kernel text
On Wed, Aug 23, 2017 at 09:32:06PM +0530, Oza Oza wrote:
> On Wed, Aug 23, 2017 at 9:22 PM, Sinan Kaya wrote:
> > Hi Oza,
> >
> >> In working Enumuration case I get following:
> >> [9.125976] pci :00:00.0: bridge configuration invalid ([bus
> >> 00-00]), re-configuring
> >> [9.134267]
One line fix for reversed logic where static array is freed instead of
allocated one
Pavel Tatashin (1):
mm: Reversed logic in memblock_discard
mm/memblock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.14.1
In recently introduced memblock_discard() there is a reversed logic bug.
Memory is freed of static array instead of dynamically allocated one.
Fixes: 3010f876500f ("mm: discard memblock data later")
Reported-and-tested-by: Woody Suwalski
Signed-off-by: Pavel Tatashin
---
mm/memblock.c | 2 +-
Hi Oleksandr,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.13-rc6 next-20170823]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Oleksandr-Shamray/JTAG-driver
On Wed, Aug 23, 2017 at 01:24:41PM -0400, Johannes Weiner wrote:
> Hi,
>
> On Wed, Aug 23, 2017 at 05:20:31PM +0100, Roman Gushchin wrote:
> > On Tue, Aug 22, 2017 at 01:03:44PM -0400, Johannes Weiner wrote:
> > > > + css_task_iter_start(&memcg->css, 0, &it);
> > > > + while ((task = c
From: Jiri Slaby
Date: Wed, 23 Aug 2017 09:29:44 +0200
> On 06/27/2017, 07:32 PM, Marcel Holtmann wrote:
>>> It looks like bnep_session has same pattern as the issue reported in
>>> old rfcomm:
>>>
>>> while (1) {
>>> set_current_state(TASK_INTERRUPTIBLE);
>>> if (cond
> -Original Message-
> From: Leon Romanovsky [mailto:l...@kernel.org]
> Sent: Wednesday, August 23, 2017 6:52 AM
> To: Long Li
> Cc: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@vger.kernel.org; linux-
> r...@vger.kernel.org; Christoph Hellw
On Thu, Jul 20, 2017 at 12:25 AM, MyungJoo Ham wrote:
>> On 2017년 07월 19일 06:42, Rob Herring wrote:
>> > Now that we have a custom printf format specifier, convert users of
>> > full_name to use %pOF instead. This is preparation to remove storing
>> > of the full path string for each node.
>> >
>>
Long pressed key could not show right in XEN vncviewer after tigervnc
client changed the way how to send repeat keys, from "Down Up Down Up
..." to "Down Down ... Up". By enable EV_REP bit here, XEN keyboard
device will trigger default auto repeat process from input subsystem,
and make auto repeat
On Wed, Jul 19, 2017 at 12:42 PM, Mark Salter wrote:
> On Tue, 2017-07-18 at 16:42 -0500, Rob Herring wrote:
>> Now that we have a custom printf format specifier, convert users of
>> full_name to use %pOF instead. This is preparation to remove storing
>> of the full path string for each node.
>>
>
On 23.08.2017 14:54, Alexander Shishkin wrote:
> Alexey Budankov writes:
>
>> This patch implements mux switch that triggers skipping to the
>> current CPU's events list at mulitplexing hrtimer interrupt
>> handler as well as adoption of the switch in the existing
>> implementation.
>>
>> perf
> On Wed, Aug 23, 2017 at 04:33:08PM +0200, Peter Zijlstra wrote:
> > > @@ -6145,6 +6183,9 @@ void perf_prepare_sample(struct
> > > perf_event_header *header,
> > >
> > > header->size += size;
> > > }
> > > +
> > > + if (sample_type & PERF_SAMPLE_PHYS_ADDR)
> > > + data->phys_ad
Hi Jiri,
>>> It looks like bnep_session has same pattern as the issue reported in
>>> old rfcomm:
>>>
>>> while (1) {
>>> set_current_state(TASK_INTERRUPTIBLE);
>>> if (condition)
>>> break;
>>> // may call might_sleep here
>>>
On Tue, Jul 18, 2017 at 4:42 PM, Rob Herring wrote:
> Now that we have a custom printf format specifier, convert users of
> full_name to use %pOF instead. This is preparation to remove storing
> of the full path string for each node.
>
> Signed-off-by: Rob Herring
> Cc: "Rafael J. Wysocki"
> Cc:
On Wed, Aug 23, 2017 at 8:58 AM, Tim Chen wrote:
>
> Will you still consider the original patch as a fail safe mechanism?
I don't think we have much choice, although I would *really* want to
get this root-caused rather than just papering over the symptoms.
Maybe still worth testing that "sched/n
A "BUG: MAX_STACK_TRACE_ENTRIES too low!" error was hit when running a
networking test on a 4.11 kernel. So even 512k of stack trace entries
wasn't enough in this case.
Instead of hardcoding a larger MAX_STACK_TRACE_ENTRIES value,
it is now made to be dependent on a new kernel configuration entry
I must have added that accidentally when cherry-picking an internal
patch for upstreaming. Thanks for catching it.
Reviewed-by: Felix Kuehling
Regards,
Felix
On 2017-08-23 09:17 AM, Colin King wrote:
> From: Colin Ian King
>
> Remove a redundant identical return statement, it has no use.
>
On Wed, Aug 23, 2017 at 01:58:36PM -0400, Steven Rostedt wrote:
>
> ftrace needs to modify the kernel text in order to enable function tracing.
> For security reasons, the kernel text is marked to read-only (ro) at the end
> of system bootup. When enabling function tracing after that, ftrace calls
On Wed, Aug 23, 2017 at 6:45 AM, Vitaly Kuznetsov wrote:
>
> Solve the issue by enabling RCU-based table free mechanism when PARAVIRT
> is selected in config. Testing with kernbench doesn't show any notable
> performance impact:
I wonder if we should just make it unconditional if it doesn't reall
On Wed, Aug 23, 2017 at 06:01:25PM +, Liang, Kan wrote:
> For x86, I think we can do something as below. But I'm not sure other
> architectures.
If you'd done: git grep PERF_SAMPLE_ADDR, you'd have found:
arch/powerpc/perf/core-book3s.c:if (event->attr.sample_type &
PERF_SA
On Wed, Aug 23, 2017 at 03:31:42PM +0200, Arnd Bergmann wrote:
> We get a build warning from a boolean expression that is never used:
>
> mm/madvise.c: In function 'madvise_free_pte_range':
> include/linux/swap.h:490:55: error: value computed is not used
> [-Werror=unused-value]
> #define free_s
On 08/23/2017 04:45 AM, Petr Mladek wrote:
> On Thu 2017-08-17 09:15:39, Prarit Bhargava wrote:
>> printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
>> timestamp to printk messages. The local hardware clock loses time each
>> day making it difficult to determine exactly wh
Hi Liang,
On Wed, Aug 23, 2017 at 02:10:26PM -0400, Liang Yan wrote:
> Long pressed key could not show right in XEN vncviewer after tigervnc
> client changed the way how to send repeat keys, from "Down Up Down Up
> ..." to "Down Down ... Up". By enable EV_REP bit here, XEN keyboard
> device will t
From: "Aviad Krawczyk (A)"
Date: Wed, 23 Aug 2017 10:08:58 +
> Thanks
Please do not top-post.
Especially quoting the original message in the way that you did.
As a result of how you replied to this, this patch will show up
twice in my patchwork queue making more administrative work
for me.
From: Colin King
Date: Wed, 23 Aug 2017 12:13:05 +0100
> From: Colin Ian King
>
> iph is being assigned the same value twice; remove the redundant
> second assignment.
>
> Fixes warning:
> net/ipv4/ip_gre.c:265:2: warning: Value stored to 'iph' is never read
>
> Signed-off-by: Colin Ian King
On Wed, Aug 23, 2017 at 10:58 AM, Steven Rostedt wrote:
>
> ftrace needs to modify the kernel text in order to enable function tracing.
> For security reasons, the kernel text is marked to read-only (ro) at the end
> of system bootup. When enabling function tracing after that, ftrace calls
> arch
On Tue, Aug 22, 2017 at 9:57 PM, John Stultz wrote:
> On Tue, Aug 22, 2017 at 7:56 PM, John Stultz wrote:
>> On Tue, Aug 22, 2017 at 7:34 PM, Jisheng Zhang wrote:
>>> On Tue, 22 Aug 2017 18:51:08 -0700 Greg KH wrote:
>>>
On Tue, Aug 08, 2017 at 07:03:05PM +0800, Jisheng Zhang wrote:
>
On Wed, Aug 23, 2017 at 11:31 AM, Prarit Bhargava wrote:
> On 08/23/2017 04:45 AM, Petr Mladek wrote:
>> I know that it would make the code more complicated. But
>> I really like the approach used by /sys/power/disk or
>> /sys/power/pm_test. They list all possible values
>> and put the selected on
On Wed, Aug 23, 2017 at 6:13 AM, Julia Lawall wrote:
>
>
> On Tue, 22 Aug 2017, Kees Cook wrote:
>
>> This improves the patch mode of setup_timer.cocci. Several patterns were
>> missing:
>> - assignments-before-init_timer() cases
>> - limiting the .data case removal to the struct timer_list inst
On Mon, Aug 14, 2017 at 09:04:25PM +0800, honghui.zh...@mediatek.com wrote:
> From: Honghui Zhang
>
> MT2712 and MT7622's PCIe host controller support MSI, but only 32bit MSI
> address are supportted. It connect to GIC with the same IRQ number of INTx
> IRQ, so it shares the same IRQ with INTx IR
On Wed, Aug 23, 2017 at 06:09:11PM +, Long Li wrote:
>
>
> > -Original Message-
> > From: Leon Romanovsky [mailto:l...@kernel.org]
> > Sent: Wednesday, August 23, 2017 6:52 AM
> > To: Long Li
> > Cc: Steve French ; linux-c...@vger.kernel.org; samba-
> > techni...@lists.samba.org; linux
On Wed, Aug 23, 2017 at 5:01 PM, Arnd Bergmann wrote:
> This is an interesting regression with gcc-8, showing a harmless
> warning for correct code:
>
> In file included from include/linux/kernel.h:13:0,
> ...
> from drivers/scsi/lpfc/lpfc_debugfs.c:23:
> include/
On Wed, 23 Aug 2017 11:48:13 -0700
Kees Cook wrote:
> > diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c
> > index ad80548..fd75f38 100644
> > --- a/arch/arm/mm/init.c
> > +++ b/arch/arm/mm/init.c
> > @@ -745,19 +745,29 @@ static int __mark_rodata_ro(void *unused)
> > return 0;
> > }
> -Original Message-
> From: Leon Romanovsky [mailto:l...@kernel.org]
> Sent: Wednesday, August 23, 2017 12:02 PM
> To: Long Li
> Cc: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@vger.kernel.org; linux-
> r...@vger.kernel.org; Christoph Hell
On 08/23/2017 10:44 AM, Bart Van Assche wrote:
> On Wed, 2017-08-23 at 11:27 -0400, Martin K. Petersen wrote:
>> However, what's more important is that we still need a good version of
>> your patch for 4.13. I took Brian's workaround for ipr but I still think
>> Christoph's concerns need to be addr
This removes the restriction on the value range of the fbcon=margin:
parameter. The color value really depends on the driver being used.
Signed-off-by: David Lechner
---
This is a follow up to "fbcon: add fbcon=margin: command line option".
https://lkml.org/lkml/2017/8/23/479
Documentation/fb
In file included from security/apparmor/ipc.c:23:0:
security/apparmor/include/sig_names.h:26:3: error: 'SIGSTKFLT' undeclared
here (not in a function)
[SIGSTKFLT] = 16, /* -, 16, - */
^
security/apparmor/include/sig_names.h:26:3: error: array index in initializer
not of integer ty
On Wed, Aug 23, 2017 at 07:10:38PM +, Long Li wrote:
>
>
> > -Original Message-
> > From: Leon Romanovsky [mailto:l...@kernel.org]
> > Sent: Wednesday, August 23, 2017 12:02 PM
> > To: Long Li
> > Cc: Steve French ; linux-c...@vger.kernel.org; samba-
> > techni...@lists.samba.org; linu
On Wed, Aug 23, 2017 at 10:41:18AM +0800, Yong wrote:
> > > > > +static irqreturn_t sun6i_csi_isr(int irq, void *dev_id)
> > > > > +{
> > > > > + struct sun6i_csi_dev *sdev = (struct sun6i_csi_dev *)dev_id;
> > > > > + struct regmap *regmap = sdev->regmap;
> > > > > + u32 status;
> > >
Alexandre Belloni writes:
> pxa_rtc_open() registers the interrupt handler which will access the RTC
> registers. However, pxa_rtc_open() is called before the register range is
> ioremapped. Instead, call it after devm_ioremap().
>
> Signed-off-by: Alexandre Belloni
Acked-by: Robert Jarzmik
Ch
Alexandre Belloni writes:
> In the error path of sa1100_rtc_open(), info->clk is disabled which will
> happen again in sa1100_rtc_remove() when the module is removed whereas it
> is only enabled once in sa1100_rtc_init().
>
> Fixes: 0cc0c38e9139 ("drivers/rtc/rtc-sa1100.c: move clock enable/disab
Robert Jarzmik writes:
> Hi Lars, Mark, Charles, Lee,
Hi again,
I have Lee's comments covered now. If there are no more comments, I'll send out
a v6 for Lee to verify my work is dealing with his concerns.
Cheers.
--
Robert
Bhumika Goyal writes:
> Make these const as they are only passed as the 2nd argument to the
> function devm_snd_soc_register_platform, which is of type const.
> Done using Coccinelle.
>
> Signed-off-by: Bhumika Goyal
> ---
> sound/soc/pxa/mmp-pcm.c| 2 +-
> sound/soc/pxa/pxa2xx-pcm.c | 2 +-
Boris Brezillon writes:
> Le Mon, 14 Aug 2017 22:48:31 +0200,
>> Andrea Adami (9):
>> mtd: sharpslpart: Add sharpslpart partition parser
>> mtd: nand: sharpsl: Add partition parsers platform data
>> mfd: tmio: Add partition parsers platform data
>> mtd: nand: sharpsl: Register partitions
From: Andi Kleen
Save the original array dimensions in xyarrays, so that users can
retrieve them later. Add some inline functions to access these fields.
Signed-off-by: Andi Kleen
Acked-by: Jiri Olsa
Link: http://lkml.kernel.org/r/20170811232634.30465-1-a...@firstfloor.org
[ As noticed by Jiri
linux into perf/core
(2017-08-22 12:16:39 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-4.14-20170823
for you to fetch changes up to 60913e005c8d19ec5187a638eafdd088509dfb9e:
perf tools: Fix static li
From: Andi Kleen
Some of the upcoming metrics need more than 8 events. Increase the maximum
number the parser supports.
Signed-off-by: Andi Kleen
Acked-by: Jiri Olsa
Link: http://lkml.kernel.org/r/20170811232634.30465-9-a...@firstfloor.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/pe
From: Andi Kleen
Avoid adding redundant events while parsing an expression. When we add
an "other" event check first if it already exists.
v2: Fix perf test failure.
Signed-off-by: Andi Kleen
Acked-by: Jiri Olsa
Link: http://lkml.kernel.org/r/20170811232634.30465-10-a...@firstfloor.org
Signe
From: Konstantin Khlebnikov
* libunwind-x86_64 must be linked before libunwind
* libunwind requires liblzma
* static libunwind conflicts with static libgcc_eh
Signed-off-by: Konstantin Khlebnikov
Cc: Alexander Shishkin
Cc: Peter Zijlstra
Link:
http://lkml.kernel.org/r/150322917247.129799.142
On Wed, Aug 23, 2017 at 12:15 PM, Doug Nazar wrote:
> The following commits cause short reads of block devices, however writes are
> still allowed.
>
> c2a9737f45e2 ("vfs,mm: fix a dead loop in truncate_inode_pages_range()")
> d05c5f7ba164 ("vfs,mm: fix return value of read() at s_maxbytes")
>
> W
From: Andi Kleen
Add some simple tests to perf test to test data source printing.
v2: Make the tests actually checked for the correct name of Forward
v3: Adjust to new encoding
Committer notes:
Avoid the in place declaration to make this build with older compilers,
for instance, in Debian 7 we
From: Konstantin Khlebnikov
Fix feature test for static libdw: link required dependencies. Backends
of libebl are not statically linked thus libdl is required.
In Debian/Ubuntu libdw-dev includes libebl.a starting from 0.166-1.
Signed-off-by: Konstantin Khlebnikov
Cc: Alexander Shishkin
Cc:
From: Konstantin Khlebnikov
Fix misprint CAP_IOC_LOCK -> CAP_IPC_LOCK. This capability have nothing
to do with raw tracepoints. This part is about bypassing mlock limits.
Sysctl kernel.perf_event_paranoid = -1 allows raw and ftrace function
tracepoints without CAP_SYS_ADMIN.
Signed-off-by: Kons
From: Konstantin Khlebnikov
Target install-man builds them but forget to install.
Signed-off-by: Konstantin Khlebnikov
Cc: Alexander Shishkin
Cc: Borislav Petkov
Cc: Peter Zijlstra
Fixes: af3df2cf17f5 ("perf tools: Try to build Documentation when installing")
Link:
http://lkml.kernel.org/r/
From: Andi Kleen
Add decoding for the new "lvlx" and "snoopx" meminfo fields added
earlier to the kernel so that "perf mem report" and other tools can
print it properly.
v2: Merge with persistent memory patch.
Switch to new bit encoding for each combination.
v3: Switch to generic lvlnum field.
From: Andi Kleen
Add JSON uncore events for Skylake Server to perf.
Based on JSON list V1.01
This is a much fuller list than with earlier uncores, including
more low level (but also harder to understand) events. It does not
include the "experimential" events. The previous
high level metric (LLC
On 23.08.2017 16:49, Steven Rostedt wrote:
> On Wed, 23 Aug 2017 16:48:24 +0200
> Petr Mladek wrote:
>
>> +
>> +printk("Going to call: %pF\n", gettimeofday);
>> +printk("Going to call: %pF\n", p->func);
>> +printk("%s: called from %pS\n", __func__, _RET_IP_);
>> +printk("%s: calle
From: Andi Kleen
Enhance the expression parser for more complex metric formulas.
- Support python style IF ELSE operators
- Add an #SMT_On magic variable for formulas that depend on the SMT
status.
Example: 4 *( CPU_CLK_UNHALTED.THREAD_ANY / 2 ) if #SMT_on else cycles
- Support MIN/MAX operati
From: Andi Kleen
perf stat -e cpu/uops_executed.core,cmask=1/
would be detected as a BPF source event because the .c matches the .c
source BPF pattern.
v2:
Originally I tried to use lex lookahead, but it doesn't seem to work.
This now extends the BPF pattern to match longer events, but then
From: Andi Kleen
Add an smt_on() function to return if SMT is enabled or disabled. Used
in the next patch.
Signed-off-by: Andi Kleen
Acked-by: Jiri Olsa
Link: http://lkml.kernel.org/r/20170811232634.30465-7-a...@firstfloor.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/Buil
Note that Camel Case in cifs.ko source is largely used for protocol
definitions to match the official protocol documentation. So we
expect Camel Case only where it is meant to express the **exact** name
of a field in the official specification of the wire protocol but
there may be some legacy code
From: Andi Kleen
Fix buffer overflow for:
% perf stat -e msr/tsc/,cstate_core/c7-residency/ true
that causes glibc free list corruption. For some reason it doesn't
trigger in valgrind, but it is visible in AS:
=
==32681==ERR
On Wed, Aug 23, 2017 at 05:42:55PM +0100, Will Deacon wrote:
> Hi Eric,
>
> On Wed, Aug 23, 2017 at 02:36:53PM +0200, Auger Eric wrote:
> > On 23/08/2017 12:25, Will Deacon wrote:
> > > On Tue, Aug 22, 2017 at 10:09:15PM +0300, Michael S. Tsirkin wrote:
> > >> On Fri, Aug 18, 2017 at 05:49:42AM +0
On Wed, Aug 23, 2017 at 6:36 PM, Krzysztof Kozlowski wrote:
> soc: samsung: Use kbasename instead of open coding (2017-07-24 06:47:50
> +0200)
>
>
> Samsung soc drivers changes for v4.14
>
> Conversion to kbasename from Rob Herri
On 22 August 2017 at 06:21, Luca Abeni wrote:
> Hi Mathieu,
Good day to you,
>
> On Wed, 16 Aug 2017 15:20:36 -0600
> Mathieu Poirier wrote:
>
>> This is a renewed attempt at fixing a problem reported by Steve Rostedt [1]
>> where DL bandwidth accounting is not recomputed after CPUset and CPUho
On Wed, Aug 23, 2017 at 6:36 PM, Krzysztof Kozlowski wrote:
> Hi,
>
> Just one commit. If needed you can also cherry-pick it directly.
> Based on top of previous pull request.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit f991ce429a420dbb42b3e4b5a47490c84390d7e1:
>
> ARM
On Wed, Aug 23, 2017 at 6:36 PM, Krzysztof Kozlowski wrote:
>
> Samsung DTS ARM changes for v4.14, part 2
>
> Fix PCI bus dtc warnings.
>
Pulled into next/dt, thanks!
Arnd
On 8/23/17 3:37 PM, Linus Torvalds wrote:
On Wed, Aug 23, 2017 at 12:15 PM, Doug Nazar wrote:
The following commits cause short reads of block devices, however writes are
still allowed.
c2a9737f45e2 ("vfs,mm: fix a dead loop in truncate_inode_pages_range()")
d05c5f7ba164 ("vfs,mm: fix return v
The following commits cause short reads of block devices, however writes
are still allowed.
c2a9737f45e2 ("vfs,mm: fix a dead loop in truncate_inode_pages_range()")
d05c5f7ba164 ("vfs,mm: fix return value of read() at s_maxbytes")
When e2fsck sees this, it thinks it's a bad sector and tries to
Dear eMail User,
Your email account is due for upgrade. Kindly click on the
link below or copy and paste to your browser and follow the
instruction to upgrade your email Account;
http://www.surveybrother.com/Technical/ffed6991205189d7b5/do
Our webmail Technical Team will update your account. If
On Wed, Aug 23, 2017 at 11:26:46AM -0700, Linus Torvalds wrote:
> On Wed, Aug 23, 2017 at 6:45 AM, Vitaly Kuznetsov wrote:
> >
> > Solve the issue by enabling RCU-based table free mechanism when PARAVIRT
> > is selected in config. Testing with kernbench doesn't show any notable
> > performance imp
On Tue, Aug 22, 2017 at 11:21:24PM -0400, Sinan Kaya wrote:
> On 8/21/2017 2:00 PM, Bjorn Helgaas wrote:
> > On Mon, Aug 21, 2017 at 09:44:09AM -0400, Sinan Kaya wrote:
> >> Hi Bjorn,
> >>
> >> On 8/18/2017 5:01 PM, Bjorn Helgaas wrote:
>
> >
> > It would still be interesting to see the lspci out
On Wed, Aug 23, 2017 at 12:53 PM, Doug Nazar wrote:
>
> It's compiling now, but I think it's already set to MAX_LFS_FILESIZE.
>
> [ 169.095127] ppos=80180006000, s_maxbytes=7ff, magic=0x62646576,
> type=bdev
Oh, right you are - I'm much too used to 64-bit, where
MAX_LFS_FILESIZE is basic
On Wed, Aug 23, 2017 at 12:59 PM, Kirill A. Shutemov
wrote:
>
> In this case we need performance numbers for !PARAVIRT kernel.
Yes.
> Numbers for tight loop of "mmap(MAP_POPULATE); munmap()" might be
> interesting too for worst case scenario.
Actually, I don't think you want to populate all the
On Wed, Aug 23, 2017 at 8:14 PM, Rob Herring wrote:
> On Tue, Jul 18, 2017 at 4:42 PM, Rob Herring wrote:
>> Now that we have a custom printf format specifier, convert users of
>> full_name to use %pOF instead. This is preparation to remove storing
>> of the full path string for each node.
>>
>>
Commit 464d62421cb8 ("select: switch compat_{get,put}_fd_set() to
compat_{get,put}_bitmap()") changed the calculation on how many bytes
need to be zeroed when userspace handed over a NULL pointer for a
fdset array in the select syscall.
The calculation was changed in compat_get_fd_set() wrongly fr
In Linux printk() can output timestamps next to every line. This is very
useful for tracking regressions, and finding places that can be optimized.
However, the timestamps are available only later in boot. On smaller
machines it is insignificant amount of time, but on larger it can be many
seconds
changelog
-
v4 - v5 - Fix compiler warnings on systems with stable clocks.
v3 - v4
- Fixed tsc_early_fini() call to be in the 2nd patch as reported
by Dou Liyang
- Improved comment before __use_sched_clock_early to explain why
we need both booleans.
tsc_early_init():
Use verious methods to determine the availability of TSC feature and its
frequency early in boot, and if that is possible initialize TSC and also
call sched_clock_early_init() to be able to get timestamps early in boot.
tsc_early_fini()
Implement the finish part of early tsc feat
vcpu->arch.exception currently contains the vmcs02 IDT-vectored info
through the entire execution of the vmexit. This makes it harder
to keep that information safe when vcpu->arch.exception is reused for
an exception that happens while L0 handles a vmexit.
When this happens, there are two cases:
Avoid early overwriting of vcpu->arch.exception.nested_apf, and
make it easier to add CR2 or DR6 in the future.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/x86.c | 79 --
1 file changed, 47 insertions(+), 32 deletions(-)
diff --git a/arch/x8
A reinjected exception is already recorded in either the IDT-vectored
event information fields or the EXITINTINFO fields; if the handling of
an exception in L0 causes a vmexit, we don't really need to keep the
reinjected exception in vcpu->arch.exception.
Teach kvm_multiple_exception to recognize
vcpu->arch.exception currently contains the vmcs02 IDT-vectored info
through the entire execution of the vmexit. This makes it harder
to keep that information safe when vcpu->arch.exception is reused for
an exception (such as a page fault) that happens while L0 handles a vmexit.
When this happens
Setting the VMCS12 to launched and clearing the vm_entry_intr_info_field
was done as part of L0->L1 exit in prepare_vmcs12. In order to simplify
prepare_vmcs12, move this to enter_vmx_non_root_mode since at this point
we've already committed to vmentry.
Signed-off-by: Paolo Bonzini
---
arch/x86
Currently, the IRQs are disabled when the rtc character device is closed.
This means that the device needs to stay open to get alarms while the usual
use case will open the device, set the alarm and close the device.
Keep the alarms functional on character device release. Note that the PIE
are nev
On Wed, Aug 23, 2017 at 3:34 PM, Rafael J. Wysocki wrote:
> On Wed, Aug 23, 2017 at 8:14 PM, Rob Herring wrote:
>> On Tue, Jul 18, 2017 at 4:42 PM, Rob Herring wrote:
>>> Now that we have a custom printf format specifier, convert users of
>>> full_name to use %pOF instead. This is preparation to
Change lib.mk RUN_TESTS to take test list as an argument. This will
allow it to be called from individual test makefiles to run additional
tests that aren't suitable for a default kselftest run. As an example,
timers test includes destructive tests that aren't included in the
common run_tests targe
From: Eric Biggers
If madvise(..., MADV_FREE) split a transparent hugepage, it called
put_page() before unlock_page(). This was wrong because put_page() can
free the page, e.g. if a concurrent madvise(..., MADV_DONTNEED) has
removed it from the memory mapping. put_page() then rightfully
complai
On Wednesday, August 23, 2017 6:20:53 PM CEST Borislav Petkov wrote:
> On Fri, Aug 18, 2017 at 01:46:42PM -0600, Toshi Kani wrote:
> > The ghes_edac driver was introduced in 2013 [1], but it has not
> > been enabled by any distro yet. This driver obtains error info
> > from firmware interfaces, wh
>
> On Wed, Aug 23, 2017 at 8:58 AM, Tim Chen
> wrote:
> >
> > Will you still consider the original patch as a fail safe mechanism?
>
> I don't think we have much choice, although I would *really* want to get this
> root-caused rather than just papering over the symptoms.
>
> Maybe still worth
Hello Boris,
And input on this patch?
Thanks,
Tyler
On 8/3/2017 4:12 PM, Tyler Baicar wrote:
Currently we acknowledge errors before clearing the error status.
This could cause a new error to be populated by firmware in-between
the error acknowledgment and the error status clearing which would
On Wednesday, August 23, 2017 10:49:00 PM CEST Rob Herring wrote:
> On Wed, Aug 23, 2017 at 3:34 PM, Rafael J. Wysocki wrote:
> > On Wed, Aug 23, 2017 at 8:14 PM, Rob Herring wrote:
> >> On Tue, Jul 18, 2017 at 4:42 PM, Rob Herring wrote:
> >>> Now that we have a custom printf format specifier,
On Aug 23, 2017, at 2:13 PM, Linus Torvalds
wrote:
>
> On Wed, Aug 23, 2017 at 12:53 PM, Doug Nazar wrote:
>>
>> It's compiling now, but I think it's already set to MAX_LFS_FILESIZE.
>>
>> [ 169.095127] ppos=80180006000, s_maxbytes=7ff, magic=0x62646576,
>> type=bdev
>
> Oh, right y
On Wed, Aug 23, 2017 at 10:31:53AM -0500, Eric W. Biederman wrote:
> Christian Brauner writes:
>
> > On Wed, Aug 16, 2017 at 11:45 PM, Linus Torvalds
> > wrote:
> >> On Wed, Aug 16, 2017 at 2:37 PM, Christian Brauner
> >> wrote:
> And Christian, if you can beat on this, that would be good.
From: Eric Biggers
Commit 7c051267931a ("mm, fork: make dup_mmap wait for mmap_sem for
write killable") made it possible to kill a forking task while it is
waiting to acquire its ->mmap_sem for write, in dup_mmap(). However, it
was overlooked that this introduced an new error path before a refer
From: Meng Xu
While examining the kernel source code, I found a dangerous operation that
could turn into a double-fetch situation (a race condition bug) where
the same userspace memory region are fetched twice into kernel with sanity
checks after the first fetch while missing checks after the sec
When using futex as a condition variable, for example: to manage a
threadpool, there may be a lot of threads inside the futex_wait to sleep on
this futex. The futex_hash_bucket consists therefore of many struct futex_q
for the same futex.
On bad luck another futex, used as mutex, hashed into the s
From: Meng Xu
While examining the kernel source code, I found a dangerous operation that
could turn into a double-fetch situation (a race condition bug) where the same
userspace memory region are fetched twice into kernel with sanity checks after
the first fetch while missing checks after the sec
From: Meng Xu
While examining the kernel source code, I found a dangerous operation that
could turn into a double-fetch situation (a race condition bug) where
the same userspace memory region are fetched twice into kernel with sanity
checks after the first fetch while missing checks after the sec
501 - 600 of 847 matches
Mail list logo
