Most HID devices behave properly when they are used with hid-generic.
Since kernel v4.12, we do not poll for input reports at plug in, so
hid-generic should behave properly with all HID devices.
There has been a long standing list of HID devices that have a special
driver. It used to be just a few
On 30.09.2017 21:50, Krzysztof Kozlowski wrote:
> On Wed, Sep 27, 2017 at 02:25:50PM +0200, Kamil Konieczny wrote:
>> Add support for MD5, SHA1, SHA256 hash algorithms for Exynos HW.
>> It uses the crypto framework asynchronous hash api.
>> It is based on omap-sham.c driver.
>> S5P has some HW diff
Better having all the devices quirks in one place.
Note that this change introduces an initial lookup for the device in
hid_gets_squirk(), which should not theoretically be required, but which
actually allows to not have to reparse the list of ignored devices
if we call hid_lookup_quirks twice.
S
On Sun, Oct 01, 2017 at 06:27:11PM -0400, Nicolas Pitre wrote:
> If you prefer, the physical address could be specified with a Kconfig
> symbol just like the kernel link address. Personally I think it is best
> to keep it along with the other root mount args. But going all the way
> with a dynam
usbhid has a list of dynamic quirks in addition to a list of static quirks.
There is not much USB specific in that, so move this part of the module
in core so we can have one central place for quirks.
Signed-off-by: Benjamin Tissoires
---
changes in v2:
- add missing EXPORT_SYMBOL[_GPL] for sepa
On Tuesday, October 03, 2017 1, Rob Herring wrote:
> On Sun, Oct 1, 2017 at 3:29 AM, Christoph Hellwig
> wrote:
> > On Wed, Sep 27, 2017 at 07:32:20PM -0400, Nicolas Pitre wrote:
> >> To distinguish between both access types, the cramfs_physmem filesystem
> >> type must be specified when using a m
On Tue, Oct 03, 2017 at 03:20:50PM +0100, Will Deacon wrote:
> Since commit 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu"),
> when a PMU is unregistered then its associated ->pmu_cpu_context is
> unconditionally freed. Whilst this is fine for dynamically allocated
> context types (
On 10/03/17 00:56, Kangmin Park wrote:
> --- linux/Documentation/sysctl/vm.txt.orig 2017-09-07 00:19:43.260477784 +0900
> +++ linux/Documentation/sysctl/vm.txt 2017-09-07 00:19:56.498431846 +0900
> @@ -793,7 +793,7 @@ with no ill effects: errors and warnings
> swappiness
>
> This control is used
On Sat, Sep 30, 2017 at 02:30:16PM +0530, Abhishek Shah wrote:
> > On a similar note, we also break CMB usage in virutalization with direct
> > assigned devices: the guest doesn't know the host physical bus address,
> > so it sets the CMB queue address incorrectly there, too. I don't know of
> > a
Thanks for the review Andrey, i'll send a new patch removing the lock.
On 03/10/17 15:53, Mark Rutland wrote:
> On Tue, Oct 03, 2017 at 03:20:27PM +0100, Julien Grall wrote:
>> Currently, the examples are using 2MB for the ITS size. Per the
>> specification (section 8.18 in ARM IHI 0069D), the ITS address map is
>> 128KB.
>>
>> Update the examples to match the specifi
On Tue, Oct 03, 2017 at 09:41:36AM -0500, Josh Poimboeuf wrote:
> On Tue, Oct 03, 2017 at 09:31:47AM -0500, Josh Poimboeuf wrote:
> > On Tue, Oct 03, 2017 at 10:06:34PM +0800, Fengguang Wu wrote:
> > > Hi Byungchul,
> > >
> > > This patch triggers a NULL-dereference bug at update_stack_state().
>
On Tue, 3 Oct 2017, Christoph Hellwig wrote:
> On Sun, Oct 01, 2017 at 06:27:11PM -0400, Nicolas Pitre wrote:
> > If you prefer, the physical address could be specified with a Kconfig
> > symbol just like the kernel link address. Personally I think it is best
> > to keep it along with the other
Hi Mark,
I considered using a new *populate() function for shadow without using
vmemmap_populate(), but that makes things unnecessary complicated:
vmemmap_populate() has builtin:
1. large page support
2. device memory support
3. node locality support
4. several config based variants on diffe
On Tue, Oct 03, 2017 at 03:32:45PM +0100, Will Deacon wrote:
> The lockdep subsystem provides a robust way to assert that a lock is
> held, so use that instead of write_can_lock, which can give incorrect
> results for qrwlocks.
>
> Cc: John Johansen
> Cc: Peter Zijlstra
> Signed-off-by: Will Dea
On Tue, Oct 3, 2017 at 10:47 PM, Maxime Ripard
wrote:
> Hi Linus,
>
> On Tue, Oct 03, 2017 at 09:27:17AM +, Linus Walleij wrote:
>> On Mon, Oct 2, 2017 at 2:08 PM, Quentin Schulz
>> wrote:
>>
>> > On AXP813/818, GPIO0 and GPIO1 can be used as LDO as (respectively)
>> > ldo_io0 and ldo_io1.
>>
Hi Michal,
I hope I haven't missed anything but it looks good to me.
Acked-by: Michal Hocko
Thank you for your review.
one nit below
---
arch/x86/mm/init_64.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
in
> -Original Message-
> From: Greg KH [mailto:g...@kroah.com]
> Sent: Tuesday, October 3, 2017 4:23 AM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; Andy Shevchenko ;
> LKML ; platform-driver-...@vger.kernel.org;
> Andy Lutomirski ; quasi...@google.com;
> pali.ro...@gmail.com
> Subje
On Tue, Oct 03, 2017 at 11:23:23AM +0200, Greg KH wrote:
> On Wed, Sep 27, 2017 at 11:02:16PM -0500, Mario Limonciello wrote:
> > For WMI operations that are only Set or Query read or write sysfs
> > attributes created by WMI vendor drivers make sense.
> >
> > For other WMI operations that are run
Josh Poimboeuf wrote:
> On Tue, Oct 03, 2017 at 10:44:13PM +0900, Tetsuo Handa wrote:
> > Josh Poimboeuf wrote:
> >
> > > On Tue, Oct 03, 2017 at 12:37:44PM +0200, Borislav Petkov wrote:
> > > > On Tue, Oct 03, 2017 at 07:29:36PM +0900, Tetsuo Handa wrote:
> > > > > Tetsuo Handa wrote:
> > > > > >
As you separated x86 and sparc patches doing essentially the same I
assume David is going to take this patch?
Correct, I noticed that usually platform specific changes are done in
separate patches even if they are small. Dave already Acked this patch.
So, I do not think it should be separated
According to https://research.google.com/pubs/pub40801.html article,
tail delay is problematic in enterprise service providers.
According to https://dl.acm.org/citation.cfm?id=2670988 article, FIFO
scheduling works best and LIFO is worst for tail latency.
As we test Linux scheduler called CFS, beha
> -Original Message-
> From: Greg KH [mailto:g...@kroah.com]
> Sent: Tuesday, October 3, 2017 4:26 AM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; Andy Shevchenko ;
> LKML ; platform-driver-...@vger.kernel.org;
> Andy Lutomirski ; quasi...@google.com;
> pali.ro...@gmail.com
> Subje
Fix a typo in Documentation/sysctl/vm.txt
Signed-off-by: Kangmin Park
Cc: Jiri Kosina
--- linux/Documentation/sysctl/vm.txt.orig 2017-09-07 00:19:43.260477784 +0900
+++ linux/Documentation/sysctl/vm.txt 2017-09-07 00:19:56.498431846 +0900
@@ -793,7 +793,7 @@ with no ill effects: errors and warn
On Tue, Oct 03, 2017 at 09:35:18AM -0500, Josh Poimboeuf wrote:
> On Tue, Oct 03, 2017 at 10:44:13PM +0900, Tetsuo Handa wrote:
> > Josh Poimboeuf wrote:
> >
> > > On Tue, Oct 03, 2017 at 12:37:44PM +0200, Borislav Petkov wrote:
> > > > On Tue, Oct 03, 2017 at 07:29:36PM +0900, Tetsuo Handa wrote:
This is on top of the parts of the previous series that have been
queued up. I've posted the first patch in a reply to Jan last week,
this is a more official posting. No changes, it works for me. Last
patch is just a cleanup, finally killing off nr_pdflush_threads,
8 years after we deprecated it.
Handle start-all writeback like we do periodic or kupdate
style writeback - by marking the bdi_writeback as needing a full
flush, and simply waking the thread. This eliminates the need to
allocate and queue a specific work item just for this purpose.
After this change, we truly only ever have one
This tunable has been obsolete since 2.6.32, and writes to the
file have been failing and complaining in dmesg since then:
nr_pdflush_threads exported in /proc is scheduled for removal
That was 8 years ago. Remove the file ABI obsolete notice, and
the sysfs file.
Signed-off-by: Jens Axboe
---
On 10/02/2017 10:34 AM, Dave Gerlach wrote:
> Russell,
> On 09/28/2017 03:38 AM, Russell King - ARM Linux wrote:
>> On Tue, Sep 26, 2017 at 07:03:55PM -0500, Dave Gerlach wrote:
>>> diff --git a/drivers/memory/emif-asm-offsets.c
>>> b/drivers/memory/emif-asm-offsets.c
>>> new file mode 100644
>>>
Hi Michal,
Please be explicit that this is possible only because we discard
memblock data later after 3010f876500f ("mm: discard memblock data
later"). Also be more explicit how the new code works.
OK
I like how the resulting code is more compact and smaller.
That was the goal :)
for_e
> -Original Message-
> From: Greg KH [mailto:g...@kroah.com]
> Sent: Tuesday, October 3, 2017 4:24 AM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; Andy Shevchenko ;
> LKML ; platform-driver-...@vger.kernel.org;
> Andy Lutomirski ; quasi...@google.com;
> pali.ro...@gmail.com
> Subje
On Tue, Oct 03, 2017 at 11:26:11AM +0200, Greg KH wrote:
> On Wed, Sep 27, 2017 at 11:02:17PM -0500, Mario Limonciello wrote:
> > +static int dell_wmi_smbios_open(struct inode *inode, struct file *file)
> > +{
> > + return nonseekable_open(inode, file);
> > +}
> > +
> > +static int dell_wmi_smbio
On Mon, Oct 2, 2017 at 4:42 PM, 'Eric Dumazet' via syzkaller
wrote:
> On Mon, Oct 2, 2017 at 7:21 AM, Mark Rutland wrote:
>> Hi Eric,
>>
>> On Mon, Oct 02, 2017 at 06:36:32AM -0700, Eric Dumazet wrote:
>>> On Mon, Oct 2, 2017 at 3:49 AM, Mark Rutland wrote:
>>> > I hit the below splat at net/cor
Acked-by: Michal Hocko
Thank you,
Pasha
Josh Poimboeuf wrote:
> On Tue, Oct 03, 2017 at 09:35:18AM -0500, Josh Poimboeuf wrote:
> > On Tue, Oct 03, 2017 at 10:44:13PM +0900, Tetsuo Handa wrote:
> > > Josh Poimboeuf wrote:
> > >
> > > > On Tue, Oct 03, 2017 at 12:37:44PM +0200, Borislav Petkov wrote:
> > > > > On Tue, Oct 03, 2017 at 07:
If CONFIG_DEBUG_LOCK_ALLOC=y, the kernel log is spammed with a few
hundred identical messages:
unwind: Unknown symbol address c0800300
unwind: Index not found c0800300
c0800300 is the return address from the last subroutine call (to
__memzero()) in __mmap_switched(). Apparently having th
Since commit 59dc76b0d4df ("mm: vmscan: reduce size of inactive file list")
'pgdat->inactive_ratio' is not used, except for printing
"node_inactive_ratio: 0" in /proc/zoneinfo output.
Remove it.
Signed-off-by: Andrey Ryabinin
---
include/linux/mmzone.h | 6 --
mm/vmscan.c| 2 +-
On 10/03/2017 09:08 AM, Michal Hocko wrote:
On Wed 20-09-17 16:17:08, Pavel Tatashin wrote:
Add struct page zeroing as a part of initialization of other fields in
__init_single_page().
This single thread performance collected on: Intel(R) Xeon(R) CPU E7-8895
v3 @ 2.60GHz with 1T of memory (26
On Tue, 2017-10-03 at 18:26 +0300, Andrey Ryabinin wrote:
> Since commit 59dc76b0d4df ("mm: vmscan: reduce size of inactive file
> list")
> 'pgdat->inactive_ratio' is not used, except for printing
> "node_inactive_ratio: 0" in /proc/zoneinfo output.
>
> Remove it.
>
> Signed-off-by: Andrey Ryabin
On Tue, 3 Oct 2017 11:33:44 +0200
Ingo Molnar wrote:
>
> * Masami Hiramatsu wrote:
>
> > Jprobe actually doesn't need to disable IRQs while calling
> > handlers, because Documentation/kprobes.txt says:
> >
> > -
> > Probe handlers are run with preemption disabled. Depending on the
> >
Since the Data Strobe pin is optional, take it out of the default
eMMC pins and add a separate entry.
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gx-p23x-q20x.dtsi| 2 +-
arch/arm64/boot/dts/amlogic/meson-gxbb-nanopi-k2.dts | 2 +-
arch/arm64/boot/
The Khadas VIM2 is a Single Board Computer, respin of the origin
Khadas VIM board, using an Amlogic S912 SoC and more server oriented.
It provides the same external connectors and header pinout, plus a SPI
NOR Flash, a reprogrammable STM8S003 MCU, FPC Connector, Cooling FAN header
and Pogo Pads Ar
The Khadas VIM2 is a Single Board Computer, respin of the origin
Khadas VIM board, using an Amlogic S912 SoC and more server oriented.
It provides the same external connectors and header pinout, plus a SPI
NOR Flash, a reprogrammable STM8S003 MCU, FPC Connector, Cooling FAN header
and Pogo Pad
Since we have converted all the user of UFS_BIT() macro
with the actual bit position, let remove unused UFS_BIT()macro.
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshci.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/scsi/ufs/ufshci.h b/drivers/scsi/ufs/ufshci.h
index dec042
Currently UFS HCI uses UFS_BIT() macro to get various bit
position for the hardware registers status bits. Which makes
code longer instead of shorter. This macro does not improve
code readability as well.
Lets re-write these macro definition with the actual bit position.
Suggested-by: Bart Van Ass
HOST_ERROR_INDICATOR and DEVICE_ERROR_INDICATOR are not used
anywhere. Also as per JESD223C specification, bit[7:4] are reserved.
Lets remove these #defines.
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshci.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/scsi/ufs/ufshci.h b/
This patchset adds support for the Tronsmart Vega S96 TV Box based
on the Q200 Amlogic Reference design.
Changes since v1 at [1] :
- Add acks
- Cleanup external_phy node
[1]
https://lkml.kernel.org/r/1505822748-23431-1-git-send-email-narmstr...@baylibre.com
Neil Armstrong (2):
ARM64: dts:
The Tronsmart Vega S96 is a TV box derived from Amlogic q200 reference design.
Cc: supp...@tronsmart.com
Acked-by: Jerome Brunet
Signed-off-by: Oleg Ivanov
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/Makefile | 1 +
arch/arm64/boot/dts/amlogic/meson-gxm-vega-s9
Cc: supp...@tronsmart.com
Acked-by: Jerome Brunet
Signed-off-by: Oleg Ivanov
Signed-off-by: Neil Armstrong
---
Documentation/devicetree/bindings/arm/amlogic.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt
b/Documentation/devicetree/bind
On Tue, 3 Oct 2017, Christoph Hellwig wrote:
> On Mon, Oct 02, 2017 at 07:33:29PM -0400, Nicolas Pitre wrote:
> > On Tue, 3 Oct 2017, Richard Weinberger wrote:
> >
> > > On Mon, Oct 2, 2017 at 12:29 AM, Nicolas Pitre
> > > wrote:
> > > > On Sun, 1 Oct 2017, Christoph Hellwig wrote:
> > > >
> >
Use actual bit position instead of UFS_BIT() macro. This
patch also changes bit-17 to meaningful #define.
This change is as per discussion here [1]
[1] -> https://lkml.org/lkml/2017/8/28/786
Signed-off-by: Alim Akhtar
Cc: Subhash Jadavani
---
drivers/scsi/ufs/ufs-qcom.c | 4 ++--
drivers/scsi/
On 10/03/2017 09:18 AM, Michal Hocko wrote:
On Wed 20-09-17 16:17:10, Pavel Tatashin wrote:
Some memory is reserved but unavailable: not present in memblock.memory
(because not backed by physical pages), but present in memblock.reserved.
Such memory has backing struct pages, but they are not ini
On 10/03/2017 07:32 AM, Will Deacon wrote:
> The lockdep subsystem provides a robust way to assert that a lock is
> held, so use that instead of write_can_lock, which can give incorrect
> results for qrwlocks.
>
> Cc: John Johansen
> Cc: Peter Zijlstra
> Signed-off-by: Will Deacon
oh nice,
Ac
On 10/03/2017 09:19 AM, Michal Hocko wrote:
On Wed 20-09-17 16:17:14, Pavel Tatashin wrote:
vmemmap_alloc_block() will no longer zero the block, so zero memory
at its call sites for everything except struct pages. Struct page memory
is zero'd by struct page initialization.
Replace allocators i
On Tue, Oct 03, 2017 at 11:30:50AM -0400, Nicolas Pitre wrote:
> Unless you have a better scheme altogether to suggest of course, given
> the existing constraints.
I still can't understand why this convoluted fault path that finds
vma, attempts with all kinds of races and then tries to update th
On Tue, 3 Oct 2017 08:51:43 -0500
Josh Poimboeuf wrote:
> Richard Weinberger saw an unwinder warning when running bcc's opensnoop:
>
> WARNING: kernel stack frame pointer at 99ef4076bea0 in opensnoop:2008
> has bad value 0008
> unwind stack type:0 next_sp: (null) m
On Tue, 3 Oct 2017, Geert Uytterhoeven wrote:
> If CONFIG_DEBUG_LOCK_ALLOC=y, the kernel log is spammed with a few
> hundred identical messages:
>
> unwind: Unknown symbol address c0800300
> unwind: Index not found c0800300
>
> c0800300 is the return address from the last subroutine call
On 10/03/2017 04:32 AM, Jon Hunter wrote:
On 03/10/17 00:02, Dmitry Osipenko wrote:
On 02.10.2017 20:05, Stephen Warren wrote:
On 09/29/2017 09:11 PM, Dmitry Osipenko wrote:
On 29.09.2017 22:30, Stephen Warren wrote:
On 09/27/2017 02:34 AM, Jon Hunter wrote:
On 27/09/17 02:57, Dmitry Osip
On Tue, Oct 3, 2017 at 8:19 AM, Dmitry Vyukov wrote:
> On Mon, Oct 2, 2017 at 4:42 PM, 'Eric Dumazet' via syzkaller
> wrote:
>> On Mon, Oct 2, 2017 at 7:21 AM, Mark Rutland wrote:
>>> Hi Eric,
>>>
>>> On Mon, Oct 02, 2017 at 06:36:32AM -0700, Eric Dumazet wrote:
On Mon, Oct 2, 2017 at 3:49
On Tue, 2017-10-03 at 20:51 +0530, Alim Akhtar wrote:
> Currently UFS HCI uses UFS_BIT() macro to get various bit
> position for the hardware registers status bits. Which makes
> code longer instead of shorter. This macro does not improve
> code readability as well.
> Lets re-write these macro defi
On Tue, 2017-10-03 at 20:51 +0530, Alim Akhtar wrote:
> Use actual bit position instead of UFS_BIT() macro. This
> patch also changes bit-17 to meaningful #define.
Reviewed-by: Bart Van Assche
On Tue, 2017-10-03 at 20:51 +0530, Alim Akhtar wrote:
> HOST_ERROR_INDICATOR and DEVICE_ERROR_INDICATOR are not used
> anywhere. Also as per JESD223C specification, bit[7:4] are reserved.
> Lets remove these #defines.
Reviewed-by: Bart Van Assche
On Tue, 3 Oct 2017, Christoph Hellwig wrote:
> On Tue, Oct 03, 2017 at 11:30:50AM -0400, Nicolas Pitre wrote:
> > Unless you have a better scheme altogether to suggest of course, given
> > the existing constraints.
>
> I still can't understand why this convoluted fault path that finds
> vma, at
On Tue, 2017-10-03 at 20:51 +0530, Alim Akhtar wrote:
> Since we have converted all the user of UFS_BIT() macro
> with the actual bit position, let remove unused UFS_BIT()macro.
Reviewed-by: Bart Van Assche
On Tue, 2017-10-03 at 17:24 +0200, Neil Armstrong wrote:
> The Khadas VIM2 is a Single Board Computer, respin of the origin
> Khadas VIM board, using an Amlogic S912 SoC and more server oriented.
>
> It provides the same external connectors and header pinout, plus a SPI
> NOR Flash, a reprogra
On Tue, 03 Oct 2017 16:21:57 +0200,
Alan Stern wrote:
>
> On Tue, 3 Oct 2017, Takashi Iwai wrote:
>
> > On Mon, 25 Sep 2017 14:39:51 +0200,
> > Andrey Konovalov wrote:
> > >
> > > Hi!
> > >
> > > I've got the following report while fuzzing the kernel with syzkaller.
> > >
> > > On commit e19b2
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Tuesday, October 3, 2017 10:20 AM
> To: Greg KH
> Cc: Limonciello, Mario ; Andy Shevchenko
> ; LKML ;
> platform-driver-...@vger.kernel.org; Andy Lutomirski ;
> quasi...@google.com; pali.ro...@gmail.com
> Subjec
From: Arnaldo Carvalho de Melo
The hfi1 driver calls request_threaded_irq with two parameters:
handler = receive_context_interrupt;
thread = receive_context_thread;
request_threaded_irq(me->msix.vector, handler, thread, 0, me->name, arg);
And tries to process packets on the ha
From: Arnaldo Carvalho de Melo
sc_buffer_alloc() disables preemption that will be reenabled by either
pio_copy() or seg_pio_copy_end(). But before disabling preemption it
grabs a spin lock that will be dropped after it disables preemption,
which ends up triggering a warning in migrate_disable() l
Hi,
Please consider pulling into the linux-4.11.y-rt branch,
It was tested with a simple netperf script found below (that I
intercepted from PeterZ :-)), systems with default kernel tunables, with
the following results:
# Both machines:
[root@opa0-qa-06 ~]# getconf _NPROCESSORS_O
On Tue, Oct 3, 2017 at 3:04 AM, Mark Rutland wrote:
> Hi Kees,
>
> On Mon, Oct 02, 2017 at 12:20:04PM -0700, Kees Cook wrote:
>> As described in the final patch:
>>
>> Nearly all modern compilers support a stack-protector option, and nearly
>> all modern distributions enable the kernel stack-prote
On Tue 03-10-17 08:36:16, Jens Axboe wrote:
> On 10/03/2017 06:25 AM, Jan Kara wrote:
> > On Tue 03-10-17 14:10:49, Jan Kara wrote:
> >> On Wed 27-09-17 14:13:49, Jens Axboe wrote:
> >>> We currently it it for find_or_create_page(), which means that it
> >>> cannot fail. Ensure we also pass in 'ret
Hi Alexey,
On 10/02, Andrew Morton wrote:
>
> From: Alexey Dobriyan
> Subject: pid: delete RESERVED_PIDS
>
> RESERVED_PIDS had a noble goal: to protect root from PID exhaustion since
> at least ~2.5.40
I am just curious, where did you find the change which documents this goal?
> except it never
From: Borislav Petkov
It should say what that range is and what that integer value
means. I had to look at the code...
Signed-off-by: Borislav Petkov
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
---
Documentation/admin-guide/kernel-parameters.txt | 6 ++
1 file changed, 6 insertions
On 10/03/2017 09:37 AM, cjacob wrote:
Implements port to port forwarding with route table and arp table
lookup for ipv4 packets using bpf_redirect helper function and
lpm_trie map.
Signed-off-by: cjacob
Thanks for the patch, just few minor comments below!
Note, should be full name, e.g.:
From: Christoph Hellwig
> Sent: 03 October 2017 11:43
> x86 does not implement DMA_ATTR_NON_CONSISTENT allocations, so it doesn't
> make any sense to do any work in dma_cache_sync given that it must be a
> no-op when dma_alloc_attrs returns coherent memory.
I believe it is just about possible to r
Hi Michal,
Are you OK, if I replace DEFERRED_FREE() macro with a function like this:
/*
* Helper for deferred_init_range, free the given range, and reset the
* counters
*/
static inline unsigned long __def_free(unsigned long *nr_free,
unsigned long *free
On Tue, 2017-10-03 at 10:39 +0200, Peter Zijlstra wrote:
> On Mon, Oct 02, 2017 at 11:53:12PM +0100, Matt Fleming wrote:
> > On Wed, 27 Sep, at 01:58:20PM, Rik van Riel wrote:
> > >
> > > I like the simplicity of your approach! I hope it does not break
> > > stuff like netperf...
> > >
> > > I h
On 9/28/17 1:03 PM, Volodymyr Babchuk wrote:
From: Volodymyr Babchuk
This patch series enables dynamic shared memory support in the TEE
subsystem as a whole and in OP-TEE in particular.
Global Platform TEE specification [1] allows client applications
to register part of own memory as a share
On Tue, Oct 3, 2017 at 2:34 PM, Colin Ian King wrote:
> On 03/10/17 12:39, Rafael J. Wysocki wrote:
>> On Tuesday, October 3, 2017 3:16:22 AM CEST Jérémy Lefaure wrote:
>>> On Mon, 02 Oct 2017 14:27:52 +0200
>>> "Rafael J. Wysocki" wrote:
>>>
ACPICA is soewhat special code, though and I'm no
On 9/28/17 1:04 PM, Volodymyr Babchuk wrote:
From: Volodymyr Babchuk
Previous patches added various features that are needed for dynamic SHM.
Dynamic SHM allows Normal World to share any buffers with OP-TEE.
While original design suggested to use pre-allocated region (usually of
1M to 2M of s
Em Tue, Sep 12, 2017 at 12:56:43PM -0700, Andi Kleen escreveu:
> From: Andi Kleen
>
> There are still problems with BPF misinterpreting some events
> that include .c. An earlier fix made it work for stand alone
> aliases, but it still fails for more complex constructs.
Hi Wang, Jiri,
Ca
On Fri, Sep 29, 2017 at 02:17:32AM +0200, Jens Axboe wrote:
> On 09/28/2017 11:44 PM, Linus Torvalds wrote:
> > On Thu, Sep 28, 2017 at 2:41 PM, Andrew Morton
> > wrote:
> >>
> >> test_and_set_bit()?
> >
> > If there aren't any atomicity concerns (either because of higher-level
> > locking, or be
The util-linux release v2.31-rc2 is available at
http://www.kernel.org/pub/linux/utils/util-linux/v2.31/
Feedback and bug reports, as always, are welcomed.
Karel
Util-linux 2.31 Release Notes
=
The package build-system follows GNU Coding Standards and uses
On Tue, Oct 3, 2017 at 5:38 PM, 'Eric Dumazet' via syzkaller
wrote:
> On Tue, Oct 3, 2017 at 8:19 AM, Dmitry Vyukov wrote:
>> On Mon, Oct 2, 2017 at 4:42 PM, 'Eric Dumazet' via syzkaller
>> wrote:
>>> On Mon, Oct 2, 2017 at 7:21 AM, Mark Rutland wrote:
Hi Eric,
On Mon, Oct 02, 20
Hi Paolo,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9e66317d3c92ddaab330c125dfe9d06eee268aff
commit: c0a1666bcb2a33e84187a15eabdcd54056be9a97 KVM: VMX: use cmpxchg64
date: 5 days ago
config: i386-randconfig
On Tue, Oct 3, 2017 at 7:46 AM, Eric W. Biederman wrote:
>
> The process that requests the signal be sent is the process that is
> receiving the signal. I can see a theoretical need for a permission
> check in there somewhere (especially as this persists over fork).
Note that it also persists ov
There was code in checkpatch that allowed continuation printks
to be used without KERN_CONT. Remove the continuation check
and always require a KERN_.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 26 --
1 file changed, 4 insertions(+), 22 deletions(-)
diff --g
On 10/03/2017 10:06 AM, Matthew Wilcox wrote:
> On Fri, Sep 29, 2017 at 02:17:32AM +0200, Jens Axboe wrote:
>> On 09/28/2017 11:44 PM, Linus Torvalds wrote:
>>> On Thu, Sep 28, 2017 at 2:41 PM, Andrew Morton
>>> wrote:
test_and_set_bit()?
>>>
>>> If there aren't any atomicity concerns (e
On Sat, Sep 30, 2017 at 12:49:00PM +0530, Srishti Sharma wrote:
> Replaces instances of container_of with list_entry to
> access current list element.
>
> Srishti Sharma (6):
> Staging: rtl8188eu: core: Use list_entry instead of container_of
> Staging: rtl8188eu: core: Use list_entry instead
On 10/02, Andrew Morton wrote:
>
> From: Alexey Dobriyan
> Subject: pid: delete struct pidmap::nr_free
>
> There is a check in pid allocation code to skip a full page:
>
> if (likely(atomic_read(&map->nr_free))) {
> ...
>
> In practice it doesn't do anything. To skip a pidm
Now acking of edge irqs happens the following way:
- omap_gpio_irq_handler
- "isr" = read irq status
- omap_clear_gpio_irqbank(bank, isr_saved & ~level_mask);
^ clear edge status, so irq can be accepted
- loop while "isr"
generic_handle_irq()
- handle_edge_irq()
On Sun, Oct 01, 2017 at 03:05:11PM -0500, Brijesh Singh wrote:
> I think theoretically a 32-bit host OS can invoke a PSP commands but
> currently PSP interface is exposing only the SEV FW command. And SEV
Let's cross that bridge when we get to it.
> feature is available when we are in 64-bit mode
The intent is to reduce code duplication with other code
iterating the list.
No functional changes.
Signed-off-by: Mateusz Guzik
---
fs/super.c | 61 -
1 file changed, 36 insertions(+), 25 deletions(-)
diff --git a/fs/super.c b/fs/sup
There are 2 distinct freezing mechanisms - one operates on block
devices and another one directly on super blocks. Both end up with the
same result, but thaw of only one of these does not thaw the other.
In particular fsfreeze --freeze uses the ioctl variant going to the
super block. Since prior t
Filesystems frozen with fsfreeze --freeze are not getting thawed with
sysrq j (or echo j > /proc/sysrq-trigger). Thawing only deals with bdev
part, does not do anything about fsfreeze.
I went for the easiest fix possible: just thaw the super block.
Doing it requires a little bit of refactoring in
For static DT usecases, we don't need the disabled nodes and can skip
unflattening. This saves a significant amount of RAM in memory constrained
cases. In one example on STM32F469, the RAM usage goes from 118K to 26K.
There are a few cases in the kernel that modify the status property
dynamically.
Add an equivalent function to of_device_is_available for flattened DT, and
convert the one existing open coded occurrence.
Cc: Nicolas Pitre
Cc: Frank Rowand
Signed-off-by: Rob Herring
---
drivers/of/fdt.c | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/d
On 10/03/2017 11:17 AM, Borislav Petkov wrote:
...
No, please add my patch below to your set for the CRYPTO_DEV_CCP_DD
dependency as it is a separate thing. Your patch should concentrate only
on adding the PSP and its dependencies.
Sure, I will include your patch in my series. thanks
--
On 21/09/2017 16:49, Paolo Bonzini wrote:
> After the first few months, the message has not led to many bug reports.
> It's been almost five years now, and in practice the main source of
> it seems to be MTIOCGET that someone is using to detect tape devices.
> While we could whitelist it just like
701 - 800 of 1098 matches
Mail list logo
