From: Hanjun Guo
Cleanup acpi_numa_processor_affinity_init() in preparation for its
move to drivers/acpi/numa.c. It will be reused by arm64, this has no
functional change.
Signed-off-by: Hanjun Guo
Signed-off-by: Robert Richter
Signed-off-by: David Daney
---
arch/x86/mm/srat.c | 21 +---
From: Robert Richter
Since acpi_numa_arch_fixup() is only used in arch ia64, move it there
to make a generic interface easier. This avoids empty function stubs
or some complex kconfig options for x86 and arm64.
Signed-off-by: Robert Richter
Reviewed-by: Hanjun Guo
Signed-off-by: David Daney
-
From: Hanjun Guo
Rework numa_add_memblk() to update the parameter "u64 size" to "u64
end", this will make it consistent with x86 and simplifies the arm64
ACPI NUMA code to be added later.
Signed-off-by: Hanjun Guo
Signed-off-by: Robert Richter
Signed-off-by: David Daney
Acked-by: Catalin Mari
From: David Daney
Rebased to Linus' master branch at commit 1d6da87a3241 ("Merge branch
'drm-next' of git://people.freedesktop.org/~airlied/linux")
ACPI 5.1 already introduced NUMA support for ARM64, which can get the
NUMA domain information from SRAT and SLIT table, so parse those two
tables to
On Tue, May 24, 2016 at 12:57 AM, Wanpeng Li wrote:
> From: Wanpeng Li
>
> If an emulated lapic timer will fire soon(in the scope of 10us the
> base of dynamic halt-polling, lower-end of message passing workload
> latency TCP_RR's poll time < 10us) we can treat it as a short halt,
> and poll to w
From: David Daney
As noted by Dennis Chen, we don't want to print "No NUMA configuration
found" if NUMA was forced off from the command line.
Change the type of numa_off to bool, and clean up printing code.
Print "NUMA disabled" if forced off on command line and "No NUMA
configuration found" if
From: Hanjun Guo
Identical implementations of acpi_numa_slit_init() are used by both
x86 and follow-on arm64 support. Move it to drivers/acpi/numa.c, and
guard with CONFIG_X86 || CONFIG_ARM64 because ia64 has its own
architecture specific implementation.
No code change.
Signed-off-by: Hanjun G
From: Hanjun Guo
The argument "header" for acpi_table_print_srat_entry()
is always checked before the function is called, it's
duplicate to check it again, remove it.
Signed-off-by: Hanjun Guo
Signed-off-by: Robert Richter
Signed-off-by: David Daney
---
drivers/acpi/numa.c | 3 ---
1 file ch
On 05/24, Michal Hocko wrote:
>
> On Mon 23-05-16 17:14:19, Oleg Nesterov wrote:
> > On 05/23, Michal Hocko wrote:
> [...]
> > > Could you add some tracing and see what are the numbers
> > > above?
> >
> > with the patch below I can press Ctrl-C when it hangs, this breaks the
> > endless loop and t
On Tue, May 24, 2016 at 3:23 PM, Linus Torvalds
wrote:
>
> Just as an example: code that does
>
> dir->i_mtime = dir->i_ctime = CURRENT_TIME_SEC;
>
> could pretty mechanically be converted to
>
> dir->i_mtime = dir->i_ctime = current_fs_time(sb);
Actually, looking at the users, mo
On Tue, 24 May 2016, David Laight wrote:
> > > Related, please can we have a flag for the sleep and/or process so that
> > > an uninterruptible sleep doesn't trigger the 'hung task' detector
> >
> > TASK_KILLABLE
>
> Not sure that does what I want.
> It appears to allow some 'kill' actions to wa
If a uaccess instruction fails due to an8 error other than #PF,
warn. If the fault is #GP, it most likely indicates access to a
non-canonical address, which means that an access_ok check is
missing, and that's bad. If the fault is something else (#UD?),
then something is very wrong and we should
> Tony / Borislav, do we have tests for the machine check code that could
> have caught this?
If I had built one of my recovery test programs as a 32-byte binary instead of
native 64-bit I might have noticed (I only print the lsb field ... which would
have been garbage on the stack, maybe I'd ha
If someone calls set_fs(KERNEL_DS), then they are responsible for
making sure that whatever addresses are accessed are safe. If they
get it wrong on a kernel address, OOPS. If they get it wrong on a user
address, warn.
This will make it harder to exploit bugs in which user code controls
a pointe
If a uaccess in USER_DS mode faults on a kernel address, it is
reasonably like to be an exploitable bug. Make it more obvious in
testing and make it harder to exploit in practice by letting it
OOPS.
Signed-off-by: Andy Lutomirski
---
arch/x86/mm/extable.c | 18 ++
1 file changed
Exception handlers might want to know the error code and, for some
exceptions, some other auxiliarry info. Pass in the error code and
an 'extra' parameter. For page faults, 'extra' is cr2.
The kprobe code is incomprehensible to me. For kprobe fixups, just
pass zeroes.
Signed-off-by: Andy Lutom
This will help debug OOPSes related to USER_DS vs KERNEL_DS.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/dumpstack_32.c | 4
arch/x86/kernel/dumpstack_64.c | 5 +
2 files changed, 9 insertions(+)
diff --git a/arch/x86/kernel/dumpstack_32.c b/arch/x86/kernel/dumpstack_32.c
index
This will give us a single piece of code to edit to harden our
uaccess fault handling.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/uaccess.h | 16
arch/x86/lib/getuser.S | 12 ++--
arch/x86/lib/putuser.S | 10 +-
arch/x86/mm/extable.c
This series hardens x86's uaccess code a bit. It adds warnings for
some screwups, adds an OOPS for a major exploitable screwup, and it
improves debuggability a bit by indicating non-default fs in oopses.
It shouldn't cause any new OOPSes except in the particularly
dangerous case where the kernel
In aa1acff356bb ("x86/xen: Probe target addresses in
set_aliased_prot() before the hypercall"), I added an explicit probe
to work around a hypercall issue. The code can be simplified by
using probe_kernel_read.
Cc: Andrew Cooper
Cc: Boris Ostrovsky
Cc: David Vrabel
Cc: Jan Beulich
Cc: Konrad
Currently, the trace_printk code chooses which static buffer to use based
on what type of atomic context (NMI, IRQ, etc) it's in. Simplify the
code and make it more robust: simply count the nesting depth and choose
a buffer based on the current nesting depth.
The new code will only drop an event
Forcing in_interrupt() to return true if we're not in a bona fide
interrupt confuses the softirq code. This fixes warnings like:
NOHZ: local_softirq_pending 282
that can happen when running things like selftests/x86.
This will change perf's static percpu buffer usage in IST context.
I think thi
On 05/23/2016 02:55 AM, Miklos Szeredi wrote:
> C is slave of B is slave of A. If a process can see (i.e. has under
> its root) A and C but not B then for C it will show
> master:B,propagate_from:A. This piece of information is shown because
> it can't see the immediate master (B) and so cannot d
On Tue, 24 May 2016 15:52:28 -0700
Andy Lutomirski wrote:
> Currently, the trace_printk code chooses which static buffer to use based
> on what type of atomic context (NMI, IRQ, etc) it's in. Simplify the
> code and make it more robust: simply count the nesting depth and choose
> a buffer based
Hi, Joerg
Not sure whether you think this calculation is correct.
If I missed something for this " + 1" in your formula, I am glad to hear your
explanation. So that I could learn something from you :-)
Have a good day~
On Sat, May 21, 2016 at 02:41:51AM +, Wei Yang wrote:
>In commit <8bf478
2016-05-25 6:38 GMT+08:00 David Matlack :
> On Tue, May 24, 2016 at 12:57 AM, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> If an emulated lapic timer will fire soon(in the scope of 10us the
>> base of dynamic halt-polling, lower-end of message passing workload
>> latency TCP_RR's poll time < 10us)
2016-05-25 1:15 GMT+08:00 Christian Borntraeger :
> On 05/24/2016 09:57 AM, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> If an emulated lapic timer will fire soon(in the scope of 10us the
>> base of dynamic halt-polling, lower-end of message passing workload
>> latency TCP_RR's poll time < 10us) we
Hi Rafal,
some comments in line.
On 16-05-22 03:09 PM, Rafał Miłecki wrote:
> Northstar is a family of SoCs used in home routers. They have USB 2.0
> and 3.0 controllers with PHYs that need to be properly initialized.
> This driver provides PHY init support in a generic way and can be bound
> wi
On 05/23, Andy Lutomirski wrote:
>
> I'm guessing you're either hitting a subtle bug in the mess that is
> breakpoint handling or you're hitting a bug in perf's context switch
> code.
yes, same feeling...
> Given that the breakpoint gets missed many times in a row,
yes, the child specially tries
On Wed, Apr 27, 2016 at 09:25:57AM -0600, Toshi Kani wrote:
> On x86, ioremap() and remap_pfn_range() fail on conflicting cache
> type of an alias mapping request only if the case is not allowed
> by the rule set in is_new_memtype_allowed(). While this exemption
> is necessary for remap_pfn_range()
On 5/24/2016 11:32 AM, Mark Brown wrote:
> On Tue, May 24, 2016 at 08:03:48PM +0200, Christer Weinigel wrote:
>> On 05/24/2016 07:20 PM, Mark Brown wrote:
>
>>> I'm not sure this is something we want to support at all, I can't
>>> immediately see anything that does this deliberately in the SPI
>>
Dan, Toshi, Christoph,
I recall a while ago while memremap() was being introduced we
discussed making stronger semantics for memremap() a desirable future
goal [0], along with removal cleanups of ioremap_cache(). This was
when only 2 types were being considered, WB and WT. I see we now have
WC as
On Tue, May 24, 2016 at 4:11 PM, Wanpeng Li wrote:
> 2016-05-25 6:38 GMT+08:00 David Matlack :
>> On Tue, May 24, 2016 at 12:57 AM, Wanpeng Li wrote:
>>> From: Wanpeng Li
>>>
>>> If an emulated lapic timer will fire soon(in the scope of 10us the
>>> base of dynamic halt-polling, lower-end of mes
On 24 May 2016 at 10:32, Kees Cook wrote:
> On Mon, May 23, 2016 at 3:15 PM, Emese Revfy wrote:
> > This plugin mitigates the problem of the kernel having too little entropy
> > during
> > and after boot for generating crypto keys.
> >
> I'm excited to see this! This looks like it'll help a lot
On Tue, May 24, 2016 at 05:31:51PM -0500, Matthew McClintock wrote:
>
> > On May 24, 2016, at 2:36 PM, Larry Finger wrote:
> >
> > On 05/24/2016 02:25 PM, Matthew McClintock wrote:
> >> On May 24, 2016, at 2:16 PM, Larry Finger
> >> wrote:
> >>>
> >>> On 05/24/2016 02:13 PM, Matthew McClintoc
On Tuesday, May 24, 2016 05:47:17 PM Viresh Kumar wrote:
> On 24-05-16, 14:13, Rafael J. Wysocki wrote:
> > I don't really get it why you don't like get/put_online_cpus() so much.
>
> Not that I don't like them, I just wanted to see if its possible to
> work without any additional locking.
>
> An
Media Device Allocator API to allows multiple drivers share a media device.
Using this API, drivers can allocate a media device with the shared struct
device as the key. Once the media device is allocated by a driver, other
drivers can get a reference to it. The media device is released when all
th
Change au0828 to use Media Device Allocator API to allocate media device
with the parent usb struct device as the key, so it can be shared with the
snd usb audio driver.
Signed-off-by: Shuah Khan
---
drivers/media/usb/au0828/au0828-core.c | 12
drivers/media/usb/au0828/au0828.h
Media Device Allocator API to allows multiple drivers share a media device.
Using this API, drivers can allocate a media device with the shared struct
device as the key. Once the media device is allocated by a driver, other
drivers can get a reference to it. The media device is released when all
th
This patch calls mark_inode_dirty_sync() for the following on-disk inode
changes.
-> largest
-> ctime/mtime/atime
-> i_current_depth
-> i_xattr_nid
-> i_pino
-> i_advise
-> flags
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/dir.c | 14 ++---
fs/f2fs/extent_cache.c | 24 +++
If roll-forward recovery can recover i_size, we don't need to update inode's
metadata during fsync.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 3 +++
fs/f2fs/f2fs.h | 23 +--
fs/f2fs/file.c | 4 ++--
fs/f2fs/inode.c| 3 +++
fs/f2fs/node.c | 9
This patch sets flush_merge by default.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/super.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index d0426a3..5696dff 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -86,6 +86,7 @@ enum {
Opt_inline
This patch removes writepages lock.
We can improve multi-threading performance.
tiobench, 32 threads, 4KB write per fsync on SSD
Before: 25.88 MB/s
After: 28.03 MB/s
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 7 ---
fs/f2fs/f2fs.h | 1 -
fs/f2fs/super.c | 1 -
3 files changed, 9 dele
This patch reduces to call them across the whole tree.
- sync_inode_page()
- update_inode_page()
- update_inode()
- f2fs_write_inode()
Instead, checkpoint will flush all the dirty inode metadata before syncing
node pages.
Note that, this is doable, since we call mark_inode_dirty_sync() for all
ino
This patch introduces f2fs_i_blocks_write() to call mark_inode_dirty_sync() when
changing inode->i_blocks.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 1 -
fs/f2fs/f2fs.h | 17 +
2 files changed, 13 insertions(+), 5 deletions(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
This patch adds lazytime support.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/super.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index e9e81cb..d0426a3 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -93,6 +93,8 @@ enum {
Opt_no
This patch registers all the inodes which have dirty metadata to sync when
checkpoint is doing.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 36
fs/f2fs/debug.c | 5 +++--
fs/f2fs/f2fs.h | 8 ++--
fs/f2fs/inode.c | 6 +-
fs
If flush commands do not incur any congestion, we don't need to throw that to
dispatching queue which causes unnecessary latency.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h| 1 +
fs/f2fs/segment.c | 7 ++-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/f2fs.h b/
This patch refactors to use inode pointer for set_inode_flag and
clear_inode_flag.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/acl.c | 7 ++---
fs/f2fs/checkpoint.c | 15 --
fs/f2fs/data.c | 21 +++---
fs/f2fs/dir.c | 22 +++
fs/f2fs/extent_cac
This patch introduces f2fs_i_size_write() to call mark_inode_dirty_sync() with
i_size_write().
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 10 --
fs/f2fs/dir.c | 2 +-
fs/f2fs/f2fs.h | 6 ++
fs/f2fs/file.c | 10 --
fs/f2fs/inline.c | 6 +++---
fs/f2f
This patch introduces f2fs_i_links_write() to call mark_inode_dirty_sync() when
changing inode->i_links.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 1 +
fs/f2fs/dir.c| 10 +-
fs/f2fs/f2fs.h | 9 +
fs/f2fs/namei.c | 24 ++--
4 fi
On Tue, May 24, 2016 at 3:44 PM, Linus Torvalds
wrote:
> On Tue, May 24, 2016 at 3:23 PM, Linus Torvalds
> wrote:
>>
>> Just as an example: code that does
>>
>> dir->i_mtime = dir->i_ctime = CURRENT_TIME_SEC;
>>
>> could pretty mechanically be converted to
>>
>> dir->i_mtime = dir
Hi Laurent
> > From: Kuninori Morimoto
> >
> > EPROBE_DEFER is not error, thus, error message on kernel log on this
> > case is confusable for user. Prints it only error cases.
> >
> > Signed-off-by: Kuninori Morimoto
> > ---
> > drivers/gpu/drm/rcar-du/rcar_du_drv.c | 6 --
> > 1 file c
On 5/24/2016 4:34 PM, Frank Rowand wrote:
> On 5/24/2016 11:32 AM, Mark Brown wrote:
>> On Tue, May 24, 2016 at 08:03:48PM +0200, Christer Weinigel wrote:
>>> On 05/24/2016 07:20 PM, Mark Brown wrote:
>>
I'm not sure this is something we want to support at all, I can't
immediately see an
On Tue, 2016-05-24 at 01:53 -0700, Christoph Hellwig wrote:
[snipped]
>
> That goes on to the next question: why do we even need a config option
> for 16TB+ volume support?
>
I believe that it makes sense to have config option during
implementation phase. I mean that it needs to protect this ex
On Tue, May 24, 2016 at 11:06:52AM -0700, Paul E. McKenney wrote:
> On Mon, May 23, 2016 at 12:35:35PM +0800, Boqun Feng wrote:
> > On Sun, May 22, 2016 at 08:28:06AM -0700, Paul E. McKenney wrote:
> > > On Sun, May 22, 2016 at 02:26:49PM +0800, Boqun Feng wrote:
> > > > Hi Paul,
> > > >
> > > > O
This patch adds a struct device_node pointer to struct mtd_partition.
Partitions parsed via ofpart can now be referenced via devicetree.
Cc: David Woodhouse
Cc: Brian Norris
Signed-off-by: Moritz Fischer
---
Hi all,
during my work on another patch series for supporting
otp regions as nvmem pr
Hi David, Laurent
These removes unneeded error message from Renesas DU driver.
Current this unneeded error message makes user confuse.
Kuninori Morimoto (2):
drm: rcar-du: error message is not needed for drm_vblank_init()
drm: rcar-du: error message is not needed for EPROBE_DEFER
d
From: Kuninori Morimoto
The only reason drm_vblank_init() could return an error at the
moment is a kcalloc() failure.
So we can remove current error message completely.
Signed-off-by: Kuninori Morimoto
---
v1 -> v2
- just removed error message
drivers/gpu/drm/rcar-du/rcar_du_drv.c | 4 +---
From: Kuninori Morimoto
EPROBE_DEFER is not error, thus, error message on kernel log on this
case is confusable. Print it only error cases
Signed-off-by: Kuninori Morimoto
---
v1 -> v2
- only for rcar_du_modeset_init()
drivers/gpu/drm/rcar-du/rcar_du_drv.c | 3 ++-
1 file changed, 2 inserti
2016-05-25 7:37 GMT+08:00 David Matlack :
> On Tue, May 24, 2016 at 4:11 PM, Wanpeng Li wrote:
>> 2016-05-25 6:38 GMT+08:00 David Matlack :
>>> On Tue, May 24, 2016 at 12:57 AM, Wanpeng Li wrote:
From: Wanpeng Li
If an emulated lapic timer will fire soon(in the scope of 10us the
>
On Wed, May 25, 2016 at 2:00 AM, Rafael J. Wysocki wrote:
> On Tuesday, May 24, 2016 05:47:17 PM Viresh Kumar wrote:
>> On 24-05-16, 14:13, Rafael J. Wysocki wrote:
>> > I don't really get it why you don't like get/put_online_cpus() so much.
>>
>> Not that I don't like them, I just wanted to see i
>> +static inline bool __pmonr__in_instate(struct pmonr *pmonr)
>> +{
>> + lockdep_assert_held(&__pkg_data(pmonr, pkg_data_lock));
>> + return __pmonr__in_istate(pmonr) && !__pmonr__in_ilstate(pmonr);
>> }
>
> This state tracking sucks. It's completely non obvious which combinations of
> m
> On Tue, May 24, 2016 at 02:36:08PM +, Li, Liang Z wrote:
> > > > > > > This can be pre-initialized, correct?
> > > > > >
> > > > > > pre-initialized? I am not quite understand your mean.
> > > > >
> > > > > I think you can maintain sg as part of device state and init sg
> > > > > with the
> >
On Tue, 2016-05-24 at 01:52 -0700, Christoph Hellwig wrote:
> On Mon, May 23, 2016 at 01:08:05PM -0700, Viacheslav Dubeyko wrote:
> > I think that it's some confusion. I didn't introduce any new fields in
> > struct f2fs_super_block. The "major_ver" and "minor_ver" fields exist in
> > F2FS superblo
8a365a8b71dabad7169896c3e75f253e8b # 01:56 27+
> 0 Merge
> 'linux-review/Rajneesh-Bhardwaj/platform-x86-Add-PMC-Driver-for-Intel-Core-SoC/20160524-222735'
> into devel-catchup-201605250104
> > git bisect bad 5c7f53f3c9182146efd37be1989f8e23e3b796ff # 02:01
> On May 24, 2016, at 6:41 PM, Al Viro wrote:
>
> Again, I understand what's going on kernel-side; the only tricky part is how
> to fix it without bringing the nasal daemons back. I think I have a solution
> and I'm going to post it tonight if it survives the local beating. In any
> case, the
> > > > > > > This is grossly inefficient if you only requested a single page.
> > > > > > > And it's also allocating memory very aggressively without
> > > > > > > ever telling the host what is going on.
> > > > > >
> > > > > > If only requested a single page, there is no need to send the
> > > >
Hi Jaegeuk,
On Mon, 2016-05-23 at 14:13 -0700, Jaegeuk Kim wrote:
> Hi Slava,
>
> On Thu, May 19, 2016 at 10:46:06AM -0700, Viacheslav Dubeyko wrote:
> ...
> >
> > +#ifdef CONFIG_F2FS_16TB_VOLUME_SUPPORT
> > +#define F2FS_MAX_SUPP_MAJOR_VERSION(2)
> > +#define F2FS_MIN_16TB_VOLU
On Tue, May 24, 2016 at 07:58:13PM -0500, Matthew McClintock wrote:
>
> > On May 24, 2016, at 6:41 PM, Al Viro wrote:
> >
> > Again, I understand what's going on kernel-side; the only tricky part is how
> > to fix it without bringing the nasal daemons back. I think I have a
> > solution
> > an
On Tue, May 24, 2016 at 4:30 PM, Rob Landley wrote:
>
>
> On 05/23/2016 06:29 PM, Rob Herring wrote:
>> On Mon, May 23, 2016 at 4:03 PM, Rich Felker wrote:
>>> On Mon, May 23, 2016 at 03:48:46PM -0500, Rob Herring wrote:
On Fri, May 20, 2016 at 02:53:03AM +, Rich Felker wrote:
> Sign
From: Kuninori Morimoto
commit 93c667ca2598bd84f1bd3f2fa176af69707699fe
("of: *node argument to of_parse_phandle_with_args should be const")
changed to const for struct device node *np,
but it cares CONFIG_OF case only, !CONFIG_OF case need it too.
Signed-off-by: Kuninori Morimoto
---
include/
> On May 24, 2016, at 8:10 PM, Al Viro wrote:
>
> Slap the WARN_ON(!size); in the very beginning of iov_iter_advance(), see
> where it's triggered...
diff --git a/lib/iov_iter.c b/lib/iov_iter.c
index 28cb431..d89e154 100644
--- a/lib/iov_iter.c
+++ b/lib/iov_iter.c
@@ -488,6 +488,7 @@ EXPORT_S
0day found a boot warning triggered in rcu_perf_writer() on !SMP kernel:
WARN_ON(rcu_gp_is_normal() && gp_exp);
, the root cause of which is trying to measure expedited grace
periods(by setting gp_exp to true by default) when all the grace periods
are normal(TINY RCU only has normal grace
On 05/23/2016 02:46 PM, Jason Low wrote:
On Sat, 2016-05-21 at 09:04 -0700, Peter Hurley wrote:
On 05/18/2016 12:58 PM, Jason Low wrote:
It should be fine to use the standard READ_ONCE here, even if it's just
for documentation, as it's probably not going to cost anything in
practice. It would b
On Tue, May 24, 2016 at 08:20:46PM -0500, Matthew McClintock wrote:
>
> > On May 24, 2016, at 8:10 PM, Al Viro wrote:
> >
> > Slap the WARN_ON(!size); in the very beginning of iov_iter_advance(), see
> > where it's triggered...
>
> diff --git a/lib/iov_iter.c b/lib/iov_iter.c
> index 28cb431..d
2016-05-25 8:47 GMT+08:00 Wanpeng Li :
> 2016-05-25 7:37 GMT+08:00 David Matlack :
>> On Tue, May 24, 2016 at 4:11 PM, Wanpeng Li wrote:
>>> 2016-05-25 6:38 GMT+08:00 David Matlack :
On Tue, May 24, 2016 at 12:57 AM, Wanpeng Li wrote:
> From: Wanpeng Li
>
> If an emulated lapic
Hi Linus,
On Mon, 23 May 2016 12:10:25 -0700 Linus Torvalds
wrote:
>
> Is there a patch pending for this that I'm not aware of, or is it just
> that nobody but me hates spurious warnings? Didn't this show up in
> linux-next? And if it _did_ show up in linux-next, why was the pull
> request not t
> On May 24, 2016, at 8:28 PM, Al Viro wrote:
>
> The next obvious question is which binary it is and what's the return
> address to userland; make that
> if (!size)
> printk(KERN_ERR "crap in %s[%x]",
> current->comm,
> current_pt_
On 25-05-16, 02:48, Rafael J. Wysocki wrote:
> I'm actually considering making the stats code non-modular.
>
> It won't have a reason to use notifiers then and may be simplified
> quite a bit this way. As an added benefit, if it doesn't use the
> transition notifier, it won't interfere with fast
On 2016/5/25 7:37, David Matlack wrote:
On Tue, May 24, 2016 at 4:11 PM, Wanpeng Li wrote:
2016-05-25 6:38 GMT+08:00 David Matlack :
On Tue, May 24, 2016 at 12:57 AM, Wanpeng Li wrote:
From: Wanpeng Li
If an emulated lapic timer will fire soon(in the scope of 10us the
base of dynamic halt-
On 05/24/2016 02:17 PM, Madhavan Srinivasan wrote:
>
>
> On Monday 23 May 2016 08:48 PM, Shreyas B. Prabhu wrote:
>> POWER ISA v3 defines a new idle processor core mechanism. In summary,
>> a) new instruction named stop is added. This instruction replaces
>> instructions like nap, sleep,
Ping Paolo or Peterz.
2016-05-25 3:22 GMT+08:00 Rik van Riel :
> On Wed, 2016-05-18 at 20:27 +0800, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> This patch adds steal guest time support to full dynticks CPU
>> time accounting. After 'commit ff9a9b4c4334 ("sched, time: Switch
>> VIRT_CPU_ACCOUNTING_
On 05/24/2016 03:54 PM, Gautham R Shenoy wrote:
> Hi Shreyas,
>
> On Mon, May 23, 2016 at 08:48:40PM +0530, Shreyas B. Prabhu wrote:
>> @@ -412,7 +517,8 @@ subcore_state_restored:
>> first_thread_in_core:
>>
>> /*
>> - * First thread in the core waking up from fastsleep. It needs to
>>
On 2016/5/25 2:40, Arnaldo Carvalho de Melo wrote:
Em Tue, May 24, 2016 at 02:29:00AM +, Wang Nan escreveu:
This patch allows following config terms and option:
Globally setting events to overwrite;
# perf record --overwrite ...
Set specific events to be overwrite or no-overwrite.
We prefer to use the pr_* to print out the log now, this patch converts
the printk to pr_info. In the error path, use the pr_err to replace the
printk.
Signed-off-by: Huang Shijie
---
samples/kprobes/jprobe_example.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/sampl
We prefer to use the pr_* to print out the log now, this patch converts
the printk to pr_info. In the error path, use the pr_err to replace the
printk.
Signed-off-by: Huang Shijie
---
samples/kprobes/kretprobe_example.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --g
The regs_return_value() returns "unsigned long" or "long" value.
But the retval is int type now, it may cause overflow, the log may
becomes:
.
[ 2911.078869] do_brk returned -2003877888 and took 4620 ns to execute
This patch converts the retval to "unsi
On Tue, May 24, 2016 at 09:09:41AM +0100, Marc Zyngier wrote:
> On 23/05/16 22:13, Rich Felker wrote:
> > On Mon, May 23, 2016 at 03:53:20PM -0500, Rob Herring wrote:
> >> On Fri, May 20, 2016 at 02:53:04AM +, Rich Felker wrote:
> >>> Signed-off-by: Rich Felker
> >>> ---
> >>> .../bindings/in
We prefer to use the pr_* to print out the log now, this patch converts
the printk to pr_info. In the error path, use the pr_err to replace the
printk.
Signed-off-by: Huang Shijie
---
samples/kprobes/kprobe_example.c | 29 -
1 file changed, 12 insertions(+), 17 deleti
On Wed, May 25, 2016 at 09:25:33AM +0800, Boqun Feng wrote:
> 0day found a boot warning triggered in rcu_perf_writer() on !SMP kernel:
>
> WARN_ON(rcu_gp_is_normal() && gp_exp);
>
> , the root cause of which is trying to measure expedited grace
> periods(by setting gp_exp to true by default
On Tue, May 24, 2016 at 08:13:14PM -0500, Rob Herring wrote:
> On Tue, May 24, 2016 at 4:30 PM, Rob Landley wrote:
> >
> >
> > On 05/23/2016 06:29 PM, Rob Herring wrote:
> >> On Mon, May 23, 2016 at 4:03 PM, Rich Felker wrote:
> >>> On Mon, May 23, 2016 at 03:48:46PM -0500, Rob Herring wrote:
> >
From: Wanpeng Li
If an emulated lapic timer will fire soon(in the scope of 10us the
base of dynamic halt-polling, lower-end of message passing workload
latency TCP_RR's poll time < 10us) we can treat it as a short halt,
and poll to wait it fire, the fire callback apic_timer_fn() will set
KVM_REQ_
On Tue, May 24, 2016 at 12:45:46PM +0300, Roger Quadros wrote:
> Hi Peter,
>
> I have one question here. Please see below.
>
> On 13/05/16 13:03, Roger Quadros wrote:
> > It provides APIs for the following tasks
> >
> > - Registering an OTG/dual-role capable controller
> > - Registering Host and
On Tue, May 24, 2016 at 4:40 PM, PaX Team wrote:
> On 24 May 2016 at 10:32, Kees Cook wrote:
>
>> On Mon, May 23, 2016 at 3:15 PM, Emese Revfy wrote:
>> > This plugin mitigates the problem of the kernel having too little entropy
>> > during
>> > and after boot for generating crypto keys.
>> >
>>
On Tue, May 24, 2016 at 09:06:03PM -0500, Matthew McClintock wrote:
>
> > On May 24, 2016, at 8:28 PM, Al Viro wrote:
> >
> > The next obvious question is which binary it is and what's the return
> > address to userland; make that
> > if (!size)
> > printk(KERN_ERR "crap in %s[%x
Hi Santosh,
On Tuesday 24 May 2016 09:59 PM, Santosh Shilimkar wrote:
Hi Keerthy,
On 5/23/2016 8:56 PM, Keerthy wrote:
On Tuesday 24 May 2016 09:07 AM, Lokesh Vutla wrote:
On Monday 23 May 2016 05:59 PM, Keerthy wrote:
keystone-k2l devices use pinmux and are compliant with PINCTRL_SINGLE
Hi Javi,
Thanks your reviewing.
On 2016年05月24日 20:57, Javi Merino wrote:
On Tue, May 03, 2016 at 05:33:29PM +0800, Caesar Wang wrote:
From: Sascha Hauer
This adds support for hardware-tracked trip points to the device tree
thermal sensor framework.
The framework supports an arbitrary number
Hi Javi,
On 2016年05月24日 21:01, Javi Merino wrote:
On Tue, May 03, 2016 at 05:33:30PM +0800, Caesar Wang wrote:
From: Sascha Hauer
This patch implemnets .set_trips for device tree thermal zones.
As the hardware-tracked trip points is supported by thermal core patch[0].
patch[0]
"thermal: Add
On Mon, May 23, 2016 at 04:02:06PM -0500, Andy Gross wrote:
> On 23 May 2016 at 14:26, Kevin Hilman wrote:
> > Hi Andy,
> >
> > On Thu, May 12, 2016 at 8:46 PM, Andy Gross wrote:
> >> This patch converts the Qualcomm SCM driver to use the streaming DMA APIs
> >> for communication buffers.
> >>
>
601 - 700 of 812 matches
Mail list logo
