The glibc __LONG_LONG_PAIR passes arguments in a different
order for BE platforms vs LE platforms. Adjust the expectations
in the kernel 32-bit syscall routines for BE to match.
Signed-off-by: Chris Metcalf
---
arch/tile/kernel/compat.c | 35 ++-
arch/tile/kernel
On 06/15/2016 01:45 PM, Peter Zijlstra wrote:
On Tue, Jun 14, 2016 at 06:48:08PM -0400, Waiman Long wrote:
+++ b/arch/alpha/include/asm/rwsem.h
@@ -17,9 +17,9 @@
#define RWSEM_UNLOCKED_VALUE 0xL
#define RWSEM_ACTIVE_BIAS 0x0001L
#define RWSE
On 06/15/2016 06:03 PM, Keith Busch wrote:
On Wed, Jun 15, 2016 at 05:28:54PM +0200, Bart Van Assche wrote:
On 06/15/2016 05:14 PM, Keith Busch wrote:
I think the idea is have the irq_affinity mask match the CPU mapping on
the submission side context associated with that particular vector. If
t
On Wed, Jun 15, 2016 at 07:13:39PM +, Mathieu Desnoyers wrote:
> - On Jun 15, 2016, at 2:18 PM, Josh Poimboeuf jpoim...@redhat.com wrote:
>
> > On Wed, Jun 15, 2016 at 04:55:16PM +, Mathieu Desnoyers wrote:
> >> Hi Josh,
> >>
> >> I notice that with gcc 6.1.1, kernel 4.6, with
> >> CO
On 06/15/2016 01:38 PM, Peter Zijlstra wrote:
On Tue, Jun 14, 2016 at 06:48:06PM -0400, Waiman Long wrote:
static bool rwsem_optimistic_spin(struct rw_semaphore *sem)
{
- bool taken = false;
+ bool taken = false, can_spin;
I would place the variables without assignment first.
On Mon, Jun 13, 2016 at 1:42 AM, Xing Zheng wrote:
> Because we need to support the multiple codecs (MAX98357A/RT5514/DA7219)
> on the RK3399 GRU boards, this patch can help us to support these codecs.
>
> Signed-off-by: Xing Zheng
> ---
>
> Changes in v5:
> - fix the build warning for missing I2
First patch describe problem about 0xe045 code. Second and third are just
cosmetic and last rework code which processing WMI events. It should be
properly tested on more Dell machines, to check that everything is still
working correctly.
Changes since v2:
* Updated description for 2/4 and 4/4
* Fi
This patch reworks code for generating sparse keymap and processing WMI
events. It unifies procedure for generating sparse keymap and also unifies
big switch code for processing WMI events of different types. After this
patch dell-wmi driver does not differ between "old" and "new" hotkey type.
It
For better readability of keymap table, sort events by codes and also
update comments for events to be more informative.
Signed-off-by: Pali Rohár
Tested-by: Michał Kępień
Reviewed-by: Michał Kępień
---
drivers/platform/x86/dell-wmi.c | 29 -
1 file changed, 16 in
>From Dell we know that WMI event code 0xe045 is for Num Lock key, but it is
unclear due to message in commit 0b3f6109f0c9 ("dell-wmi: new driver for
hotkey control").
Signed-off-by: Pali Rohár
Tested-by: Michał Kępień
Reviewed-by: Michał Kępień
Cc: Matthew Garrett
Cc: Mario Limonciello
Link:
ACPI DSDT tables have defined other WMI codes, but does not contain any
description when those codes are emitted. Some other codes can be found in
logs on internet. In this patch are all which I saw, but lot of them are
not tested properly (e.g. for duplicate events with AT keyboard). Now we
have a
On Wednesday 08 June 2016 12:44:44 Gabriele Mazzotta wrote:
> On 08/06/2016 08:02, mario_limoncie...@dell.com wrote:
> >> -Original Message-
> >> From: Pali Rohár [mailto:pali.ro...@gmail.com]
> >> Sent: Tuesday, June 7, 2016 6:00 PM
> >> To: Gabriele Mazzotta ; Limonciello, Mario
> >>
> >
Hi Madhavan,
On Wed, Jun 15, 2016 at 05:12:53PM +0530, Madhavan Srinivasan wrote:
> When decoding the perf_regs mask in regs_dump__printf(),
> we loop through the mask using find_first_bit and find_next_bit functions.
> And mask is of type "u64". But "u64" is send as a "unsigned long *" to
> lib f
Hello,
On Wed, 15 Jun 2016, Quentin Armitage wrote:
> I am updating the patches in line with your comments, but I'm not sure about
> a couple of points.
>
> Patch 4:
>
> You state that before bind(), such changes should be safe. However, from the
> function make_send_sock(), when the f
On Wed, Jun 15, 2016 at 09:36:54PM +0200, Bart Van Assche wrote:
> Sorry that I had not yet this made this clear but my concern is about a
> system equipped with two or more adapters and with more CPU cores than the
> number of MSI-X interrupts per adapter. Consider e.g. a system with two
> adapter
On Wed, Jun 15, 2016 at 01:20:19PM +0200, SF Markus Elfring wrote:
> > +DIR=$(dirname $(readlink -f $0))
> > +DIR="${DIR}/../"
>
> How do you think about to merge these variable assignments also into one?
>
> +DIR="$(dirname $(readlink -f $0))/../"
Sure.
Luis
On 15 Jun, Zheng, Lv wrote:
> Hi, Rafael
>
> > From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of
> > Rafael J. Wysocki
> > Subject: Re: acpi: broken suspend to RAM with v4.7-rc1
> >
> > On Mon, Jun 13, 2016 at 12:07 PM, Andrey Skvortsov
> > wrote:
> > > Hi Lv,
> > >
> > > On 13
On Wed, Jun 15, 2016 at 04:06:55PM -0400, Keith Busch wrote:
> >
> > 0: A0 B0
> > 1: A1 B1
> > 2: A2 B2
> > 3: A3 B3
> > 4: A4 B4
> > 5: A5 B5
> > 6: A6 B6
> > 7: A7 B7
> > 8: (none)
> > ...
> > 31: (none)
>
> I'll need to look at the follow on patches do to confirm, but that's
> not what this sh
On 06/15/2016 03:08 PM, Waiman Long wrote:
On 06/15/2016 01:12 PM, Peter Zijlstra wrote:
On Wed, Jun 15, 2016 at 09:56:59AM -0700, Davidlohr Bueso wrote:
On Tue, 14 Jun 2016, Waiman Long wrote:
+++ b/kernel/locking/osq_lock.c
@@ -115,7 +115,7 @@ bool osq_lock(struct optimistic_spin_queue *lock
Lukasz wrote:
> From: Nadav Amit [mailto:nadav.a...@gmail.com]
> Sent: Tuesday, June 14, 2016 8:38 PM
>
>>> + pte_t pte = ptep_get_and_clear(mm, addr, ptep);
>>> +
>>> + if (boot_cpu_has_bug(X86_BUG_PTE_LEAK))
>>> + fix_pte_leak(mm, addr, ptep);
>>> + return pte;
>>> }
>>
>> I
On Wed, Jun 15, 2016 at 09:29:38PM +0200, Daniel Vetter wrote:
> On Wed, Jun 15, 2016 at 7:21 PM, Liviu Dudau wrote:
> > Could be the tda998x_drv fault, but I'm getting this splat:
>
> Yeah, tda9998x needs to be fixed to _not_ register it's connector
> before the overall (componentized) driver is
From: Ebru Akagunduz
Currently khugepaged makes swapin readahead under down_write. This patch
supplies to make swapin readahead under down_read instead of down_write.
The patch was tested with a test program that allocates 800MB of memory,
writes to it, and then sleeps. The system was forced t
As with anon THP, we only mlock file huge pages if we can prove that the
page is not mapped with PTE. This way we can avoid mlock leak into
non-mlocked vma on split.
We rely on PageDoubleMap() under lock_page() to check if the the page
may be PTE mapped. PG_double_map is set by page_add_file_rmap(
From: Ebru Akagunduz
After creating revalidate vma function, locking inconsistency occured
due to directing the code path to wrong label. This patch directs
to correct label and fix the inconsistency.
Related commit that caused inconsistency:
http://git.kernel.org/cgit/linux/kernel/git/next/linu
Let's wire up existing madvise() hugepage hints for file mappings.
MADV_HUGEPAGE advise shmem to allocate huge page on page fault in the
VMA. It only has effect if the filesystem is mounted with huge=advise or
huge=within_size.
MADV_NOHUGEPAGE prevents hugepage from being allocated on page fault
Even if user asked to allocate huge pages always (huge=always), we
should be able to free up some memory by splitting pages which are
partly byound i_size if memory presure comes or once we hit limit on
filesystem size (-o size=).
In order to do this we maintain per-superblock list of inodes, whic
File COW for THP is handled on pte level: just split the pmd.
It's not clear how benefitial would be allocation of huge pages on COW
faults. And it would require some code to make them work.
I think at some point we can consider teaching khugepaged to collapse
pages in COW mappings, but allocatin
For file mappings, we don't deposit page tables on THP allocation
because it's not strictly required to implement split_huge_pmd(): we
can just clear pmd and let following page faults to reconstruct the
page table.
But Power makes use of deposited page table to address MMU quirk.
Let's hide THP p
Hi Sinan,
On 13/06/2016 06:26, Sinan Kaya wrote:
> Open call is ignoring the return code from reset call and can
> potentially continue even though reset call failed.
>
> If reset_required module parameter is set, this patch is going
> to validate the return code and will abort open if reset fail
On Wed, Jun 15, 2016 at 10:31:36AM +0100, Mark Brown wrote:
> On Wed, Jun 15, 2016 at 10:16:27AM +0100, Srinivas Kandagatla wrote:
> > On 14/06/16 16:59, Mark Brown wrote:
> > > On Fri, Jun 10, 2016 at 07:18:45PM +0100, Srinivas Kandagatla wrote:
> > In theory there are 3 devices,
> > one is the p
On 06/15/2016 01:04 PM, Nadav Amit wrote:
> Be careful here. According to the SDM when invalidating a huge-page,
> each 4KB page needs to be invalidated separately. In practice, when
> Linux invalidates 2MB/1GB pages it performs a full TLB flush. The
> full flush may not be required on knights land
The PCI_MSI symbol is used inconsistently throughout the tree,
with some drivers using 'select' and others using 'depends on',
or using conditional selects. This keeps causing problems,
and the latest one is a result of ARCH_ALPINE using a 'select'
statement to enable its platform specific MSI driv
Add info about tmpfs/shmem with huge pages.
Signed-off-by: Kirill A. Shutemov
---
Documentation/filesystems/proc.txt | 9 +++
Documentation/vm/transhuge.txt | 128 ++---
2 files changed, 101 insertions(+), 36 deletions(-)
diff --git a/Documentation/filesyst
The new helper is similar to radix_tree_maybe_preload(), but tries to
preload number of nodes required to insert (1 << order) continuous
naturally-aligned elements.
This is required to push huge pages into pagecache.
Signed-off-by: Kirill A. Shutemov
---
include/linux/radix-tree.h | 1 +
lib/r
Both variants of khugepaged_alloc_page() do up_read(&mm->mmap_sem)
first: no point keep it inside the function.
Signed-off-by: Kirill A. Shutemov
---
mm/khugepaged.c | 25 ++---
1 file changed, 10 insertions(+), 15 deletions(-)
diff --git a/mm/khugepaged.c b/mm/khugepaged.c
vma_addjust_trans_huge() splits pmd if it's crossing VMA boundary.
During split we munlock the huge page which requires rmap walk.
rmap wants to take the lock on its own.
Let's move vma_adjust_trans_huge() outside i_mmap_rwsem to fix this.
Signed-off-by: Kirill A. Shutemov
---
mm/mmap.c | 4 ++-
We are going to need to call shmem_charge() under tree_lock to get
accoutning right on collapse of small tmpfs pages into a huge one.
The problem is that tree_lock is irq-safe and lockdep is not happy, that
we take irq-unsafe lock under irq-safe[1].
Let's convert the lock to irq-safe.
[1] https:
khugepaged implementation grew to the point when it deserve separate
file in source.
Let's move it to mm/khugepaged.c.
Signed-off-by: Kirill A. Shutemov
---
include/linux/huge_mm.h| 10 +
include/linux/khugepaged.h |5 +
mm/Makefile|2 +-
mm/huge_memory.c
Let's add ShmemHugePages and ShmemPmdMapped fields into meminfo and
smaps. It indicates how many times we allocate and map shmem THP.
NR_ANON_TRANSPARENT_HUGEPAGES is renamed to NR_ANON_THPS.
Signed-off-by: Kirill A. Shutemov
---
drivers/base/node.c| 13 +
fs/proc/meminfo.c
This patch adds new mount option "huge=". It can have following values:
- "always":
Attempt to allocate huge pages every time we need a new page;
- "never":
Do not allocate huge pages;
- "within_size":
Only allocate huge page if it will be fully within i_size.
This patch extends khugepaged to support collapse of tmpfs/shmem pages.
We share fair amount of infrastructure with anon-THP collapse.
Few design points:
- First we are looking for VMA which can be suitable for mapping huge
page;
- If the VMA maps shmem file, the rest scan/collapse opera
copy_page_range() has a check for "Don't copy ptes where a page fault
will fill them correctly." It works on VMA level. We still copy all page
table entries from private mappings, even if they map page cache.
We can simplify copy_huge_pmd() a bit by skipping file PMDs.
We don't map file private p
On 06/15/2016 12:36 PM, Yannick Brosseau wrote:
> The execveat test try to exec the Makefile file and expect an EACCES results.
> When running
> the test in the installed destination it would fail with ENOENT since the
> file is
> not there.
> Add Makefile to the TEST_FILES list so it's copied at
From: Hugh Dickins
Provide a shmem_get_unmapped_area method in file_operations, called
at mmap time to decide the mapping address. It could be conditional
on CONFIG_TRANSPARENT_HUGEPAGE, but save #ifdefs in other places by
making it unconditional.
shmem_get_unmapped_area() first calls the usual
This is preparation of vmscan for file huge pages. We cannot write out
huge pages, so we need to split them on the way out.
Signed-off-by: Kirill A. Shutemov
---
mm/vmscan.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/mm/vmscan.c b/mm/vmscan.c
index 93ba33789ac6..21d417ccff69 10064
On Wed, Jun 15, 2016 at 06:21:04PM +0100, Liviu Dudau wrote:
> Could be the tda998x_drv fault, but I'm getting this splat:
>
> [1.347687] kobject_add_internal failed for card0-HDMI-A-1 (error: -2
> parent: card0)
Right, so this is -ENOENT - I expect that it's complaining that the
parent does
For shmem/tmpfs we only need to tweak truncate_inode_page() and
invalidate_mapping_pages().
truncate_inode_pages_range() and invalidate_inode_pages2_range() are
adjusted to use page_to_pgoff().
Signed-off-by: Kirill A. Shutemov
---
mm/truncate.c | 28 +++-
1 file changed
Basic scheme is the same as for anon THP.
Main differences:
- File pages are on radix-tree, so we have head->_count offset by
HPAGE_PMD_NR. The count got distributed to small pages during split.
- mapping->tree_lock prevents non-lockless access to pages under split
over radix-tree;
change_huge_pmd() has assert which is not relvant for file page.
For shared mapping it's perfectly fine to have page table entry
writable, without explicit mkwrite.
Signed-off-by: Kirill A. Shutemov
---
mm/huge_memory.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/mm/hug
In the AMD powerplay driver, a pointer is checked for validity by
comparing against an integer '0', which causes a harmless warning
when building with "make W=1":
drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/processpptables.c:1502:16: error:
ordered comparison of pointer with integer zero [-Werr
split_huge_pmd() for file mappings (and DAX too) is implemented by just
clearing pmd entry as we can re-fill this area from page cache on pte
level later.
This means we don't need deposit page tables when file THP is mapped.
Therefore we shouldn't try to withdraw a page table on zap_huge_pmd()
fil
Splitting THP PMD is simple: just unmap it as in DAX case. This way we
can avoid memory overhead on page table allocation to deposit.
It's probably a good idea to try to allocation page table with
GFP_ATOMIC in __split_huge_pmd_locked() to avoid refaulting the area,
but clearing pmd should be good
For now, we would have HPAGE_PMD_NR entries in radix tree for every huge
page. That's suboptimal and it will be changed to use Matthew's
multi-order entries later.
'add' operation is not changed, because we don't need it to implement
hugetmpfs: shmem uses its own implementation.
Signed-off-by: Ki
Here's basic implementation of huge pages support for shmem/tmpfs.
It's all pretty streight-forward:
- shmem_getpage() allcoates huge page if it can and try to inserd into
radix tree with shmem_add_to_page_cache();
- shmem_add_to_page_cache() puts the page onto radix-tree if there's
On 10/06/16 03:35, Oleg Drokin wrote:
> These patches remove multiple assignments in Lustre, that makes
> checkpatch (somewhat understandably) unhappy.
>
> Nathaniel Clark (8):
> staging/lustre/osc: Fix Multiple Assignment Warnings
> staging/lustre/fid: Fix Multiple Assignments
> staging/lus
The idea borrowed from Peter's patch from patchset on speculative page
faults[1]:
Instead of passing around the endless list of function arguments,
replace the lot with a single structure so we can change context
without endless function signature changes.
The changes are mostly mechanical with e
These flags are in use for file THP.
Signed-off-by: Kirill A. Shutemov
---
include/linux/page-flags.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
index 8cf09639185a..74e4dda91238 100644
--- a/include/linux/page
Vlastimil noted[1] that pmd can be no longer valid after we drop
mmap_sem. We need recheck it once mmap_sem taken again.
[1] http://lkml.kernel.org/r/12918dcd-a695-c6f4-e06f-69141c5f3...@suse.cz
Signed-off-by: Kirill A. Shutemov
---
mm/huge_memory.c | 6 ++
1 file changed, 6 insertions(+)
From: Omar Sandoval
This is exposed in debugfs but there's no quick way to set it with
trace-cmd. While we're adding support for this, fix --profile so it sets
max_graph_depth back to whatever it was before.
Signed-off-by: Omar Sandoval
---
Documentation/trace-cmd-record.1.txt | 5
trace
We always have vma->vm_mm around.
Signed-off-by: Kirill A. Shutemov
---
arch/alpha/mm/fault.c | 2 +-
arch/arc/mm/fault.c | 2 +-
arch/arm/mm/fault.c | 2 +-
arch/arm64/mm/fault.c | 2 +-
arch/avr32/mm/fault.c | 2 +-
arch/cris/mm/fault.c
The newly added nilfs_msg() infrastructure caused a warning in
nilfs_clear_dirty_page() when it is disabled:
fs/nilfs2/page.c: In function 'nilfs_clear_dirty_page':
fs/nilfs2/page.c:402:22: error: unused variable 'sb' [-Werror=unused-variable]
struct super_block *sb = inode->i_sb;
We can avoid
Naive approach: on mapping/unmapping the page as compound we update
->_mapcount on each 4k page. That's not efficient, but it's not obvious
how we can optimize this. We can look into optimization later.
PG_double_map optimization doesn't work for file pages since lifecycle
of file pages is differe
THP_FILE_ALLOC: how many times huge page was allocated and put page
cache.
THP_FILE_MAPPED: how many times file huge page was mapped.
Signed-off-by: Kirill A. Shutemov
---
include/linux/vm_event_item.h | 7 +++
mm/memory.c | 1 +
mm/vmstat.c | 2 ++
3 fil
With postponed page table allocation we have chance to setup huge pages.
do_set_pte() calls do_set_pmd() if following criteria met:
- page is compound;
- pmd entry in pmd_none();
- vma has suitable size and alignment;
Signed-off-by: Kirill A. Shutemov
---
include/linux/huge_mm.h | 2 ++
mm/
The idea (and most of code) is borrowed again: from Hugh's patchset on
huge tmpfs[1].
Instead of allocation pte page table upfront, we postpone this until we
have page to map in hands. This approach opens possibility to map the
page as huge if filesystem supports this.
Comparing to Hugh's patch I
Passing 'vma' to hugepage_vma_revlidate() is useless. It doesn't make use
of it anyway.
Link: http://lkml.kernel.org/r/20160530095058.ga53...@black.fi.intel.com
Cc: Ebru Akagunduz
Cc: Hugh Dickins
Cc: Michal Hocko
Signed-off-by: Andrew Morton
---
mm/huge_memory.c | 11 +--
1 file ch
Andrew,
As requested, here's refreshed version of the patchset.
During preparation, Ebru mentionedi (on irc) on that she wanted to withdraw
mm-thp-avoid-unnecessary-swapin-in-khugepaged.patch from mm tree, but it's
difficult in current state of the tree. So I did rebase removing the patch.
The p
Add description of THP handling into unevictable-lru.txt.
Signed-off-by: Kirill A. Shutemov
---
Documentation/vm/unevictable-lru.txt | 21 +
1 file changed, 21 insertions(+)
diff --git a/Documentation/vm/unevictable-lru.txt
b/Documentation/vm/unevictable-lru.txt
index fa3b5
From: Andrew Morton
update comment to match new code
Cc: Andrea Arcangeli
Cc: Ebru Akagunduz
Cc: Kirill A. Shutemov
Cc: Rik van Riel
Cc: Sergey Senozhatsky
Cc: Stephen Rothwell
Cc: Vlastimil Babka
Signed-off-by: Andrew Morton
---
mm/huge_memory.c | 6 +++---
1 file changed, 3 insertions
While removing all interfaces in media_device_unregister(), all
media_interface pointers are freed. This is illegal and results in
double kfree() if any media_interface is still linked at this point;
maybe because a userspace process still has a file handle. Once the
process closes the file handl
media_gobj_destroy() may be called twice on one instance - once by
media_device_unregister() and again by dvb_media_device_free(). The
function media_remove_intf_links() establishes and documents the
convention that mdev==NULL means that the object is not registered,
but nobody ever NULLs this var
On Thursday 06/02 at 15:50 -0700, Calvin Owens wrote:
> On 05/13/2016 01:28 PM, Calvin Owens wrote:
> > Currently we free the resources backing the enclosure device before we
> > call device_unregister(). This is racy: during rmmod of low-level SCSI
> > drivers that hook into enclosure, we end up w
On Fri, Jun 10, 2016 at 5:14 PM, Heinrich Schuchardt wrote:
> avc_cache_threshold is of type unsigned int.
>
> Do not use a signed new_value in
> sscanf(page, "%u", &new_value).
>
> Signed-off-by: Heinrich Schuchardt
> ---
> security/selinux/selinuxfs.c | 2 +-
> 1 file changed, 1 insertion(+),
On Wed, Jun 15, 2016 at 08:01:09PM +, Mathieu Desnoyers wrote:
> - On Jun 15, 2016, at 3:38 PM, Josh Poimboeuf jpoim...@redhat.com wrote:
>
> > On Wed, Jun 15, 2016 at 07:13:39PM +, Mathieu Desnoyers wrote:
> >> - On Jun 15, 2016, at 2:18 PM, Josh Poimboeuf jpoim...@redhat.com
> >
On Wed, Jun 15 2016, Prarit Bhargava wrote:
> At some point I was 100% sure this worked. I do remember testing it against
> just a loadable module and had positive testing results.
I think the current %ps/%pf behaviour was introduced in 4796dd200db9
(way back in 2012).
> In any case this is a
The _etext position is defined to be the end of the kernel text code,
and should not include any part of the data segments. This interferes
with things that might check memory ranges and expect executable code
up to _etext. Just to be conservative, leave the kernel resource as
it was, using __init_
Don't free the object until the file handle has been closed. Fixes
use-after-free bug which occurs when I disconnect my DVB-S received
while VDR is running.
Signed-off-by: Max Kellermann
---
drivers/media/dvb-core/dvb_ca_en50221.c | 24 +++-
1 file changed, 23 insertions(+
On 11/06/16 21:08, Rithvik Patibandla wrote:
> Fix "Block comments use * on subsequent lines" and "Block comments use
> */ on trailing lines" warnings thrown by checkpatch.pl
>
> Signed-off-by: Rithvik Patibandla
> ---
> drivers/staging/vt6656/card.c | 3 ++-
> 1 file changed, 2 insertions(+), 1
On Wed, Jun 15, 2016 at 07:02:38PM +0200, Thomas Gleixner wrote:
> On Wed, 15 Jun 2016, Paul E. McKenney wrote:
> > On Mon, Jun 13, 2016 at 09:15:14AM -0700, Paul E. McKenney wrote:
> > > On Mon, Jun 13, 2016 at 08:40:50AM -, Thomas Gleixner wrote:
> > > > The current timer wheel has some drawb
On Wed, 2016-06-15 at 13:54 +0200, j...@8bytes.org wrote:
> On Thu, Jun 09, 2016 at 03:48:44PM +, Vesely, Jan wrote:
> > On Sat, 2016-05-21 at 14:11 -0400, Jan Vesely wrote:
> > > From: Jan Vesely
> > >
> > > Signed-off-by: Jan Vesely
> > > ---
> > > drivers/iommu/amd_iommu.c | 1 +
> > > 1
On Wed, Jun 15, 2016 at 03:24:52PM -0500, Josh Poimboeuf wrote:
> Thanks, figured it out. It was an objtool bug. It was expecting the
> macro to create a section symbol (STT_SECTION), but for some reason this
> file's use of the macro creates a function symbol (STT_FUNC).
Actually, to be precise
A strange behaviour is observed when comparing PCI hotplug in QEMU, between
x86 and pseries. If you consider the following steps:
- start a VM
- add a PCI device via the QEMU monitor before the rtasd has started (for
example starting the VM in paused state, or hotplug during FW or boot
loader)
Dave Hansen wrote:
> On 06/15/2016 01:04 PM, Nadav Amit wrote:
>> Be careful here. According to the SDM when invalidating a huge-page,
>> each 4KB page needs to be invalidated separately. In practice, when
>> Linux invalidates 2MB/1GB pages it performs a full TLB flush. The
>> full flush may not
On Wed, Jun 15, 2016 at 09:11:45PM +0200, Michal Marek wrote:
> Dne 15.6.2016 v 18:02 Luis R. Rodriguez napsal(a):
> > On Wed, Jun 15, 2016 at 09:50:11AM +0200, Michal Marek wrote:
> >> On 2016-06-15 00:10, Luis R. Rodriguez wrote:
> >>> +weight = (int(rel_specs['VERSION'])<< 32) + \
>
On 11/06/16 22:10, Sudip Mukherjee wrote:
> return is not a function so no need to use the parenthesis.
>
> Signed-off-by: Sudip Mukherjee
> ---
> drivers/staging/i4l/icn/icn.c | 16
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
All the patches in this series look like g
When building a kernel with W=1, the nl80211.c file causes a number of
warnings, all about the same problem:
net/wireless/nl80211.c: In function 'nl80211_parse_mesh_config':
net/wireless/nl80211.c:5287:103: error: comparison is always false due to
limited range of data type [-Werror=type-limits]
When building with -Wextra, we get a harmless warning from the
EFX_EXTRACT_OWORD32 macro:
ethernet/sfc/farch.c: In function 'efx_farch_test_registers':
ethernet/sfc/farch.c:119:30: error: comparison of unsigned expression < 0 is
always false [-Werror=type-limits]
ethernet/sfc/farch.c:124:144: err
On Wed, 15 Jun 2016, Luis R. Rodriguez wrote:
> On Wed, Jun 15, 2016 at 09:11:45PM +0200, Michal Marek wrote:
> > Dne 15.6.2016 v 18:02 Luis R. Rodriguez napsal(a):
> > > On Wed, Jun 15, 2016 at 09:50:11AM +0200, Michal Marek wrote:
> > >> On 2016-06-15 00:10, Luis R. Rodriguez wrote:
> > >>> +
On Wed, Jun 15, 2016 at 10:05 PM, Russell King - ARM Linux
wrote:
> On Wed, Jun 15, 2016 at 09:29:38PM +0200, Daniel Vetter wrote:
>> On Wed, Jun 15, 2016 at 7:21 PM, Liviu Dudau wrote:
>> > Could be the tda998x_drv fault, but I'm getting this splat:
>>
>> Yeah, tda9998x needs to be fixed to _not
On 06/15/2016 02:15 PM, Max Kellermann wrote:
> While removing all interfaces in media_device_unregister(), all
> media_interface pointers are freed. This is illegal and results in
> double kfree() if any media_interface is still linked at this point;
> maybe because a userspace process still has
On Wed, 15 Jun 2016 11:55:44 -0700
Kees Cook wrote:
> The limit on the length of lines is 80 columns and this is a strongly
> preferred limit.
I think the code looks worse when it is truncated to 80 columns but
I'll do it and resend the patches.
--
Emese
On 06/15/16 12:12, Rob Herring wrote:
> On Wed, Jun 15, 2016 at 1:13 PM, Frank Rowand wrote:
>> From: Frank Rowand
>>
>> Fix a memory leak resulting from memory allocation in safe_name().
>> This patch fixes all call sites of safe_name().
>>
>> Mathieu Malaterre reported the memory leak on boot:
Compiling the rtlwifi drivers for ARM with gcc -Wextra warns about lots of
incorrect code that results from 'char' being unsigned here, e.g.
staging/rtl8192e/rtl8192e/r8192E_phy.c:1072:36: error: comparison is always
false due to limited range of data type [-Werror=type-limits]
staging/rtl8192e/r
Asynchronous wb switching of inodes takes an additional ref count on an
inode to make sure inode remains valid until switchover is completed.
However, anyone calling ihold() must already have a ref count on inode,
but in this case inode->i_count may already be zero:
[ cut here ]--
On 2016/06/15 22:32, Shuah Khan wrote:
> This change introduces memory leaks, since drivers are relying on
> media_device_unregister() to free interfaces.
This is what I thought, too, until I checked the code paths. Who adds
entries to that list? Only media_gobj_create() does, and only when
typ
Linus,
The following changes since commit db06d759d6cf903aeda8c107fd3abd366dd80200:
Merge branch 'for-4.7-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu (2016-06-13 19:54:46
-1000)
are available in the git repository at:
git://git.infradead.org/linux-ubifs.git tags/upst
When building with -Wextra, we get a lot of warnings for the lpfc driver
concerning expressions that are always true, starting with:
drivers/scsi/lpfc/lpfc_attr.c: In function 'lpfc_enable_npiv_init':
drivers/scsi/lpfc/lpfc_attr.c:2786:77: error: comparison of unsigned expression
>= 0 is always t
From: Frank Rowand
Fix a memory leak resulting from memory allocation in safe_name().
This patch fixes all call sites of safe_name().
Mathieu Malaterre reported the memory leak on boot:
On my PowerMac device-tree would generate a duplicate name:
[0.023043] device-tree: Duplicate name in Po
- On Jun 15, 2016, at 4:28 PM, Josh Poimboeuf jpoim...@redhat.com wrote:
> On Wed, Jun 15, 2016 at 03:24:52PM -0500, Josh Poimboeuf wrote:
>> Thanks, figured it out. It was an objtool bug. It was expecting the
>> macro to create a section symbol (STT_SECTION), but for some reason this
>> fil
On Wed, 15 Jun 2016 11:07:08 -0700
Kees Cook wrote:
> On Tue, Jun 14, 2016 at 3:20 PM, Emese Revfy wrote:
> This doesn't look right to me: these are CFLAGS_REMOVE_* entries, and
> I think you want to _add_ the DISABLE_LATENT_ENTROPY_PLUGIN to the
> CFLAGS here.
Thanks for the report. I think
701 - 800 of 1105 matches
Mail list logo
