On Wed, 31 May 2017 14:51:50 +0200
Alexander Potapenko wrote:
> + /* alias comes from the userspace and may not be zero-terminated.
> + */
> + memcpy(dev->ifalias, alias, len);
You don't need a multi-line comment here.
On Tue, May 30, 2017 at 11:15:41PM +0200, Thomas Gleixner wrote:
> None of these declarations is required outside of kernel/time. Move them to
> an internal header.
It seems like struct k_clock itself could be marked private as well.
And with a small exported helper for /the /proc/timers implemen
On Tue, May 30, 2017 at 11:15:46PM +0200, Thomas Gleixner wrote:
> That function is a misnomer. Rename it with a proper prefix to
> posixtimer_rearm().
Please also move it out of asm-generic/siginfo.h as it's implemented
and used in generic code only, and there is no arch override at all.
In fact
Hi Laurent!
On Wed, 24 May 2017, Laurent Dufour wrote:
When mmap_sem will be moved to a range lock, some assertion done in
the code will have to be reviewed to work with the range locking as
well.
This patch disables these assertions for the moment but it has be
reviewed later once the range l
On Mon, May 15, 2017 at 10:46:35AM +0100, Matt Redfearn wrote:
> + select HAVE_SYSCALL_TRACEPOINTS
> + select HAVE_SYSCALL_TRACEPOINTS
Maybe we could remove duplicates while we're at it?
Cheers
James
signature.asc
Description: Digital signature
Hi Tahsin,
[auto build test ERROR on ext4/dev]
[also build test ERROR on next-20170531]
[cannot apply to v4.12-rc3]
[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/Tahsin-Erdogan/ext4-xattr-in
On Wed, May 31, 2017 at 04:32:17PM +0200, Michal Hocko wrote:
> I would assume such a patch would be backported to stable trees because
> to me it sounds like the current semantic is simply broken and needs
> fixing anyway but it shouldn't be much different from any other bugs.
So the program woul
From: Chris Wilson
An error during suspend (e100e_pm_suspend),
[ 429.994338] ACPI : EC: event blocked
[ 429.994633] e1000e: EEE TX LPI TIMER: 0011
[ 430.955451] pci_pm_suspend(): e1000e_pm_suspend+0x0/0x30 [e1000e] returns -2
[ 430.955454] dpm_run_callback(): pci_pm_suspend+0x0/0x140 ret
On Wed, 31 May 2017, David Miller wrote:
> And we can't understand why respinning with the requested change is
> less work than making several postings such as this one.
When our CI hits tons of non-drm issues every merge window, I imagine
our developers can start to get a little frustrated tryin
Hallo,
Mein Name ist Joanna Diane Christopher. Ich bin die einzige Tochter von spät
Dr. Fredrick Christopher. Mein Vater war ein vorzüglicher Öl- und
Gasunternehmer, bevor er starb. Er hatte auch umfangreiche Investitionen in
Immobilien, Agrar- und Bankensektoren. Meine Mutter starb mit meinen
On Wed, May 31, 2017 at 11:03:52PM +0800, Xunlei Pang wrote:
> For kdump case, it will be put in some reserved crash memory allocated
> by kexec-tools, and passed the corresponding start address of the
> allocated reserved crash memory to kdump kernel via "elfcorehdr=",
> please see kernel function
On Wed, 31 May 2017, Chen, Yu C wrote:
> May I know if it is possible to get the following commit merged into the
>
> stable tree 4.10.17:
>
> commit 90b4f30b6d15222a509dacf47f29efef2b22571e
>
> Author: Thomas Gleixner mailto:t...@linutronix.de>>
>
> Date: Wed May 10 16:30:12 2017 +0200
>
>
> > Possibly more useful would be a variant of (IIRC) dma_map_for_device()
> > that will allocate a suitable bounce buffer for non-dma memory.
> > I think it can already do so for memory that is outside the address
> > range that the device can address (eg for a 32bit PCIe master in 64bit
> > syst
Hi Tahsin,
[auto build test ERROR on ext4/dev]
[also build test ERROR on next-20170531]
[cannot apply to v4.12-rc3]
[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/Tahsin-Erdogan/ext4-xattr-in
From: Michal Hocko
bucket_table_alloc can be currently called with GFP_KERNEL or
GFP_ATOMIC. For the former we basically have an open coded kvzalloc
while the later only uses kzalloc. Let's simplify the code a bit by
the dropping the open coded path and replace it with kvzalloc
Cc: Thomas Graf
From: Michal Hocko
xt_alloc_table_info basically opencodes kvmalloc so use the library
function instead.
Cc: Pablo Neira Ayuso
Cc: Jozsef Kadlecsik
Cc: Florian Westphal
Cc: netfilter-de...@vger.kernel.org
Signed-off-by: Michal Hocko
---
net/netfilter/x_tables.c | 12
1 file cha
From: Michal Hocko
There is no real reason to duplicate kvmalloc* helpers so drop
alloc_fdmem and replace it with the appropriate library function.
Cc: Alexander Viro
Signed-off-by: Michal Hocko
---
fs/file.c | 22 --
1 file changed, 4 insertions(+), 18 deletions(-)
diff
Hi,
while doing something unrelated I've noticed these few open coded
kvmalloc variants so let's replace them with the library function. Each
patch can be merged separately so I hope I've CCed proper people. This
is based on the current linux-next.
Shortlog
Michal Hocko (3):
fs/file: replace
Hi,
On Tue, May 30, 2017 at 5:10 PM, David Rientjes wrote:
> On Wed, 24 May 2017, Doug Anderson wrote:
>
>> * Matthias has been sending out individual patches that take each
>> particular case into account to try to remove the warnings. In some
>> cases this removes totally dead code. In other
Due to errata it is possible for the TSC_DEADLINE timer to misbehave
after using TSC_ADJUST. A microcode update is available to fix this
situation.
Avoid using the TSC_DEADLINE timer if it is affected by this issue and
report the required microcode version.
Signed-off-by: Peter Zijlstra (Intel)
On Wed, May 31, 2017 at 04:55:36PM +0200, Oleksij Rempel wrote:
> On Wed, May 31, 2017 at 03:44:38PM +0100, Mark Brown wrote:
> > I'm missing both the cover letter and the rest of the series, what's
> > going on with dependencies here?
> Hmm... I probably needed to add same list of maintainers to
So that we can more easily see in what mode the lapic timer operates.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/kernel/apic/apic.c |1 +
1 file changed, 1 insertion(+)
--- a/arch/x86/kernel/apic/apic.c
+++ b/arch/x86/kernel/apic/apic.c
@@ -563,6 +563,7 @@ static void setup_APIC_tim
Hi all,
These patches rely on the latest microcode data files from Intel [*]
Without this microcode loaded, we'll print a FW_BUG informing the user to
update their microcode image and disable TSC_DEADLINE support.
This in turn allows us to remove the TSC_ADJUST workarounds which were required
du
Now that all affected platforms have a microcode update; and we check
this and disable TSC_DEADLINE and print a microcode revision update
error if its too old, we can remove the TSC_ADJUST clamp.
This should help with systems where the second socket runs ahead of
the first socket and needs a negat
Hi Eric,
> On 23 May 2017, at 21:00, Eric Biggers wrote:
>
> Hi David,
>
> On Tue, May 23, 2017 at 07:11:20AM +0200, David Gstir wrote:
>> From: Daniel Walter
>>
>> fscrypt provides facilities to use different encryption algorithms which
>> are selectable by userspace when setting the encrypt
Am 31.05.2017 um 17:27 schrieb Stephen Warren:
> On 05/30/2017 06:23 AM, Phil Elwell wrote:
>> Hi,
>>
>> I've run into a problem using the fixed-factor clock on Raspberry Pi
>> and I'd
>> like some advice before I submit a patch.
>>
>> Some context: the aim is to use a standard UART and some extern
On Wed, 24 May 2017, Laurent Dufour wrote:
The range locking framework doesn't yet provide nest locking
operation.
Once the range locking API while provide nested operation support,
this patch will have to be reviewed.
Please note that we already have range_write_lock_nest_lock().
Thanks,
Da
On Wed, May 31, 2017 at 01:15:16AM -0700, Tahsin Erdogan wrote:
> Ext4 now supports xattr values that are up to 64k in size (vfs limit).
> Large xattr values are stored in external inodes each one holding a
> single value. Once written the data blocks of these inodes are immutable.
>
> The real wo
On 15 May 2017 at 17:35, Georgi Djakov wrote:
> This patch introduce a new API to get the requirement and configure the
> interconnect buses across the entire chipset to fit with the current demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the interconnect co
Hi Tom,
I have stumbled over the following construct in xgbe_map_rx_buffer
order = max_t(int, PAGE_ALLOC_COSTLY_ORDER - 1, 0);
which looks quite suspicious. Why does it PAGE_ALLOC_COSTLY_ORDER - 1?
And why do you depend on PAGE_ALLOC_COSTLY_ORDER at all?
Thanks!
--
Michal Hocko
SUSE Labs
On Wed, May 31, 2017 at 01:14:58AM -0700, Tahsin Erdogan wrote:
> EXT4_XATTR_MAX_LARGE_EA_SIZE definition in ext4 is currently unused.
> Besides, vfs enforces its own 64k limit which makes the 1MB limit in
> ext4 redundant. Remove it.
>
> Signed-off-by: Tahsin Erdogan
> ---
> fs/ext4/ext4.h | 6
On Mon, May 29, 2017 at 05:03:01PM -0400, Nicolas Pitre wrote:
> On most small systems where user space is tightly controlled, the realtime
> scheduling class can often be dispensed with to reduce the kernel footprint.
> Let's make it configurable.
>
> Signed-off-by: Nicolas Pitre
> ---
> stati
Most users of irq_alloc_generic_chip() call irq_setup_generic_chip()
too. To simplify the cleanup provide a function that both removes a
generic chip and frees its memory.
Signed-off-by: Bartosz Golaszewski
---
include/linux/irq.h | 8
1 file changed, 8 insertions(+)
diff --git a/inclu
Provide a resource managed variant of irq_setup_generic_chip().
Signed-off-by: Bartosz Golaszewski
---
Documentation/driver-model/devres.txt | 1 +
include/linux/irq.h | 3 ++
kernel/irq/devres.c | 52 +++
3 files changed, 56
This series is a follow-up to [1].
Some users of irq_alloc_generic_chip() are modules which can be
removed (e.g. gpio-ml-ioh) but have no means of freeing the allocated
generic chip.
Last time it was suggested to provide irq_destroy_generic_chip() which
would undo both irq_remove_generic_chip() a
Provide a resource managed variant of irq_alloc_generic_chip().
Signed-off-by: Bartosz Golaszewski
---
Documentation/driver-model/devres.txt | 1 +
include/linux/irq.h | 5 +
kernel/irq/devres.c | 34 ++
3 files changed, 4
This function will be used in the devres variant of
irq_alloc_generic_chip().
Signed-off-by: Bartosz Golaszewski
---
kernel/irq/generic-chip.c | 7 +++
kernel/irq/internals.h| 11 +++
2 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/kernel/irq/generic-chip.c b/ker
Currently there's no way for users of irq_alloc_generic_chip() to free
the allocated memory other than calling kfree() manually on the
returned pointer. This may lead to errors if the internals of
irq_alloc_generic_chip() ever change. Provide a routine to free the
generic chip.
Signed-off-by: Bart
On Wed, May 31, 2017 at 7:03 AM, Peter Zijlstra wrote:
> On Wed, May 31, 2017 at 06:17:16AM -0700, Kees Cook wrote:
>> On Wed, May 31, 2017 at 4:13 AM, Peter Zijlstra wrote:
>> > On Tue, May 30, 2017 at 02:39:51PM -0700, Kees Cook wrote:
>> >> The coming x86 refcount protection needs to be able t
On Tue, May 30, 2017 at 02:58:06PM +0300, Sagi Grimberg wrote:
> > So, the reason the state is changed when the work is running rather than
> > queueing is for the window when the state may be set to NVME_CTRL_DELETING,
> > and we don't want the reset work to proceed in that case.
> >
> > What do
On Wed, 2017-05-31 at 11:46 +0200, Andrey Konovalov wrote:
> Hi,
>
> I've got the following error report while fuzzing the kernel with syzkaller.
>
> On commit 5ed02dbb497422bf225783f46e6eadd237d23d6b (4.12-rc3).
>
> Unfortunately it's not reproducible.
>
> =
Hi Jon,
> > From: Khuong Dinh
> >
> > This patch makes pci-xgene-msi driver ACPI-aware and provides
> > MSI capability for X-Gene v1 PCIe controllers in ACPI boot mode.
> >
> > Signed-off-by: Khuong Dinh
> > Signed-off-by: Duc Dang
> > Acked-by: Marc Zyngier
> > ---
> > v2:
> > - Verify with
Hi Darrick,
>> -#define EXT4_XATTR_MAX_LARGE_EA_SIZE(1024 * 1024)
>
> Uhhh... didn't you add this in patch 1/28? There's little point in
> adding a symbol just to delete it shortly thereafter.
>
1/28 is the original patch I've received from Andreas. I wanted to
leave his patch in its original
On Wed, May 31, 2017 at 01:14:56AM -0700, Tahsin Erdogan wrote:
> ea_inode contents are treated as metadata, that's why it is journaled
> during initial writes. Failing to call revoke during freeing could cause
> user data to be overwritten with original ea_inode contents during journal
> replay.
>
On Wed, May 31, 2017 at 4:12 AM, Bjorn Helgaas wrote:
> On Mon, May 22, 2017 at 11:39 AM, Oza Pawandeep wrote:
>> This patch adds support for inbound memory window
>> for PCI RC drivers.
>>
>> It defines new function pci_create_root_bus2 which
>> takes inbound resources as an argument and fills i
Hi all,
this series, which is a combined effort from Amir, Andy and me introduces
new uuid_t and guid_t type names that are less confusing than the existing
types, adds new helpers for them and starts switching the fs code over to
it. Andy has additional patches on top to convert many of the user
From: Amir Goldstein
uuid_t definition is about to change.
Signed-off-by: Amir Goldstein
Signed-off-by: Christoph Hellwig
Reviewed-by: Brian Foster
Reviewed-by: Andy Shevchenko
Reviewed-by: Darrick J. Wong
---
fs/xfs/xfs_inode_item.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletio
This essentially is a partial revert of commit ff548773
("afs: Move UUID struct to linux/uuid.h") and moves struct uuid_v1 back into
fs/afs as struct afs_uuid. It however keeps it as big endian structure
so that we can use the normal uuid generation helpers when casting to/from
struct afs_uuid.
T
Signed-off-by: Christoph Hellwig
---
fs/nfsd/export.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/nfsd/export.c b/fs/nfsd/export.c
index e71f11b1a180..3bc08c394a3f 100644
--- a/fs/nfsd/export.c
+++ b/fs/nfsd/export.c
@@ -486,7 +486,7 @@ secinfo_parse(char **mesg, ch
Our "little endian" UUID really is a Wintel GUID, so rename it and its
helpers such (guid_t). The big endian UUID is the only true one, so
give it the name uuid_t. The uuid_le and uuid_be names are retained for
now, but will hopefully go away soon. The exception to that are the _cmp
helpers that
These helper are used to compare and copy two uuid_t type objects.
Signed-off-by: Amir Goldstein
[hch: also provide the respective guid_ versions]
Signed-off-by: Christoph Hellwig
Reviewed-by: Andy Shevchenko
---
fs/xfs/uuid.c| 6 --
fs/xfs/uuid.h| 7 ---
include/linu
From: Amir Goldstein
The md private helper uuid_equal() collides with a generic helper
of the same name.
Rename the md private helper to md_uuid_equal() and do the same for
md_sb_equal().
Signed-off-by: Amir Goldstein
Signed-off-by: Christoph Hellwig
Reviewed-by: Shaohua Li
Reviewed-by: Andy
Hoist the libnvdimm helper as an inline helper to linux/uuid.h
using an auxiliary const variable uuid_null in lib/uuid.c.
[hch: also add the guid variant. Both do the same but I'd like
to keep casts to a minimum]
The common helper uses the new abstract type uuid_t * instead of
u8 *.
Suggested-b
Use the generic Linux definition to implement our UUID type, this will
allow using more generic infrastructure in the future.
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Reviewed-by: Brian Foster
Reviewed-by: Andy Shevchenko
Reviewed-by: Darrick J. Wong
---
fs/xfs/uuid.h
On Wed, 24 May 2017, Laurent Dufour wrote:
A new configuration variable is introduced to activate the use of
range lock instead of semaphore to protect per process memory layout.
This range lock is replacing the use of a semaphore for mmap_sem.
Currently only available for X86_64 and PPC64 arc
This helper was only used by IMA of all things, which would get spurious
errors if CONFIG_BLOCK is disabled. Just opencode the call there.
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Acked-by: Mimi Zohar
Reviewed-by: Andy Shevchenko
---
include/linux/genhd.h |
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Reviewed-by: Andy Shevchenko
---
fs/overlayfs/copy_up.c | 2 +-
fs/overlayfs/overlayfs.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/overlayfs/copy_up.c b/fs/overlayfs/copy_up.c
index 5b795873f7fa..2a67
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Reviewed-by: Andy Shevchenko
---
drivers/nvme/host/fabrics.c | 8
drivers/nvme/host/fabrics.h | 2 +-
drivers/nvme/host/fc.c | 3 +--
drivers/nvme/target/nvmet.h | 1 +
include/linux/nvme-fc.h | 3 +--
include/linux/
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Reviewed-by: Andy Shevchenko
---
kernel/sysctl_binary.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sysctl_binary.c b/kernel/sysctl_binary.c
index ece4b177052b..939a158eab11 100644
--- a/kernel/sysct
And the uuid helpers.
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Reviewed-by: Andy Shevchenko
---
block/partitions/ldm.c | 10 +-
block/partitions/ldm.h | 6 ++
2 files changed, 7 insertions(+), 9 deletions(-)
diff --git a/block/partitions/ldm.c b/block/partitio
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Reviewed-by: Andy Shevchenko
---
drivers/scsi/scsi_debug.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
index 17249c3650fe..35ee09644cfb 100644
--
I'll keep maintaining whatever little changed we need here, with Andy as
my designated reviewer.
Signed-off-by: Christoph Hellwig
---
MAINTAINERS | 11 +++
1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 053c3bdd1fe5..660c14729205 100644
--- a/MAINTAINERS
+
From: Amir Goldstein
This is used by overlayfs to encode intrasystem unique file handles.
Suggested-by: Miklos Szeredi
Cc: Hugh Dickins
Cc: Andrew Morton
Signed-off-by: Amir Goldstein
Signed-off-by: Christoph Hellwig
---
mm/shmem.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/s
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Acked-by: Mimi Zohar
Reviewed-by: Andy Shevchenko
---
security/integrity/ima/ima_policy.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/security/integrity/ima/ima_policy.c
b/security/integrity/ima/i
For some file systems we still memcpy into it, but in various places this
already allows us to use the proper uuid helpers. More to come..
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Acked-by: Mimi Zohar (Changes to IMA/EVM)
Reviewed-by: Andy Shevchenko
---
drivers/xen/tmem.
From: Amir Goldstein
Use the common helper uuid_is_null() and remove the xfs specific
helper uuid_is_nil().
The common helper does not check for the NULL pointer value as
xfs helper did, but xfs code never calls the helper with a pointer
that can be NULL.
Conform comments and warning strings to
Opencode uuid_getnodeuniq in the only caller, and directly decode
the uuid_t representation instead of using a structure cast for it.
Signed-off-by: Christoph Hellwig
---
fs/xfs/uuid.c | 25 -
fs/xfs/uuid.h | 1 -
fs/xfs/xfs_mount.c | 5 -
3 files changed,
And switch to use uuid_t instead of the old uuid_be type.
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Reviewed-by: Andy Shevchenko
---
arch/s390/include/asm/sysinfo.h | 4 ++--
arch/s390/kernel/sysinfo.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
On Wed, May 31, 2017 at 5:08 PM, David Miller wrote:
> From: Daniel Vetter
> Date: Wed, 31 May 2017 08:10:45 +0200
>
>> On Wed, May 31, 2017 at 7:54 AM, Daniel Vetter
>> wrote:
>>> On Wed, May 31, 2017 at 1:06 AM, Dave Airlie wrote:
On 31 May 2017 at 08:10, David Miller wrote:
> From
This matches the userspace version of it, and describes the functionality
much better. Also do the same for the guid version.
Signed-off-by: Christoph Hellwig
---
include/linux/uuid.h | 8
lib/test_uuid.c | 8
lib/uuid.c | 14 +++---
3 files changed, 1
These are only used in uuid.c and vsprintf.c and aren't something modules
should use directly.
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Reviewed-by: Andy Shevchenko
---
lib/uuid.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/lib/uuid.c b/lib/uuid.c
index 90bee73f7bd
[I am sorry I didn't get to reply earlier]
On Thu 25-05-17 13:08:05, Johannes Weiner wrote:
> On Thu, May 25, 2017 at 05:38:19PM +0200, Michal Hocko wrote:
> > On Tue 23-05-17 09:25:44, Johannes Weiner wrote:
[...]
> > > We don't need any elaborate
> > > just-in-time evaluation of what each entity
We don't use uuid_be and the UUID_BE constants in any uapi headers, so make
them private to the kernel.
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
Reviewed-by: Andy Shevchenko
---
include/linux/uuid.h | 15 +++
include/uapi/linux/uuid.h | 16
On Wed, 31 May 2017, Rob Herring wrote:
> On Mon, May 29, 2017 at 05:03:01PM -0400, Nicolas Pitre wrote:
> > On most small systems where user space is tightly controlled, the realtime
> > scheduling class can often be dispensed with to reduce the kernel footprint.
> > Let's make it configurable.
>
On 05/26, Bjorn Andersson wrote:
> In order to aid post-mortem debugging the Qualcomm platforms provides a
> "memory download mode", where the boot loader will provide an interface
> for custom tools to "download" the content of RAM to a host machine.
>
> The mode is triggered by writing a magic v
On 05/26, Bjorn Andersson wrote:
> The secure IO service provides operations for reading and writing secure
> memory from non-secure mode, expose this API through SCM.
>
> Signed-off-by: Bjorn Andersson
> ---
>
> Changes since v1:
> - Correct scm-call return value handling
> - Make scm_io_readl(
On Mon, May 22, 2017 at 01:37:37PM -0500, Dave Gerlach wrote:
> Commit 7cc119f29b19 ("dt-bindings: Add TI SCI PM Domains") introduced a
> number of K2G_DEV_x macros to represent each device ID available on the
> K2G platform for use by the genpd, clock, and reset drivers. Rather than
> use these ma
On 31/05/2017 16:58, Stefan Wahren wrote:
> Am 31.05.2017 um 17:27 schrieb Stephen Warren:
>> On 05/30/2017 06:23 AM, Phil Elwell wrote:
>>> Hi,
>>>
>>> I've run into a problem using the fixed-factor clock on Raspberry Pi
>>> and I'd
>>> like some advice before I submit a patch.
>>>
>>> Some contex
On 05/31/2017 08:50 AM, Joonsoo Kim wrote:
>>> But the main win as I see it is that that's basically complete support
>>> for 32-bit arches. People do ask about arm32 support:
>>> https://groups.google.com/d/msg/kasan-dev/Sk6BsSPMRRc/Gqh4oD_wAAAJ
>>> https://groups.google.com/d/msg/kasan-dev/B22vOF
On 05/26, Bjorn Andersson wrote:
> diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi
> b/arch/arm64/boot/dts/qcom/msm8916.dtsi
> index ab3093995ded..33013835639d 100644
> --- a/arch/arm64/boot/dts/qcom/msm8916.dtsi
> +++ b/arch/arm64/boot/dts/qcom/msm8916.dtsi
> @@ -241,6 +241,8 @@
>
On Wed, May 31, 2017 at 03:34:57PM +0200, Arnd Bergmann wrote:
> On Wed, May 31, 2017 at 3:12 PM, Paul E. McKenney
> wrote:
> > On Wed, May 31, 2017 at 12:21:10PM +0200, Arnd Bergmann wrote:
> >> On Wed, May 31, 2017 at 11:43 AM, Arend van Spriel
> >> wrote:
> >> > On 5/30/2017 1:20 PM, Arnd Berg
On Tue 30-05-17 13:16:50, Pasha Tatashin wrote:
> >Could you be more specific? E.g. how are other stores done in
> >__init_single_page safe then? I am sorry to be dense here but how does
> >the full 64B store differ from other stores done in the same function.
>
> Hi Michal,
>
> It is safe to do
From: Andy Shevchenko
Date: Tue, 30 May 2017 21:48:05 +0300
> On Tue, May 30, 2017 at 10:33 AM, Jan Kiszka wrote:
>> Some cleanups of the way we probe DMI platforms in the driver. Reduces
>> a bit of open-coding and makes the logic easier reusable for any
>> potential DMI platform != Quark.
>>
>
Hi,
A system running v4.12-rc3-11-gf511c0b on s390 hangs after boot with no
messages on the console. The message buffer obtained via a system dump
looked like this:
[...]
[ 17.870712] virbr0: port 1(virbr0-nic) entered disabled state
[ 19.618523] Unable to handle kernel pointer dereference in
On 2017-05-30 20:33, Andy Shevchenko wrote:
> On Tue, May 30, 2017 at 10:01 AM, Jan Kiszka wrote:
>> Commtech adapters need the MPIOs for internal purposes, and the
>> gpio-exar driver already refused to pick them up. But there is actually
>> no point in even creating the underlying platform devic
From: Vivien Didelot
Date: Fri, 26 May 2017 18:03:04 -0400
> This patchset isolates more PPU code into phy.c and makes distinction
> between PHY Registers read and write implementations vs. generic PHY
> routines.
Series applied, thanks.
From: Vivien Didelot
Date: Fri, 26 May 2017 18:12:51 -0400
> The current dsa_register_switch function takes a useless struct device
> pointer argument, which always equals ds->dev.
>
> Drivers either call it with ds->dev, or with the same device pointer
> passed to dsa_switch_alloc, which ends u
On 2017-05-30 23:41, Rafael J. Wysocki wrote:
> On Tue, May 30, 2017 at 11:16 PM, Moore, Robert
> wrote:
>>
>>
>>> -Original Message-
>>> From: Jan Kiszka [mailto:jan.kis...@siemens.com]
>>> Sent: Monday, May 29, 2017 5:53 AM
>>> To: Mika Westerberg
>>> Cc: Rafael J. Wysocki ; Len Brown
On Tue 30-05-17 19:52:31, Roman Gushchin wrote:
> >From c57e3674efc609f8364f5e228a2c1309cfe99901 Mon Sep 17 00:00:00 2001
> From: Roman Gushchin
> Date: Tue, 23 May 2017 17:37:55 +0100
> Subject: [PATCH v2] mm,oom: add tracepoints for oom reaper-related events
>
> During the debugging of the prob
On 22/05/2017 17:02, Sudeep Holla wrote:
>
>
> On 22/05/17 15:48, Daniel Lezcano wrote:
>> On 22/05/2017 15:02, Sudeep Holla wrote:
>>
>> [ ... ]
>>
+ drv->cpumask = &cpu_topology[cpu].core_sibling;
+
>>>
>>> This is not always true and not architecturally g
On Wed, May 31, 2017 at 01:14:50AM -0700, Tahsin Erdogan wrote:
> From: Andreas Dilger
>
> Large xattr support is implemented for EXT4_FEATURE_INCOMPAT_EA_INODE.
>
> If the size of an xattr value is larger than will fit in a single
> external block, then the xattr value will be saved into the bo
On Tue, May 23, 2017 at 11:48:08AM +0200, Quentin Schulz wrote:
> Some PHY require to wait for a bit after the reset GPIO has been
> toggled. This adds support for the DT property `phy-reset-post-delay`
> which gives the delay in milliseconds to wait after reset.
>
> If the DT property is not give
Hi,
Looks like current Linux next won't boot on most ARMs
and git bisect points to commit b6bc6724488a ("mm: vmstat:
move slab statistics from zone to node counters").
Mark Brown noticed that the so far the only booting
ARMs are all with CONFIG_SMP disabled and I just
confirmed that's the case.
On Wed, May 31, 2017 at 2:42 AM, Andrey Konovalov wrote:
> Hi,
>
> I've got the following error report while fuzzing the kernel with syzkaller.
>
> On commit 5ed02dbb497422bf225783f46e6eadd237d23d6b (4.12-rc3).
>
> Unfortunately it's not reproducible.
>
> ==
On 05/31/2017 10:28 AM, Phil Elwell wrote:
On 31/05/2017 16:58, Stefan Wahren wrote:
Am 31.05.2017 um 17:27 schrieb Stephen Warren:
On 05/30/2017 06:23 AM, Phil Elwell wrote:
Hi,
I've run into a problem using the fixed-factor clock on Raspberry Pi
and I'd
like some advice before I submit a pa
From: Michal Hocko
Date: Wed, 31 May 2017 18:31:31 +0200
> On Tue 30-05-17 13:16:50, Pasha Tatashin wrote:
>> >Could you be more specific? E.g. how are other stores done in
>> >__init_single_page safe then? I am sorry to be dense here but how does
>> >the full 64B store differ from other stores d
From: Arnd Bergmann
Date: Tue, 30 May 2017 11:26:14 +0200
> The new mlxfw code fails to build without the xz library:
>
> drivers/net/ethernet/mellanox/mlxfw/mlxfw_mfa2.o: In function
> `mlxfw_mfa2_xz_dec_run':
> :(.text.mlxfw_mfa2_xz_dec_run+0x8): undefined reference to `xz_dec_run'
> drivers/
On Tue, May 30, 2017 at 3:50 PM, Douglas Anderson wrote:
> When the "if (record->size <= 0)" test is true in
> pstore_get_backend_records() it's pretty clear that nobody holds a
> reference to the allocated pstore_record, yet we don't free it.
>
> Let's free it.
>
> Fixes: 2a2b0acf768c ("pstore: A
On Wed, May 31, 2017 at 9:45 AM, Cong Wang wrote:
> On Wed, May 31, 2017 at 2:42 AM, Andrey Konovalov
> wrote:
>> Hi,
>>
>> I've got the following error report while fuzzing the kernel with syzkaller.
>>
>> On commit 5ed02dbb497422bf225783f46e6eadd237d23d6b (4.12-rc3).
>>
>> Unfortunately it's n
Hi,
Le lundi 08 mai 2017 à 09:58 -0600, Stephen Warren a écrit :
> On 05/07/2017 12:12 PM, Paul Kocialkowski wrote:
> > Hi,
> >
> > Le mardi 25 avril 2017 à 10:57 -0600, Stephen Warren a écrit :
> > > On 04/24/2017 12:41 PM, Paul Kocialkowski wrote:
> > > > Le lundi 24 avril 2017 à 09:35 -0600, S
501 - 600 of 1025 matches
Mail list logo
