On 09/04/2018 07:40 AM, Jiri Kosina wrote:
> From: Jiri Kosina
>
> Current ptrace_may_access() implementation assumes that the 'source' task is
> always the caller (current).
>
> Expose ___ptrace_may_access() that can be used to apply the check on arbitrary
> tasks.
Casey recently has proposed
On 09/04/2018 07:00 AM, Jerome Glisse wrote:
> On Mon, Sep 03, 2018 at 07:56:54AM +0200, Michal Hocko wrote:
>> On Thu 30-08-18 14:39:44, Jerome Glisse wrote:
>>> For all intents and purposes this is not a backport of the original
>>> patch so maybe we should just drop the commit reference and
Hi David,
On Tue, Sep 04, 2018 at 10:48:27AM -0700, David Miller wrote:
> From: Quentin Schulz
> Date: Mon, 3 Sep 2018 10:48:47 +0200
>
> > LEDs modes are set the same way, except they are offset by 4 times the
> > index of the LED.
> >
> > Let's factorize all the code so that it's easier to
On 8/30/18 11:19 PM, Christoph Hellwig wrote:
+#else
+static inline bool can_hotplug_cpu(void) { return 0; }
+static inline void arch_send_call_wakeup_ipi(int cpu) { }
Please use normal coding style for these stubs.
Done.
#define INTERRUPT_CAUSE_FLAG (1UL << (__riscv_xlen - 1))
Hello,
On Thu, Aug 23, 2018 at 08:07:32AM -0700, Eduardo Valentin wrote:
> On a system with X86_FEATURE_ARCH_PERFMON disabled
> and with a model not known by family PMU drivers,
> user gets a kernel message log like the following:
> [ 0.100114] Performance Events: unsupported p6 CPU model 85 no
On Mon, 2018-07-23 at 14:42 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Sascha Hauer
>
> commit f78e5623f45bab2b726eec29dc5cefbbab2d0b1c upstream.
[...]
This results in a couple of error paths
Fedora got a bug report of a crash with iSCSI:
kernel BUG at include/linux/scatterlist.h:143!
...
RIP: 0010:iscsit_do_crypto_hash_buf+0x154/0x180 [iscsi_target_mod]
...
Call Trace:
? iscsi_target_tx_thread+0x200/0x200 [iscsi_target_mod]
iscsit_get_rx_pdu+0x4cd/0xa90 [iscsi_target_mod]
?
On Tue, 4 Sep 2018, Ding Xiang wrote:
> simple_strtoul is obsolete, and use kstrtouint instead
>
> Signed-off-by: Ding Xiang
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
next-general
and next-testing.
--
James Morris
On Tue, Sep 04, 2018 at 06:15:14PM +0530, Anup Patel wrote:
> Instead of directly calling RISC-V timer interrupt handler from
> RISC-V local interrupt conntroller driver, this patch implements
> RISC-V timer interrupt as a per-CPU interrupt using per-CPU APIs
> of Linux IRQ subsystem.
And the
On Sat, Sep 01, 2018 at 07:28:23PM +0800, Fengguang Wu wrote:
> Signed-off-by: Fengguang Wu
> ---
> arch/x86/kvm/Kconfig | 11 +++
> arch/x86/kvm/Makefile | 4
> 2 files changed, 15 insertions(+)
>
> diff --git a/arch/x86/kvm/Kconfig b/arch/x86/kvm/Kconfig
> index
On Tue, Sep 4, 2018 at 10:07 PM Afonso Bordado wrote:
>
> This patch adds support for reading/writing ODR/Scale
>
> We don't support the scale boost modes.
> @@ -44,7 +44,10 @@
> #define FXAS21002C_REG_F_EVENT 0x0A
> #define FXAS21002C_REG_INT_SRC_FLAG0x0B
> #define
On 09/04/2018 11:33 AM, Alexander Duyck wrote:
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -1444,7 +1444,7 @@ void * __init memblock_virt_alloc_try_nid_raw(
>
> ptr = memblock_virt_alloc_internal(size, align,
> min_addr, max_addr, nid);
>
On Tue, Sep 04, 2018 at 06:30:21PM +0300, Jarkko Sakkinen wrote:
> On Tue, Sep 04, 2018 at 07:54:51AM -0700, Sean Christopherson wrote:
> > I don't see any value in trying to rule out specific causes of
> > INVALID_TOKEN, but we should only retry EINIT if ret==INVALID_TOKEN
> > and RDMSR(HASH0) !=
On Sun, 2 Sep 2018 13:03:43 +
Sasha Levin wrote:
> [
> Note, this only fixes the symptom. The real fix was not to call
> this function when tracing_on was already one. But this still makes
> the code more robust, so we'll add it.
> ]
This patch really didn't need to be backported (which
On Mon, Sep 3, 2018 at 11:39 AM Holger Hoffstätte
wrote:
>
> Sep 3 20:19:38 ragnarok kernel: tlb_flush_mmu_tlbonly+0x76/0xc0
> Sep 3 20:19:38 ragnarok kernel: tlb_table_flush.part.13+0xe/0x30
> Sep 3 20:19:38 ragnarok kernel: tlb_flush_mmu_tlbonly+0x54/0xc0
> ..a few hundred times..
> Sep
On Tue, Sep 4, 2018 at 3:13 AM, Grant Likely wrote:
> Hey folks. More comments below, but the short answer is I really don't
> see what the problem is. Distros cannot easily support platforms that
> require a dtb= parameter, and so they probably won't. They may or may
> not disable 'dtb=',
On a platform with MB resource enabled, a divided-by-zero
exception is triggered when accessing 'size':
[ 151.193447] divide error: [#1] SMP PTI
[ 151.197743] CPU: 93 PID: 1929 Comm: cat Not tainted 4.19.0-rc2-debug-rdt+ #25
[ 151.205070] Hardware name: Dell Inc. PowerEdge R640/0CRT1G,
This patch adds the device ID for the AMPAK AP6335 combo module used
in the 1st generation WeTek Hub Android/LibreELEC HTPC box. The WiFI
chip identifies itself as BCM4339, while Bluetooth identifies itself
as BCM4335 (rev C0):
```
[4.864248] Bluetooth: hci0: BCM: chip id 86
[4.866388]
On Fri, 2018-08-31 at 17:35 +0200, Tomasz Duszynski wrote:
> On Thu, Aug 30, 2018 at 10:18:22PM +0100, Afonso Bordado wrote:
> > FXAS21002C is a 3 axis gyroscope with integrated temperature sensor
> >
> > Signed-off-by: Afonso Bordado
> > ---
> > Changes in v2
> >- Use ANSI C Comments
> >
On 08/24/2018 11:52 AM, Will Deacon wrote:
> I hacked up this RFC on the back of the recent changes to the mmu_gather
> stuff in mainline. It's had a bit of testing and it looks pretty good so
> far.
I will request the server folks go and test this. You'll probably
remember a couple of parts
During probe, the port driver will disable error reporting and assumes
it will be enabled later by the AER driver's pci_walk_bus() sequence.
This may not be the case for host-bridge enabled root ports, who will
enable first error reporting on the bus during the root port probe, and
then disable
On Tue, Sep 04, 2018 at 06:15:12PM +0530, Anup Patel wrote:
> This patch selects following GENERIC_IRQ kconfig options:
> GENERIC_IRQ_MULTI_HANDLER
This is already selected by arch/riscv/Kconfig.
> GENERIC_IRQ_PROBE
This is something only used by ISA drivers. Why would we want that
on RISC-V?
On 08/29/18 17:50, Manivannan Sadhasivam wrote:
On Wed, Aug 29, 2018 at 10:24:11AM +0200, Saravanan Sekar wrote:
Add pinctrl and pio bindings for Actions Semi S700 SoC.
Signed-off-by: Parthiban Nallathambi
Signed-off-by: Saravanan Sekar
Reviewed-by: Rob Herring
---
On Tue, Sep 4, 2018 at 10:06 PM Afonso Bordado wrote:
>
> This patch adds device tree support for the fxas21002c driver, including
> bindings.
>
> Signed-off-by: Afonso Bordado
> +#ifdef CONFIG_OF
> +#endif
Please, remove this ifdef...
> + .of_match_table =
On Tue, Sep 4, 2018 at 10:07 PM Afonso Bordado wrote:
>
> Add entry for fxas21002c gyroscope driver and add myself as
> maintainer of this driver.
>
> Signed-off-by: Afonso Bordado
> ---
> MAINTAINERS | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
>
On Tue, Sep 04, 2018 at 10:08:13AM +0530, Naresh Kamboju wrote:
> On 3 September 2018 at 22:26, Greg Kroah-Hartman
> wrote:
> > 4.18-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Peter Zijlstra
> >
> > commit
On Tue, Sep 04, 2018 at 09:49:43AM +0530, Naresh Kamboju wrote:
> On 3 September 2018 at 22:24, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.14.68 release.
> > There are 165 patches in this series, all will be posted as a response
> > to this one. If
On Mon, Sep 03, 2018 at 06:55:44PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.18.6 release.
> There are 123 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Sep 3, 2018 at 1:34 PM Miguel Ojeda
wrote:
>
> Cc: Rasmus Villemoes
> Cc: Luc Van Oostenryck
> Cc: Eli Friedman
> Cc: Christopher Li
> Cc: Kees Cook
> Cc: Ingo Molnar
> Cc: Geert Uytterhoeven
> Cc: Arnd Bergmann
> Cc: Greg Kroah-Hartman
> Cc: Masahiro Yamada
> Cc: Joe Perches
>
> .sample = process_sample_event,
> @@ -1678,6 +1680,8 @@ static struct option __record_options[] = {
> "signal"),
> OPT_BOOLEAN(0, "dry-run", _run,
> "Parse options then exit"),
> + OPT_INTEGER(0, "aio", _cblocks,
> +
On Tue, 4 Sep 2018, Tim Chen wrote:
> > Current ptrace_may_access() implementation assumes that the 'source' task is
> > always the caller (current).
> >
> > Expose ___ptrace_may_access() that can be used to apply the check on
> > arbitrary
> > tasks.
>
> Casey recently has proposed putting
On Mon, Aug 27 2018 at 16:35 -0600, Matthias Kaehlcke wrote:
Hi Lina,
On Fri, Aug 24, 2018 at 02:01:53PM -0600, Lina Iyer wrote:
QCOM SoC's that have Power Domain Controller (PDC) chip in the always-on
domain can wakeup the SoC, when interrupts and GPIOs are routed to the
its interrupt
On Mon, 2018-09-03 at 23:53 -0700, Francisco Jerez wrote:
> Eero Tamminen writes:
>
> > Hi,
> >
> > On 31.08.2018 20:28, Srinivas Pandruvada wrote:
> > ...
> > > As per testing Eero Tamminen, the results are comparable to the
> > > patchset
> > > https://patchwork.kernel.org/patch/10312259/
> >
Hi,
On 04.09.2018 20:34, Andi Kleen wrote:
>> .sample = process_sample_event,
>> @@ -1678,6 +1680,8 @@ static struct option __record_options[] = {
>>"signal"),
>> OPT_BOOLEAN(0, "dry-run", _run,
>> "Parse options then exit"),
>> +
Thanks Baoquan!
Reviewed-by: Thomas Garnier
On Wed, Aug 29, 2018 at 4:49 AM Kirill A. Shutemov wrote:
>
> On Wed, Aug 29, 2018 at 10:17:53AM +0800, Baoquan He wrote:
> > In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the
> > initial size of the direct mapping region. This is
On Wed, Aug 29, 2018 at 06:04:07AM +0200, Dominique Martinet wrote:
> The 'm' kcore_list item can point to kclist_head, and it is incorrect to
> look at m->addr / m->size in this case.
> There is no choice but to run through the list of entries for every address
> if we did not find any entry in
[now CC Vladimir for real]
On Tue 04-09-18 20:06:31, Michal Hocko wrote:
> On Tue 04-09-18 10:52:46, Roman Gushchin wrote:
> > On Tue, Sep 04, 2018 at 06:14:31PM +0200, Michal Hocko wrote:
> [...]
> > > I am not opposing your patch but I am trying to figure out whether that
> > > is the best
On Tue 04-09-18 10:52:46, Roman Gushchin wrote:
> On Tue, Sep 04, 2018 at 06:14:31PM +0200, Michal Hocko wrote:
[...]
> > I am not opposing your patch but I am trying to figure out whether that
> > is the best approach.
>
> I don't think the current logic does make sense. Why should cgroups
>
Devices using the new V4L2 mem2mem vdec require a larger CMA pool. As
nearly all GX* devices are video/media focused and will use it, set a
larger (256MB) default value.
Signed-off-by: Christian Hewitt
---
arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 2 +-
1 file changed, 1 insertion(+), 1
This patch adds support for reading/writing ODR/Scale
We don't support the scale boost modes.
Signed-off-by: Afonso Bordado
---
drivers/iio/gyro/fxas21002c.c | 161 +++---
1 file changed, 148 insertions(+), 13 deletions(-)
diff --git a/drivers/iio/gyro/fxas21002c.c
This patch adds device tree support for the fxas21002c driver, including
bindings.
Signed-off-by: Afonso Bordado
---
.../bindings/iio/gyroscope/fsl,fxas21002c.txt | 35 +++
drivers/iio/gyro/fxas21002c.c | 10 +-
2 files changed, 44 insertions(+), 1
On Tue, Sep 4, 2018 at 10:08 PM Afonso Bordado wrote:
>
> FXAS21002C is a 3 axis gyroscope with integrated temperature sensor
>
> Signed-off-by: Afonso Bordado
> ---
> Changes in v3
>- Use unsigned int on regmap functions
>- Remove the export of the regmap config
>- Fix undefined
On 09/04/2018 11:33 AM, Alexander Duyck wrote:
> +++ b/mm/page_alloc.c
> @@ -1231,7 +1231,7 @@ void __meminit reserve_bootmem_region(phys_addr_t
> start, phys_addr_t end)
> /* Avoid false-positive PageTail() */
> INIT_LIST_HEAD(>lru);
>
> -
On 09/03/2018 11:53 PM, Pavel Machek wrote:
> Hi!
>
>>> +static int pattern_trig_start_pattern(struct led_classdev *led_cdev)
>>> +{
>>> + struct pattern_trig_data *data = led_cdev->trigger_data;
>>> +
>>> + if (!data->npatterns)
>>> + return 0;
>>> +
>>> + if
On Mon, 3 Sep 2018 09:22:47 -0700
Andi Kleen wrote:
> Fix ETM build failure
> ---
> diff --git a/tools/perf/util/cs-etm.c b/tools/perf/util/cs-etm.c
> index 2ae640257fdb..0296405f38b2 100644
> --- a/tools/perf/util/cs-etm.c
> +++ b/tools/perf/util/cs-etm.c
> @@ -1432,7 +1432,8 @@ int
The ION_IOC_{MAP,SHARE} ioctls drop and reacquire client->lock several
times while operating on one of the client's ion_handles. This creates
windows where userspace can call ION_IOC_FREE on the same client with
the same handle, and effectively make the kernel drop its own reference.
For example:
Dear Maintainers,
This series is still needed to complete the initial cache pseudo-locking
implementation and still applies cleanly to both x86/cache of tip.git as
well as v4.19-rc2.
At this time users are unable to measure the success of their cache
pseudo-locked regions and either need to
On Fri, Aug 31, 2018 at 06:57:47PM +0530, Manish Narani wrote:
> Add platform specific structures, so that we can add different IP
> support later using quirks.
>
> Signed-off-by: Manish Narani
> ---
> drivers/edac/synopsys_edac.c | 78
> +---
> 1 file
On 18-09-04 03:13 AM, Grant Likely wrote:
Hey folks. More comments below, but the short answer is I really don't
see what the problem is. Distros cannot easily support platforms that
require a dtb= parameter, and so they probably won't. They may or may
not disable 'dtb=', depending on whether
Hi RT folks!
The call for proposals (CfP) is now open for the RT Microconference at
Linux Plumbers in Vancouver, Canada. The topics we are looking at this
year are:
- How will PREEMPT_RT be maintained (is it a subsystem?)
- Who will maintain it?
- How do we teach the rest of the kernel
On Mon, Aug 27 2018 at 16:57 -0600, Matthias Kaehlcke wrote:
Hi Lina,
On Fri, Aug 24, 2018 at 02:01:55PM -0600, Lina Iyer wrote:
During suspend the system may power down some of the system rails. As a
result, the TLMM hw block may not be operational anymore and wakeup
capable GPIOs will not be
On Tue, Sep 04, 2018 at 06:14:31PM +0200, Michal Hocko wrote:
> On Tue 04-09-18 08:34:49, Roman Gushchin wrote:
> > On Tue, Sep 04, 2018 at 09:00:05AM +0200, Michal Hocko wrote:
> > > On Mon 03-09-18 13:28:06, Roman Gushchin wrote:
> > > > On Mon, Sep 03, 2018 at 08:29:56PM +0200, Michal Hocko
Hi,
On 04-09-18 17:25, Hans de Goede wrote:
Hi,
On 04-09-18 16:42, Hans de Goede wrote:
X86's setup_arch() calls parse_early_param() somewhat late, to make
sure that everything is setup correcty to deal with earlyprintk over
the EHCI debug port.
This means that a number of pr_info-s get done
On Tue, Sep 4, 2018 a> +/**
> > > + va = ioremap_cache(addr, size);
> > > + if (!va)
> > > + return -ENOMEM;
> >
> > I'm not sure this is a right API. Do we operate with memory? Does it
> > have I/O side effects?
> > If no, memremap() would be better to use.
>
>
On Mon, Sep 03, 2018 at 06:54:46PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.68 release.
> There are 165 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Tue, Sep 4, 2018 at 6:13 AM Abel Vesa wrote:
>
> On Tue, Aug 28, 2018 at 12:11:13PM -0700, Andrey Smirnov wrote:
> > On Tue, Aug 28, 2018 at 3:58 AM Abel Vesa wrote:
> > >
> > > On Fri, Aug 24, 2018 at 09:40:11AM +0200, Sascha Hauer wrote:
> > > > +Cc Andrey Smirnov who made me aware of this
On Tue, 4 Sep 2018, Benjamin Tissoires wrote:
> When implementing commit 7f81c8db5489 ("HID: multitouch: simplify
> the settings of the various features"), I wrongly removed a test
> that made sure we never try to set the second InputMode feature
> to something else than 0.
>
> This broke badly
On Mon, Sep 03, 2018 at 12:45:45PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix kernel-doc warnings for missing parameter descriptions:
>
> ../include/linux/srcu.h:175: warning: Function parameter or member 'p' not
> described in 'srcu_dereference_notrace'
>
On Tue, 4 Sep 2018, Thomas Gleixner wrote:
> On Tue, 4 Sep 2018, Yang, Bin wrote:
> > On Tue, 2018-09-04 at 00:27 +0200, Thomas Gleixner wrote:
> > > On Tue, 21 Aug 2018, Bin Yang wrote:
> > > > @@ -625,6 +625,7 @@ try_preserve_large_page(pte_t *kpte, unsigned long
> > > > address,
> > > >
> >
On Mon, Aug 27, 2018 at 9:58 PM Jarkko Sakkinen
wrote:
>
> Intel Software Guard eXtensions (SGX) is a set of CPU instructions that
> can be used by applications to set aside private regions of code and
> data. The code outside the enclave is disallowed to access the memory
> inside the enclave by
On 8/30/18 11:03 PM, Christoph Hellwig wrote:
On Tue, Aug 28, 2018 at 01:36:08AM -0700, Atish Patra wrote:
Currently, both linux cpu id and hardware cpu id are same.
This is not recommended as it will lead to discontinuous cpu
indexing in Linux. Moreover, kdump kernel will run from CPU0
which
Hi,
Hope all is well!
We are a database organization. We provide business executives' contact
information.
Below, I've included a few examples:
Industry-Specific Lists: Agriculture, Business Services, Chambers of
Commerce, Cities, Towns & Municipalities, Construction, Consumer Services,
From: Colin Ian King
In the case where IS_BUILTIN(CONFIG_AC97_BUS)) is not true, the
wm97xx_driver driver is being unregistered even it has not been
previously registered. Fix this by only unregistering it if
IS_BUILTIN(CONFIG_AC97_BUS)) is true. This fixes the warning
message:
[ 834.111248]
On Tue, Sep 04, 2018 at 06:15:11PM +0530, Anup Patel wrote:
> The scause is already part of pt_regs so no need to pass
> scause as separate arg to do_IRQ().
>
> Signed-off-by: Anup Patel
Looks fine,
Reviewed-by: Christoph Hellwig
): []
__do_softirq+0x47c/0x574
[ 33.073284] softirqs last disabled at (389): []
irq_exit+0x134/0x148
[ 33.084852] CPU: 3 PID: 27 Comm: migration/3 Tainted: GW
4.19.0-rc2-next-20180904-1-g32563c06c8db-dirty #42
[ 33.095929] Hardware name: Qualcomm Technologies, Inc. DB820c (DT
On Tue, 4 Sep 2018, Andrea Parri wrote:
> Heh, your confusion might be the reflection of mine... ;-) That was
> indeed a long and not conclusive discussion (meaning there're pending
> issues); and I cannot claim to find "arguments" such as:
>
> "More than one kernel developer has expressed the
On 09/03/2018 10:48 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.121 release.
> There are 56 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Tue, 4 Sep 2018, Benjamin Tissoires wrote:
> Hi Jiri,
>
> there is no real link between those 4 commit but the fact that I wrote
> them today ;)
>
> 2 patches should at least be scheduled for v4.19: 1/4 and 3/4
> Both are stable fixes for mistakes I made in v4.18.
>
> Patch 2 and 4 are just
On Tue, Sep 04, 2018 at 01:52:25PM +0530, Naresh Kamboju wrote:
> On 3 September 2018 at 22:25, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.9.125 release.
> > There are 107 patches in this series, all will be posted as a response
> > to this one. If
On Mon, Sep 03, 2018 at 05:41:53PM +0300, Andy Shevchenko wrote:
> On Mon, Aug 27, 2018 at 9:58 PM Jarkko Sakkinen
> wrote:
>
> > + va = ioremap_cache(addr, size);
> > + if (!va)
> > + return -ENOMEM;
>
> I'm not sure this is a right API. Do we operate with memory?
Commit 375899cddcbb ("printk: make sure to print log on console."), moved
the checking of the loglevel of messages from flush time to the actual
log time.
This introduces one problem, some early boot messages are printed before
parse_early_param() gets called and thus before kernel commandline
Am Dienstag, den 04.09.2018, 10:00 +0200 schrieb Dmitry Vyukov:
> On Tue, Sep 4, 2018 at 8:27 AM, Uecker, Martin
> wrote:
> > Am Montag, den 03.09.2018, 14:28 -0700 schrieb Linus Torvalds:
Hi Dmitry,
> Compiler and KASAN should still be able to do checking against the
> static array size.
From: Alexander Duyck
On systems with a large amount of memory it can take a significant amount
of time to initialize all of the page structs with the PAGE_POISON_PATTERN
value. I have seen it take over 2 minutes to initialize a system with
over 12GB of RAM.
In order to work around the issue I
On Wed, Aug 29, 2018 at 08:44:30PM +0800, Pu Wen wrote:
> Hygon processors use modern APIC, so just return in modern_apic() and
> sync_Arb_IDs(). And should break in switch case in detect_init_API().
>
> When running on 32 bit mode, should set bigsmp if there are more than
> 8 cores.
>
>
On 09/04/2018 09:33 AM, Greg Hackmann wrote:
The ION_IOC_{MAP,SHARE} ioctls drop and reacquire client->lock several
times while operating on one of the client's ion_handles. This creates
windows where userspace can call ION_IOC_FREE on the same client with
the same handle, and effectively make
From: Alexander Duyck
It doesn't make much sense to use the atomic SetPageReserved at init time
when we are using memset to clear the memory and manipulating the page
flags via simple "&=" and "|=" operations in __init_single_page.
This patch adds a non-atomic version __SetPageReserved that can
This patch series is meant to address some issues I consider to be
low-hanging fruit in regards to memory initialization optimization.
With these two changes I am able to cut the hot-plug memory initialization
times in my environment in half.
---
Alexander Duyck (2):
mm: Move page struct
On 08/29/18 17:20, Manivannan Sadhasivam wrote:
Hi Saravanan,
On Wed, Aug 29, 2018 at 10:24:09AM +0200, Saravanan Sekar wrote:
Move generic defines common to the Owl family out of S900 driver.
Signed-off-by: Parthiban Nallathambi
Signed-off-by: Saravanan Sekar
---
On Tue, 4 Sep 2018, Schaufler, Casey wrote:
> > So if this should be done in LSM, it'd probably have to be written by
> > someone else than me :) who actually understands how the "sidechannel LSM"
> > idea works.
>
> Yes. That would be me.
Ok, cool. Then 1/2 and 2/3 can be ignored / replaced
On Tue, Sep 04, 2018 at 06:23:48PM +0200, Rogier Wolff wrote:
> On Tue, Sep 04, 2018 at 12:12:03PM -0400, J. Bruce Fields wrote:
> > Well, I think the point was that in the above examples you'd prefer that
> > the read just fail--no need to keep the data. A bit marking the file
> > (or even the
On Tue, Sep 04, 2018 at 06:15:13PM +0530, Anup Patel wrote:
> Few advantages of this new driver over previous one are:
> 1. It registers all local interrupts as per-CPU interrupts
Please explain why this is an advantage.
> 2. We can develop drivers for devices with per-CPU local interrupts
>
Hi Christian,
On Tue, Sep 4, 2018 at 4:47 PM chewitt wrote:
>
> This change adds the ttyAML1 uart used by the brmcfmac sdio module in
> the WeTek Hub and WeTek Play 2 devices.
do you know which Broadcom chip this is exactly?
I assume you want to use the "patchram" userspace program (or
On 08/29/18 18:34, Manivannan Sadhasivam wrote:
On Wed, Aug 29, 2018 at 10:24:12AM +0200, Saravanan Sekar wrote:
Add pinctrl driver for Actions Semi S700 SoC. The driver supports pinctrl,
pinmux and pinconf functionalities through a range of registers common to
both gpio driver and pinctrl
On 09/03/2018 10:55 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.125 release.
> There are 107 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Tue, Sep 04, 2018 at 10:12:13AM -0700, Linus Torvalds wrote:
> On Mon, Sep 3, 2018 at 11:39 AM Holger Hoffstätte
> wrote:
> >
> > Sep 3 20:19:38 ragnarok kernel: tlb_flush_mmu_tlbonly+0x76/0xc0
> > Sep 3 20:19:38 ragnarok kernel: tlb_table_flush.part.13+0xe/0x30
> > Sep 3 20:19:38
Stephen Rothwell writes:
> [ Unknown signature status ]
> Hi Eric,
>
> Fetching the bcm2835 tree (git://github.com/anholt/linux.git#for-next)
> produces this error:
>
> fatal: Couldn't find remote ref refs/heads/for-next
I'd passed responsibility for the git tree off to Stefan while I'm
> -Original Message-
> From: Jiri Kosina [mailto:ji...@kernel.org]
> Sent: Tuesday, September 04, 2018 10:35 AM
> To: Tim Chen
> Cc: Thomas Gleixner ; Ingo Molnar ;
> Peter Zijlstra ; Josh Poimboeuf
> ; Andrea Arcangeli ;
> Woodhouse, David ; Oleg Nesterov
> ; Schaufler, Casey ; linux-
>
On Tue, Sep 04, 2018 at 09:01:15PM +0300, Andy Shevchenko wrote:
> On Tue, Sep 4, 2018 a> +/**
>
> > > > + va = ioremap_cache(addr, size);
> > > > + if (!va)
> > > > + return -ENOMEM;
> > >
> > > I'm not sure this is a right API. Do we operate with memory? Does it
> > >
On Fri, 2018-08-31 at 17:55 +0530, Himanshu Jha wrote:
> Hello Afonso,
>
> On Thu, Aug 30, 2018 at 10:18:22PM +0100, Afonso Bordado wrote:
> > FXAS21002C is a 3 axis gyroscope with integrated temperature sensor
> >
> > Signed-off-by: Afonso Bordado
> > ---
> > Changes in v2
> >- Use ANSI C
On Tue, Sep 04, 2018 at 06:15:10PM +0530, Anup Patel wrote:
> The mechanism to trigger IPI is generally part of interrupt-controller
> driver for various architectures. On RISC-V, we have an option to trigger
> IPI using SBI or SOC vendor can implement RISC-V CPU where IPI will be
> triggered
On 09/04/2018 01:47 PM, Laura Abbott wrote:
> Fedora got a bug report of a crash with iSCSI:
>
> kernel BUG at include/linux/scatterlist.h:143!
> ...
> RIP: 0010:iscsit_do_crypto_hash_buf+0x154/0x180 [iscsi_target_mod]
> ...
> Call Trace:
> ? iscsi_target_tx_thread+0x200/0x200
FXAS21002C is a 3 axis gyroscope with integrated temperature sensor
Signed-off-by: Afonso Bordado
---
Changes in v3
- Use unsigned int on regmap functions
- Remove the export of the regmap config
- Fix undefined behaviour on dev_err call
- Minor cleanups
Changes in v2
- Use
Add entry for fxas21002c gyroscope driver and add myself as
maintainer of this driver.
Signed-off-by: Afonso Bordado
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2b7b24b145f0..faf5f41b1465 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
On Sat, Sep 01, 2018 at 07:28:20PM +0800, Fengguang Wu wrote:
> diff --git a/fs/proc/internal.h b/fs/proc/internal.h
> index da3dbfa09e79..732a502acc27 100644
> --- a/fs/proc/internal.h
> +++ b/fs/proc/internal.h
> @@ -305,6 +305,7 @@ extern const struct file_operations
>
On 09/03/2018 10:48 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.154 release.
> There are 80 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
For platforms whose firmwares provide valid module handles
(SMBIOS type 17) in error records, this patch uses the module
handles to locate corresponding DIMMs and enables per-DIMM
error counter update.
Signed-off-by: Fan Wu
Reviewed-by: Tyler Baicar
Tested-by: Toshi Kani
---
Changes from v3:
On Fri, Aug 10, 2018 at 09:09:40PM +0530, Bharat Kumar Gogada wrote:
> Add nwl_setup_service_irqs hook to setup_platform_service_irq IRQs to
> register platform provided IRQ number to kernel AER service.
>
> Signed-off-by: Bharat Kumar Gogada
> ---
> drivers/pci/controller/pcie-xilinx-nwl.c |
Hi!
Any other comment before I resubmit v2 tomorrow from
https://github.com/ribalda/linux/tree/gpio-addr-flash-v2
So far the diff for v2 I have
>From Boris Brezillon:
-Add Fixes and cc:stable
>From kbuild:
- Fix warnings
- Rebase
Thanks!
On Tue, Aug 21, 2018 at 4:31 PM Ricardo Ribalda
On Fri, Aug 31, 2018 at 06:57:48PM +0530, Manish Narani wrote:
> Add information of ZynqMP DDRC which reports the single bit errors that
> are corrected and the double bit errors that are detected.
>
> Signed-off-by: Manish Narani
> ---
> .../bindings/memory-controllers/synopsys.txt | 27
Pavel
On 08/31/2018 04:30 PM, Pavel Machek wrote:
> Hi!
>
>>> Aha. I did not realize that was for same hardware... I should have
>>> cc-ed you, I guess.
>>
>> No worries Jacek cc'd me.
>
> Good.
>
I do not like this driver.
I don't like that it smashes numerous devices into some
1 - 100 of 1168 matches
Mail list logo
