[PATCH net-next 1/6] rxrpc: Fix exclusive client connections

Exclusive connections are currently reusable (which they shouldn't be) because rxrpc_alloc_client_connection() checks the exclusive flag in the rxrpc_connection struct before it's initialised from the function parameters. This means that the DONT_REUSE flag doesn't get set. Fix this by checking

[PATCH net-next 3/6] rxrpc: When activating client conn channels, do state check inside lock

In rxrpc_activate_channels(), the connection cache state is checked outside of the lock, which means it can change whilst we're waking calls up, thereby changing whether or not we're allowed to wake calls up. Fix this by moving the check inside the locked region. The check to see if all the

Re: ima measurement carrying on -mm

Am Donnerstag, 29 September 2016, 16:53:50 schrieb Eric W. Biederman: > Thiago Jung Bauermann writes: > > Am Donnerstag, 29 September 2016, 14:02:06 schrieb Andrew Morton: > >> On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann > > > >

[PATCH net-next 4/6] rxrpc: Reduce the rxrpc_local::services list to a pointer

Reduce the rxrpc_local::services list to just a pointer as we don't permit multiple service endpoints to bind to a single transport endpoints (this is excluded by rxrpc_lookup_local()). The reason we don't allow this is that if you send a request to an AFS filesystem service, it will try to talk

[PATCH net-next 6/6] rxrpc: Note serial number being ACK'd in the congestion management trace

Note the serial number of the packet being ACK'd in the congestion management trace rather than the serial number of the ACK packet. Whilst the serial number of the ACK packet is useful for matching ACK packet in the output of wireshark, the serial number that the ACK is in response to is of more

[PATCH net-next 1/6] rxrpc: Fix exclusive client connections

Exclusive connections are currently reusable (which they shouldn't be) because rxrpc_alloc_client_connection() checks the exclusive flag in the rxrpc_connection struct before it's initialised from the function parameters. This means that the DONT_REUSE flag doesn't get set. Fix this by checking

[PATCH net-next 3/6] rxrpc: When activating client conn channels, do state check inside lock

In rxrpc_activate_channels(), the connection cache state is checked outside of the lock, which means it can change whilst we're waking calls up, thereby changing whether or not we're allowed to wake calls up. Fix this by moving the check inside the locked region. The check to see if all the

Re: ima measurement carrying on -mm

Am Donnerstag, 29 September 2016, 16:53:50 schrieb Eric W. Biederman: > Thiago Jung Bauermann writes: > > Am Donnerstag, 29 September 2016, 14:02:06 schrieb Andrew Morton: > >> On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann > > > > wrote: > >> > Hello Andrew, > >> > > >> > You have

[PATCH net-next 2/6] rxrpc: Make Tx loss-injection go through normal return and adjust tracing

In rxrpc_send_data_packet() make the loss-injection path return through the same code as the transmission path so that the RTT determination is initiated and any future timer shuffling will be done, despite the packet having been binned. Whilst we're at it: (1) Add to the tx_data tracepoint an

[PATCH] perf record: Add a tip about system-wide collection from all CPUs

Signed-off-by: Donghyun Kim Cc: Namhyung Kim Cc: Jiri Olsa Cc: Taeung Song --- tools/perf/Documentation/tips.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/Documentation/tips.txt

[PATCH net-next 2/6] rxrpc: Make Tx loss-injection go through normal return and adjust tracing

In rxrpc_send_data_packet() make the loss-injection path return through the same code as the transmission path so that the RTT determination is initiated and any future timer shuffling will be done, despite the packet having been binned. Whilst we're at it: (1) Add to the tx_data tracepoint an

[PATCH] perf record: Add a tip about system-wide collection from all CPUs

Signed-off-by: Donghyun Kim Cc: Namhyung Kim Cc: Jiri Olsa Cc: Taeung Song --- tools/perf/Documentation/tips.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/Documentation/tips.txt b/tools/perf/Documentation/tips.txt index 5950b5a..1435d70 100644 ---

[PATCH net-next 0/6] rxrpc: Fixes and adjustments

/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite Tagged thusly: git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git rxrpc-rewrite-20160929 David --- David Howells (6): rxrpc: Fix exclusive client connections rxrpc: Make Tx loss-injection

[PATCH net-next 0/6] rxrpc: Fixes and adjustments

/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite Tagged thusly: git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git rxrpc-rewrite-20160929 David --- David Howells (6): rxrpc: Fix exclusive client connections rxrpc: Make Tx loss-injection

Re: [PATCH v5 00/10] ima: carry the measurement list across kexec

On Thu, 2016-09-29 at 16:37 -0500, Eric W. Biederman wrote: > Mimi Zohar writes: > > > The TPM PCRs are only reset on a hard reboot. In order to validate a > > TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list > > of the running kernel must be

Re: [PATCH v5 00/10] ima: carry the measurement list across kexec

On Thu, 2016-09-29 at 16:37 -0500, Eric W. Biederman wrote: > Mimi Zohar writes: > > > The TPM PCRs are only reset on a hard reboot. In order to validate a > > TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list > > of the running kernel must be saved and then restored on

[PATCH] perf report: Add a tip about source line numbers with overhead

There is a existing tip as below. If you have debuginfo enabled, try: perf report -s sym,srcline However this tip only describe a condition to use --sort sym,scrline options. So there is lack of explanation in the tip. I think that it would be better to add a tip that exactly explain the

[PATCH] perf report: Add a tip about source line numbers with overhead

There is a existing tip as below. If you have debuginfo enabled, try: perf report -s sym,srcline However this tip only describe a condition to use --sort sym,scrline options. So there is lack of explanation in the tip. I think that it would be better to add a tip that exactly explain the

Re: [PATCH] brcmfmac: implement more accurate skb tracking

On 27 September 2016 at 11:24, Arend Van Spriel wrote: > On 26-9-2016 14:38, Rafał Miłecki wrote: >> On 26 September 2016 at 14:13, Rafał Miłecki wrote: >>> On 26 September 2016 at 13:46, Arend Van Spriel >>> wrote:

Re: [PATCH] brcmfmac: implement more accurate skb tracking

On 27 September 2016 at 11:24, Arend Van Spriel wrote: > On 26-9-2016 14:38, Rafał Miłecki wrote: >> On 26 September 2016 at 14:13, Rafał Miłecki wrote: >>> On 26 September 2016 at 13:46, Arend Van Spriel >>> wrote: On 26-9-2016 12:23, Rafał Miłecki wrote: > From: Rafał Miłecki >

Re: ima measurement carrying on -mm

Thiago Jung Bauermann writes: > Am Donnerstag, 29 September 2016, 14:02:06 schrieb Andrew Morton: >> On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann > wrote: >> > Hello Andrew, >> > >> > You have in the -mm tree a version of

Re: ima measurement carrying on -mm

Thiago Jung Bauermann writes: > Am Donnerstag, 29 September 2016, 14:02:06 schrieb Andrew Morton: >> On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann > wrote: >> > Hello Andrew, >> > >> > You have in the -mm tree a version of the "kexec handover buffer" and >> > "ima carry measurement

Re: [PATCH v19 04/12] add sysfs document for fpga bridge class

On Wed, Sep 28, 2016 at 11:21 AM, Alan Tull wrote: > Add documentation for new FPGA bridge class's sysfs interface. > > Signed-off-by: Alan Tull Acked-by: Moritz Fischer

Re: [PATCH v19 04/12] add sysfs document for fpga bridge class

On Wed, Sep 28, 2016 at 11:21 AM, Alan Tull wrote: > Add documentation for new FPGA bridge class's sysfs interface. > > Signed-off-by: Alan Tull Acked-by: Moritz Fischer

Re: [PATCH v19 12/12] fpga-manager: Add Socfpga Arria10 support

On Thu, 29 Sep 2016, Moritz Fischer wrote: > Hi Alan, > > On Wed, Sep 28, 2016 at 11:22 AM, Alan Tull > wrote: > > > +static void socfpga_a10_fpga_generate_dclks(struct a10_fpga_priv *priv, > > + u32 count) > > +{ > > +

Re: [PATCH v19 12/12] fpga-manager: Add Socfpga Arria10 support

On Thu, 29 Sep 2016, Moritz Fischer wrote: > Hi Alan, > > On Wed, Sep 28, 2016 at 11:22 AM, Alan Tull > wrote: > > > +static void socfpga_a10_fpga_generate_dclks(struct a10_fpga_priv *priv, > > + u32 count) > > +{ > > + u32 val; > > +

Re: [PATCH V2 3/5] PCI: save and restore bus on parent bus reset

Hi Sinan, On Fri, Sep 16, 2016 at 04:06:32PM -0400, Sinan Kaya wrote: > Device states on the bus are saved and restored for all bus resets except > the one initiated through pci_dev_reset. Filling the hole. > > Signed-off-by: Sinan Kaya > --- > drivers/pci/pci.c | 14

Re: [PATCH V2 3/5] PCI: save and restore bus on parent bus reset

Hi Sinan, On Fri, Sep 16, 2016 at 04:06:32PM -0400, Sinan Kaya wrote: > Device states on the bus are saved and restored for all bus resets except > the one initiated through pci_dev_reset. Filling the hole. > > Signed-off-by: Sinan Kaya > --- > drivers/pci/pci.c | 14 ++ > 1 file

Re: ima measurement carrying on -mm

Andrew Morton writes: > On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann > wrote: > >> Hello Andrew, >> >> You have in the -mm tree a version of the "kexec handover buffer" and "ima >> carry measurement list" patches that were

Re: ima measurement carrying on -mm

Andrew Morton writes: > On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann > wrote: > >> Hello Andrew, >> >> You have in the -mm tree a version of the "kexec handover buffer" and "ima >> carry measurement list" patches that were NAKed by Eric Biederman. I would >> just like to

Re: [PATCH 2/2] Input: add motion-tracking ABS_* bits and docs

On Thu, Sep 29, 2016 at 1:55 AM, wrote: > On 28.09.2016 18:39, Dmitry Torokhov wrote: >> >> On Tue, Sep 27, 2016 at 4:38 PM, Roderick Colenbrander >> wrote: >>> >>> From: Roderick Colenbrander >>> >>> This patch

Re: [PATCH 2/2] Input: add motion-tracking ABS_* bits and docs

On Thu, Sep 29, 2016 at 1:55 AM, wrote: > On 28.09.2016 18:39, Dmitry Torokhov wrote: >> >> On Tue, Sep 27, 2016 at 4:38 PM, Roderick Colenbrander >> wrote: >>> >>> From: Roderick Colenbrander >>> >>> This patch introduces new axes for acceleration and angular velocity. >>> David Herrmann's

Re: [PATHC v2 0/9] ima: carry the measurement list across kexec

Thiago Jung Bauermann writes: > Hello Eric, > > Am Dienstag, 20 September 2016, 11:07:29 schrieb Eric W. Biederman: >> A semi-generic concept called a hand-over buffer seems to be a >> construction of infrustructure for no actual reason that will just >> result in

Re: [PATHC v2 0/9] ima: carry the measurement list across kexec

Thiago Jung Bauermann writes: > Hello Eric, > > Am Dienstag, 20 September 2016, 11:07:29 schrieb Eric W. Biederman: >> A semi-generic concept called a hand-over buffer seems to be a >> construction of infrustructure for no actual reason that will just >> result in confusion. There are lots of

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 14:21 -0700, Joe Perches wrote: > > > It doesn't matter match either way to me. > > Why does this stop you fixing an apparently wrong checkpatch rule, > > crude as parts of it are (ie, uppercase identifier must be a > > constant)? > > It doesn't.  It just doesn't matter much

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 14:21 -0700, Joe Perches wrote: > > > It doesn't matter match either way to me. > > Why does this stop you fixing an apparently wrong checkpatch rule, > > crude as parts of it are (ie, uppercase identifier must be a > > constant)? > > It doesn't.  It just doesn't matter much

Re: [RFC PATCH 0/3] kvm: x86: speedups for APICv

> Another possible optimization: when delivering an IPI, don't write the > vector to PIR, but directly to VIRR. If the guest is not in VMX > non-root mode, then vm entry will take care of the injection; in the > other case, we'll send POSTED_INTR_VECTOR. > It seems that we don't even have to set

Re: [RFC PATCH 0/3] kvm: x86: speedups for APICv

> Another possible optimization: when delivering an IPI, don't write the > vector to PIR, but directly to VIRR. If the guest is not in VMX > non-root mode, then vm entry will take care of the injection; in the > other case, we'll send POSTED_INTR_VECTOR. > It seems that we don't even have to set

Re: [PATCH v5 00/10] ima: carry the measurement list across kexec

Mimi Zohar writes: > The TPM PCRs are only reset on a hard reboot. In order to validate a > TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list > of the running kernel must be saved and then restored on the subsequent > boot, possibly of a

Re: [PATCH v5 00/10] ima: carry the measurement list across kexec

Mimi Zohar writes: > The TPM PCRs are only reset on a hard reboot. In order to validate a > TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list > of the running kernel must be saved and then restored on the subsequent > boot, possibly of a different architecture. > > The

[PATCH 3/3] arm64: dump: Add checking for writable and exectuable pages

Page mappings with full RWX permissions are a security risk. x86 has an option to walk the page tables and dump any bad pages. (See e1a58320a38d ("x86/mm: Warn on W^X mappings")). Add a similar implementation for arm64. Signed-off-by: Laura Abbott ---

[PATCH 3/3] arm64: dump: Add checking for writable and exectuable pages

Page mappings with full RWX permissions are a security risk. x86 has an option to walk the page tables and dump any bad pages. (See e1a58320a38d ("x86/mm: Warn on W^X mappings")). Add a similar implementation for arm64. Signed-off-by: Laura Abbott --- arch/arm64/Kconfig.debug| 28

[PATCH 2/3] arm64: dump: Make the page table dumping seq_file optional

The page table dumping code always assumes it will be dumping to a seq_file to userspace. The dumping code is useful in other situations. Let the seq_file be optional. Signed-off-by: Laura Abbott --- arch/arm64/mm/dump.c | 26 +++--- 1 file changed, 19

[PATCH 2/3] arm64: dump: Make the page table dumping seq_file optional

The page table dumping code always assumes it will be dumping to a seq_file to userspace. The dumping code is useful in other situations. Let the seq_file be optional. Signed-off-by: Laura Abbott --- arch/arm64/mm/dump.c | 26 +++--- 1 file changed, 19 insertions(+), 7

[PATCH 1/3] arm64: dump: Make ptdump debugfs a separate option

ptdump_register currently initializes a set of page table information and registers debugfs. There are uses for the ptdump option without wanting the debugfs options. Split this out to make it a separate option. Signed-off-by: Laura Abbott --- arch/arm64/Kconfig.debug

[PATCH 0/3] WX Checking for arm64

Hi, This is an implementation to check for writable and executable pages on arm64. This is heavily based on the x86 version which uses the existing page table dumping code to do the checking. Some notes: - The W^X checking is important so this option should become defaut eventually. To make

[PATCH 1/3] arm64: dump: Make ptdump debugfs a separate option

ptdump_register currently initializes a set of page table information and registers debugfs. There are uses for the ptdump option without wanting the debugfs options. Split this out to make it a separate option. Signed-off-by: Laura Abbott --- arch/arm64/Kconfig.debug| 6 +-

[PATCH 0/3] WX Checking for arm64

Hi, This is an implementation to check for writable and executable pages on arm64. This is heavily based on the x86 version which uses the existing page table dumping code to do the checking. Some notes: - The W^X checking is important so this option should become defaut eventually. To make

Re: ima measurement carrying on -mm

Am Donnerstag, 29 September 2016, 14:02:06 schrieb Andrew Morton: > On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann wrote: > > Hello Andrew, > > > > You have in the -mm tree a version of the "kexec handover buffer" and > > "ima carry measurement list"

Re: ima measurement carrying on -mm

Am Donnerstag, 29 September 2016, 14:02:06 schrieb Andrew Morton: > On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann wrote: > > Hello Andrew, > > > > You have in the -mm tree a version of the "kexec handover buffer" and > > "ima carry measurement list" patches that were NAKed by Eric

[PATCH] perf config: Add tips about a list option

Add two tips that describe --list option of config sub-command and explain how to choose particular config file location. Signed-off-by: Nambong Ha Cc: Namhyung Kim Cc: Jiri Olsa Cc: Taeung Song ---

[PATCH] perf config: Add tips about a list option

Add two tips that describe --list option of config sub-command and explain how to choose particular config file location. Signed-off-by: Nambong Ha Cc: Namhyung Kim Cc: Jiri Olsa Cc: Taeung Song --- tools/perf/Documentation/tips.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 23:14 +0200, Paul Bolle wrote: > On Thu, 2016-09-29 at 13:56 -0700, Joe Perches wrote: > > It doesn't matter match either way to me. > Why does this stop you fixing an apparently wrong checkpatch rule, > crude as parts of it are (ie, uppercase identifier must be a constant)?

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 23:14 +0200, Paul Bolle wrote: > On Thu, 2016-09-29 at 13:56 -0700, Joe Perches wrote: > > It doesn't matter match either way to me. > Why does this stop you fixing an apparently wrong checkpatch rule, > crude as parts of it are (ie, uppercase identifier must be a constant)?

[RFC 0/4] try to reduce fragmenting fallbacks

Hi Johannes, here's something quick to try or ponder about. However, untested since it's too late here. Based on mmotm-2016-09-27-16-08 plus this fix [1] [1] http://lkml.kernel.org/r/ Vlastimil Babka (4): mm, compaction: change

[RFC 0/4] try to reduce fragmenting fallbacks

Hi Johannes, here's something quick to try or ponder about. However, untested since it's too late here. Based on mmotm-2016-09-27-16-08 plus this fix [1] [1] http://lkml.kernel.org/r/ Vlastimil Babka (4): mm, compaction: change migrate_async_suitable() to suitable_migration_source() mm,

[GIT PULL] libnvdimm fixes for 4.8

Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes ...to receive the following: - (4) fixes for "flush hint" support. Flush hints are addresses advertised by the ACPI 6+ NFIT (NVDIMM Firmware Interface Table) that when written and fenced

[GIT PULL] libnvdimm fixes for 4.8

Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes ...to receive the following: - (4) fixes for "flush hint" support. Flush hints are addresses advertised by the ACPI 6+ NFIT (NVDIMM Firmware Interface Table) that when written and fenced

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 13:56 -0700, Joe Perches wrote: > It doesn't matter match either way to me. > > The case for the unnecessary multiply with <= gcc 4.8 was > removed with: > > commit 91c6a05f72a996bee5133e76374ab3ad7d3b9b72 > Author: Alexey Dobriyan > Date:   Tue Jul 26

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 13:56 -0700, Joe Perches wrote: > It doesn't matter match either way to me. > > The case for the unnecessary multiply with <= gcc 4.8 was > removed with: > > commit 91c6a05f72a996bee5133e76374ab3ad7d3b9b72 > Author: Alexey Dobriyan > Date:   Tue Jul 26 15:22:08 2016 -0700

[RFC 4/4] mm, page_alloc: disallow migratetype fallback in fastpath

The previous patch has adjusted async compaction so that it helps against longterm fragmentation when compacting for a non-MOVABLE high-order allocation. The goal of this patch is to force such allocations go through compaction once before being allowed to fallback to a pageblock of different

[RFC 4/4] mm, page_alloc: disallow migratetype fallback in fastpath

The previous patch has adjusted async compaction so that it helps against longterm fragmentation when compacting for a non-MOVABLE high-order allocation. The goal of this patch is to force such allocations go through compaction once before being allowed to fallback to a pageblock of different

[RFC 2/4] mm, compaction: add migratetype to compact_control

Preparation patch. We are going to need migratetype at lower layers than compact_zone() and compact_finished(). Signed-off-by: Vlastimil Babka --- mm/compaction.c | 15 +++ mm/internal.h | 1 + 2 files changed, 8 insertions(+), 8 deletions(-) diff --git

[RFC 2/4] mm, compaction: add migratetype to compact_control

Preparation patch. We are going to need migratetype at lower layers than compact_zone() and compact_finished(). Signed-off-by: Vlastimil Babka --- mm/compaction.c | 15 +++ mm/internal.h | 1 + 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/mm/compaction.c

Re: [PATCH] x86/entry/64: Fix context tracking state warning when load_gs_index fails

On Mon, Sep 26, 2016 at 4:49 AM, Wanpeng Li wrote: > From: Wanpeng Li > > WARNING: CPU: 0 PID: 3331 at arch/x86/entry/common.c:45 > enter_from_user_mode+0x32/0x50 > CPU: 0 PID: 3331 Comm: ldt_gdt_64 Not tainted 4.8.0-rc7+ #13 > Call Trace: >

Re: ima measurement carrying on -mm

On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann wrote: > Hello Andrew, > > You have in the -mm tree a version of the "kexec handover buffer" and "ima > carry measurement list" patches that were NAKed by Eric Biederman. I would > just like to double-check

Re: ima measurement carrying on -mm

On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann wrote: > Hello Andrew, > > You have in the -mm tree a version of the "kexec handover buffer" and "ima > carry measurement list" patches that were NAKed by Eric Biederman. I would > just like to double-check that there's no risk of that

Re: [PATCH] x86/entry/64: Fix context tracking state warning when load_gs_index fails

On Mon, Sep 26, 2016 at 4:49 AM, Wanpeng Li wrote: > From: Wanpeng Li > > WARNING: CPU: 0 PID: 3331 at arch/x86/entry/common.c:45 > enter_from_user_mode+0x32/0x50 > CPU: 0 PID: 3331 Comm: ldt_gdt_64 Not tainted 4.8.0-rc7+ #13 > Call Trace: > dump_stack+0x99/0xd0 > __warn+0xd1/0xf0 >

[RFC 3/4] mm, compaction: restrict async compaction to matching migratetype

The migrate scanner in async compaction is currently limited to MIGRATE_MOVABLE pageblocks. This is a heuristic intended to reduce latency, based on the assumption that non-MOVABLE pageblocks are unlikely to contain movable pages. However, with the exception of THP's, most high-order allocations

[RFC 3/4] mm, compaction: restrict async compaction to matching migratetype

The migrate scanner in async compaction is currently limited to MIGRATE_MOVABLE pageblocks. This is a heuristic intended to reduce latency, based on the assumption that non-MOVABLE pageblocks are unlikely to contain movable pages. However, with the exception of THP's, most high-order allocations

[RFC 1/4] mm, compaction: change migrate_async_suitable() to suitable_migration_source()

Preparation for making the decisions more complex and depending on compact_control flags. No functional change. Signed-off-by: Vlastimil Babka --- include/linux/mmzone.h | 5 + mm/compaction.c| 19 +++ 2 files changed, 16 insertions(+), 8

[RFC 1/4] mm, compaction: change migrate_async_suitable() to suitable_migration_source()

Preparation for making the decisions more complex and depending on compact_control flags. No functional change. Signed-off-by: Vlastimil Babka --- include/linux/mmzone.h | 5 + mm/compaction.c| 19 +++ 2 files changed, 16 insertions(+), 8 deletions(-) diff --git

Re: [PATCH] mos7840: fix chars_in_buffer() return value

29.09.2016 13:09, Johan Hovold пишет: On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch

Re: [PATCH] mos7840: fix chars_in_buffer() return value

29.09.2016 13:09, Johan Hovold пишет: On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 22:39 +0200, Paul Bolle wrote: > On Thu, 2016-09-29 at 13:24 -0700, Joe Perches wrote: > > On Thu, 2016-09-29 at 21:43 +0200, Paul Bolle wrote: > > > Why doesn't that regex match on "ORIGIN_HASH_SIZE"? > > It does match. > If that regex does match, it being part of a negative

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 22:39 +0200, Paul Bolle wrote: > On Thu, 2016-09-29 at 13:24 -0700, Joe Perches wrote: > > On Thu, 2016-09-29 at 21:43 +0200, Paul Bolle wrote: > > > Why doesn't that regex match on "ORIGIN_HASH_SIZE"? > > It does match. > If that regex does match, it being part of a negative

Re: [PATCH v5 01/14] drivers: iommu: add FWNODE_IOMMU fwnode type

On Thursday, September 29, 2016 03:15:20 PM Lorenzo Pieralisi wrote: > Hi Rafael, > > On Fri, Sep 09, 2016 at 03:23:30PM +0100, Lorenzo Pieralisi wrote: > > On systems booting with a device tree, every struct device is > > associated with a struct device_node, that represents its DT > >

Re: [PATCH v5 01/14] drivers: iommu: add FWNODE_IOMMU fwnode type

On Thursday, September 29, 2016 03:15:20 PM Lorenzo Pieralisi wrote: > Hi Rafael, > > On Fri, Sep 09, 2016 at 03:23:30PM +0100, Lorenzo Pieralisi wrote: > > On systems booting with a device tree, every struct device is > > associated with a struct device_node, that represents its DT > >

Re: Regression in 4.8 - CPU speed set very low

On Thursday, September 29, 2016 08:56:16 AM Srinivas Pandruvada wrote: > On Thu, 2016-09-29 at 14:19 +0200, Rafael J. Wysocki wrote: > > [...] > > > > My laptop was inadvertently put to sleep while I was gone. I forgot > > > to leave a > > > note for my wife and she quieted the noisy cpu fan.

[PATCH v2 1/3] KVM: VMX: remove functions that enable msr intercepts

All intercepts are enabled at the beginning, so they can only be used if we disabled an intercept that we wanted to have enabled. This was done for TMCCT to simplify a loop that disables all x2APIC MSR intercepts, but just keeping TMCCT enabled yields better results. Signed-off-by: Radim Krčmář

Re: Regression in 4.8 - CPU speed set very low

On Thursday, September 29, 2016 08:56:16 AM Srinivas Pandruvada wrote: > On Thu, 2016-09-29 at 14:19 +0200, Rafael J. Wysocki wrote: > > [...] > > > > My laptop was inadvertently put to sleep while I was gone. I forgot > > > to leave a > > > note for my wife and she quieted the noisy cpu fan.

[PATCH v2 1/3] KVM: VMX: remove functions that enable msr intercepts

All intercepts are enabled at the beginning, so they can only be used if we disabled an intercept that we wanted to have enabled. This was done for TMCCT to simplify a loop that disables all x2APIC MSR intercepts, but just keeping TMCCT enabled yields better results. Signed-off-by: Radim Krčmář

ima measurement carrying on -mm

Hello Andrew, You have in the -mm tree a version of the "kexec handover buffer" and "ima carry measurement list" patches that were NAKed by Eric Biederman. I would just like to double-check that there's no risk of that version reaching v4.9. Mimi posted v5 of a merged patch set that addresses

ima measurement carrying on -mm

Hello Andrew, You have in the -mm tree a version of the "kexec handover buffer" and "ima carry measurement list" patches that were NAKed by Eric Biederman. I would just like to double-check that there's no risk of that version reaching v4.9. Mimi posted v5 of a merged patch set that addresses

[PATCH v2 3/3] KVM: VMX: refactor setup of global page-sized bitmaps

We've had 10 page-sized bitmaps that were being allocated and freed one by one when we could just use a cycle. Signed-off-by: Radim Krčmář --- arch/x86/kvm/vmx.c | 120 + 1 file changed, 38 insertions(+), 82 deletions(-)

[PATCH v2 3/3] KVM: VMX: refactor setup of global page-sized bitmaps

We've had 10 page-sized bitmaps that were being allocated and freed one by one when we could just use a cycle. Signed-off-by: Radim Krčmář --- arch/x86/kvm/vmx.c | 120 + 1 file changed, 38 insertions(+), 82 deletions(-) diff --git

Re: linux-next: build failure after merge of the tip tree

On Thursday, September 29, 2016 03:54:24 PM Chen, Yu C wrote: > Hi, > > > -Original Message- > > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > > Sent: Thursday, September 29, 2016 8:25 PM > > To: Stephen Rothwell > > Cc: Thomas Gleixner; Ingo Molnar; H. Peter Anvin; Peter

[PATCH] edac: use Intel Model Macros instead of open-coding them

From: Dave Hansen We now have symbolic names for a bunch of Intel cpu modes via asm/intel-family.h. The original conversion missed the edac drivers. Convert them. Signed-off-by: Dave Hansen Cc: Mauro Carvalho Chehab Cc: Doug

[PATCH v2 2/3] KVM: VMX: join functions that disable x2apic msr intercepts

vmx_disable_intercept_msr_read_x2apic() and vmx_disable_intercept_msr_write_x2apic() differed only in the type. Pass the type to a new function. Signed-off-by: Radim Krčmář --- arch/x86/kvm/vmx.c | 36 ++-- 1 file changed, 10 insertions(+), 26

[PATCH v2 2/3] KVM: VMX: join functions that disable x2apic msr intercepts

vmx_disable_intercept_msr_read_x2apic() and vmx_disable_intercept_msr_write_x2apic() differed only in the type. Pass the type to a new function. Signed-off-by: Radim Krčmář --- arch/x86/kvm/vmx.c | 36 ++-- 1 file changed, 10 insertions(+), 26 deletions(-) diff

Re: linux-next: build failure after merge of the tip tree

On Thursday, September 29, 2016 03:54:24 PM Chen, Yu C wrote: > Hi, > > > -Original Message- > > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > > Sent: Thursday, September 29, 2016 8:25 PM > > To: Stephen Rothwell > > Cc: Thomas Gleixner; Ingo Molnar; H. Peter Anvin; Peter

[PATCH] edac: use Intel Model Macros instead of open-coding them

From: Dave Hansen We now have symbolic names for a bunch of Intel cpu modes via asm/intel-family.h. The original conversion missed the edac drivers. Convert them. Signed-off-by: Dave Hansen Cc: Mauro Carvalho Chehab Cc: Doug Thompson Cc: Borislav Petkov Cc: linux-e...@vger.kernel.org Cc:

[PATCH v2 0/3] KVM: VMX: refactor global page-sized bitmaps

v1: http://www.spinics.net/lists/kvm/msg138118.html v2: - split into multiple patches [Paolo] - add macros for bitmap definitions [Paolo] Radim Krčmář (3): KVM: VMX: remove functions that enable msr intercepts KVM: VMX: join functions that disable x2apic msr intercepts KVM: VMX: refactor

[PATCH v2 0/3] KVM: VMX: refactor global page-sized bitmaps

v1: http://www.spinics.net/lists/kvm/msg138118.html v2: - split into multiple patches [Paolo] - add macros for bitmap definitions [Paolo] Radim Krčmář (3): KVM: VMX: remove functions that enable msr intercepts KVM: VMX: join functions that disable x2apic msr intercepts KVM: VMX: refactor

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 13:24 -0700, Joe Perches wrote: > On Thu, 2016-09-29 at 21:43 +0200, Paul Bolle wrote: > > Why doesn't that regex match on "ORIGIN_HASH_SIZE"? > > It does match. If that regex does match, it being part of a negative test, the specific checkpatch rule should be silent,

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 13:24 -0700, Joe Perches wrote: > On Thu, 2016-09-29 at 21:43 +0200, Paul Bolle wrote: > > Why doesn't that regex match on "ORIGIN_HASH_SIZE"? > > It does match. If that regex does match, it being part of a negative test, the specific checkpatch rule should be silent,

Re: [PATCH locking/Documentation 1/2] Add note of release-acquire store vulnerability

On Thu, Sep 29, 2016 at 03:36:38PM -0400, Alan Stern wrote: > On Thu, 29 Sep 2016, Paul E. McKenney wrote: > > > On Thu, Sep 29, 2016 at 08:44:39PM +0200, Peter Zijlstra wrote: > > > > How about something like so on PPC? > > > > > > P0(int *x, int *y) > > > { > > > WRITE_ONCE(*x, 1); > > >

Re: [PATCH locking/Documentation 1/2] Add note of release-acquire store vulnerability

On Thu, Sep 29, 2016 at 03:36:38PM -0400, Alan Stern wrote: > On Thu, 29 Sep 2016, Paul E. McKenney wrote: > > > On Thu, Sep 29, 2016 at 08:44:39PM +0200, Peter Zijlstra wrote: > > > > How about something like so on PPC? > > > > > > P0(int *x, int *y) > > > { > > > WRITE_ONCE(*x, 1); > > >

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 21:43 +0200, Paul Bolle wrote: > On Thu, 2016-09-29 at 08:01 -0700, Joe Perches wrote: > > $Constant there is any number and the match regex is > > any upper case variable. > Why doesn't that regex match on "ORIGIN_HASH_SIZE"? It does match. Did you see my earlier email? $

Re: [PATCH 01/10] dm snapshot: Use kmalloc_array() in init_origin_hash()

On Thu, 2016-09-29 at 21:43 +0200, Paul Bolle wrote: > On Thu, 2016-09-29 at 08:01 -0700, Joe Perches wrote: > > $Constant there is any number and the match regex is > > any upper case variable. > Why doesn't that regex match on "ORIGIN_HASH_SIZE"? It does match. Did you see my earlier email? $

<    1   2   3   4   5   6   7   8   9   10   >