Fix checkpatch.pl error:
ERROR: space prohibited before open square bracket '['.
Signed-off-by: Arvind Yadav
---
net/netfilter/ipvs/ip_vs_proto_tcp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/netfilter/ipvs/ip_vs_proto_tcp.c
b/net/netfilter/ipvs/ip_vs_proto_tcp
There maybe still threads waiting on event_wqh at the time the userfault
file descriptor is closed. Flush the events wait-queue to prevent waiting
threads from hanging.
Cc: sta...@vger.kernel.org
Fixes: 9cd75c3cd4c3d ("userfaultfd: non-cooperative: add ability to report
non-PF events from uffd des
On Thu, Jul 27, 2017 at 10:18:40PM -0400, Prakash Sangappa wrote:
> This patch adds tests for UFFD_FEATURE_SIGBUS feature. The
> tests will verify signal delivery instead of userfault events.
> Also, test use of UFFDIO_COPY to allocate memory and retry
> accessing monitored area after signal delive
On 07/30/2017 12:55 AM, David Lang wrote:
> You are thinking of Trademarks, they must be defended or you loose them.
> Contracts and Licenses do not need to be defended at every chance or risk
> loosing them.
No, not always, it can apply in plain contract as well. The defenses that
could be later
-to-__write_data_page-for-dentry-pages/20170730-141454
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
dev-test
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
On 07/29, Yunlong Song wrote:
> f2fs_balance_fs of dentry pages is skipped in __write_data_page due to
> deadlock
> of gc_mutex in write_checkpoint flow. This patch enables f2fs_balance_fs for
> normal dentry page writeback to ensure there are always enough free segments.
Sorry, by the way, why d
From: Wanpeng Li
[ cut here ]
WARNING: CPU: 5 PID: 2288 at arch/x86/kvm/vmx.c:11124
nested_vmx_vmexit+0xd64/0xd70 [kvm_intel]
CPU: 5 PID: 2288 Comm: qemu-system-x86 Not tainted 4.13.0-rc2+ #7
RIP: 0010:nested_vmx_vmexit+0xd64/0xd70 [kvm_intel]
Call Trace:
vmx_check_n
Hi Chao,
When I add this patch, xfstests/fsstress are giving some weird kernel hang
or panic now. Without only this patch, I can't see any problem. Can you review
this patch one more time in terms of memory and lock usages.
I'm doing xfstests without quota though.
Thanks,
On 07/26, Chao Yu wrot
On 07/29, Chao Yu wrote:
> Hi Jaegeuk,
>
> Could you take time to have a look at this? Is this change reasonable?
>
> Thanks,
>
> On 2017/7/26 22:33, Chao Yu wrote:
> > From: Chao Yu
> >
> > Previously, in order to avoid losing important inode metadata after
> > checkpoint & sudden power-off,
Hi Daniel,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0a07b238e5f488b459b6113a62e06b6aab017f71
commit: dc11bae78529526605c5c45c369c9512fd012093 clocksource/drivers: Add
timer-of common init routine
date: 7 we
when SMP VM start, AP may lost INIT because of receiving INIT between
kvm_vcpu_ioctl_x86_get/set_vcpu_events.
vcpu 0 vcpu 1
kvm_vcpu_ioctl_x86_get_vcpu_events
events->smi.latched_init=0
send INIT
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Arvind Yadav (29):
[PATCH 01/29] scsi: qla1280: constify pci_device_id.
[PATCH 02/29] scsi: qedi: constify pci_devic
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/qla4xxx/ql4_os.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/mvsas/mv_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/3w-9xxx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/am53c974.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/qla1280.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/dpt_i2o.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/arcmsr/arcmsr_hba.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/pm8001/pm8001_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/ipr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/qedi/qedi_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/megaraid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/esas2r/esas2r_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/sym53c8xx_2/sym_glue.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/3w-sas.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/dmx3191d.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/snic/snic_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/cxlflash/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/qla2xxx/qla_os.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/hptiop.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/fdomain.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/pmcraid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/nsp32.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/a100u2w.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/megaraid/megaraid_sas_base.c | 2 +-
1 file changed, 1 insertion(+), 1 de
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/atp870u.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/3w-.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/stex.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/advansys.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/scsi/fnic/fnic_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
Fix for a regression caused by the conversion of x86 to the generic hotplug
code. Instead of doing a plain single line revert, this adds a pile of
Linus,
please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
A couple of fixes for performance counters and kprobes:
- A series of small patches which make the uncore performance counters on
Skylake
Linus,
please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
Two patches addressing build warnings caused by inconsistent kernel doc
comments.
Thanks,
tglx
-->
Jonathan Corbet (
Thomas,
on Linus' most recent kernel (v4.12-rc2, git head 0a07b238e5f48), I see the
following message on my Dell XPS13 when resuming from sleep. MEI is, AFAIK,
not being used on this system:
[ 192.940537] Restarting tasks ...
[ 192.940610] PGI is not set
[ 192.940619] [ cut here ]
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
A small set of x86 fixes:
- Prevent the kernel from using the EFI reboot method when EFI is
disabled.
- Two patches addressing clang issu
> -Original Message-
> From: Dominik Brodowski [mailto:li...@dominikbrodowski.net]
> Sent: Sunday, July 30, 2017 11:59
> To: Winkler, Tomas
> Cc: Usyskin, Alexander ; linux-
> ker...@vger.kernel.org
> Subject: MEI-related WARN_ON() triggered during resume-from-sleep on
> v4.12-rc2+
>
>
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> Test results at the end of this message, as usual.
>
> The following changes since commit ee438ec8f33c5af0d4a4ffb935c5b9272e8c2680:
>
> Merge tag 'perf-core-for-mingo-4.14-20170725' of
> git
Change this:
Warning: arch/x86/include/asm/disabled-features.h differs from kernel
Warning: arch/x86/include/asm/cpufeatures.h differs from kernel
Warning: arch/powerpc/include/uapi/asm/kvm.h differs from kernel
Warning: arch/s390/include/uapi/asm/kvm.h differs from kernel
to:
Warning:
Commit-ID: de63403bfd14ae8d613f30c9a0d415581b4cb37e
Gitweb: http://git.kernel.org/tip/de63403bfd14ae8d613f30c9a0d415581b4cb37e
Author: Jiri Olsa
AuthorDate: Wed, 26 Jul 2017 14:02:04 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 26 Jul 2017 14:20:28 -0300
perf tools: Add p
Commit-ID: f7794d525447f1e4e4b2228dd29dba084005e6bf
Gitweb: http://git.kernel.org/tip/f7794d525447f1e4e4b2228dd29dba084005e6bf
Author: Jiri Olsa
AuthorDate: Wed, 26 Jul 2017 14:02:05 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 26 Jul 2017 14:21:59 -0300
perf evsel: Add r
Commit-ID: 82bf311e15d22e2fa45423b1fb4a21cf925381fe
Gitweb: http://git.kernel.org/tip/82bf311e15d22e2fa45423b1fb4a21cf925381fe
Author: Jiri Olsa
AuthorDate: Wed, 26 Jul 2017 14:02:06 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 26 Jul 2017 14:25:44 -0300
perf stat: Use gr
Commit-ID: ce9ee4a2de20062a97ad50ecc11ebda7e7618fd1
Gitweb: http://git.kernel.org/tip/ce9ee4a2de20062a97ad50ecc11ebda7e7618fd1
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 26 Jul 2017 17:16:46 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 26 Jul 2017 17:16:46 -0300
pe
Commit-ID: c6c13be76c1fc8a3169dbd29cd1d42af1d64773f
Gitweb: http://git.kernel.org/tip/c6c13be76c1fc8a3169dbd29cd1d42af1d64773f
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 26 Jul 2017 16:52:25 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 26 Jul 2017 16:52:25 -0300
pe
Commit-ID: 48cc33085253d607706e68a67ac98fe2a6abdd3d
Gitweb: http://git.kernel.org/tip/48cc33085253d607706e68a67ac98fe2a6abdd3d
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 28 Jul 2017 12:49:02 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Jul 2017 12:53:05 -0300
pe
Commit-ID: bb79a232b0881ce47f921a53f40612a9f9996482
Gitweb: http://git.kernel.org/tip/bb79a232b0881ce47f921a53f40612a9f9996482
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 27 Jul 2017 11:24:59 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Jul 2017 12:53:06 -0300
pe
From: Wanpeng Li
When SMP VM start, AP may lost INIT because of receiving INIT between
kvm_vcpu_ioctl_x86_get/set_vcpu_events.
vcpu 0 vcpu 1
kvm_vcpu_ioctl_x86_get_vcpu_events
events->smi.l
Commit-ID: f67d395c6e3895c3c8c67c8f7523f6a94d61a82d
Gitweb: http://git.kernel.org/tip/f67d395c6e3895c3c8c67c8f7523f6a94d61a82d
Author: Taeung Song
AuthorDate: Fri, 28 Jul 2017 12:04:32 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Jul 2017 12:53:08 -0300
perf annotate T
Commit-ID: 29dc267f270a4ad5ae1341e7fdc8539ac7dc907a
Gitweb: http://git.kernel.org/tip/29dc267f270a4ad5ae1341e7fdc8539ac7dc907a
Author: Taeung Song
AuthorDate: Thu, 27 Jul 2017 11:33:20 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Jul 2017 12:53:06 -0300
perf annotate T
Commit-ID: 3861c4a49bea432c57d6e7cbd89c8b71ed4445b7
Gitweb: http://git.kernel.org/tip/3861c4a49bea432c57d6e7cbd89c8b71ed4445b7
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 28 Jul 2017 13:19:32 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Jul 2017 13:19:32 -0300
pe
Commit-ID: bc1e5d60cebb711ca3783a87a969d18db376d357
Gitweb: http://git.kernel.org/tip/bc1e5d60cebb711ca3783a87a969d18db376d357
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 27 Jul 2017 12:05:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Jul 2017 12:53:07 -0300
pe
2017-07-31 0:24 GMT+08:00 Peng Hao :
> when SMP VM start, AP may lost INIT because of receiving INIT between
> kvm_vcpu_ioctl_x86_get/set_vcpu_events.
>
>vcpu 0 vcpu 1
>kvm_vcpu_ioctl_x86_get_vcpu_events
>
Commit-ID: f9f6f2a90343c5be3294d1336da055a99c28897d
Gitweb: http://git.kernel.org/tip/f9f6f2a90343c5be3294d1336da055a99c28897d
Author: Geneviève Bastien
AuthorDate: Thu, 27 Jul 2017 14:12:04 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Jul 2017 16:26:06 -0300
perf data
Commit-ID: a3073c8e590d7baa5a6cb01438cb945c92bfcd91
Gitweb: http://git.kernel.org/tip/a3073c8e590d7baa5a6cb01438cb945c92bfcd91
Author: Geneviève Bastien
AuthorDate: Thu, 27 Jul 2017 14:12:03 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Jul 2017 16:25:07 -0300
perf data
Commit-ID: 6b7007af728df7258bb60ed73099be3b59b3030e
Gitweb: http://git.kernel.org/tip/6b7007af728df7258bb60ed73099be3b59b3030e
Author: Geneviève Bastien
AuthorDate: Thu, 27 Jul 2017 14:12:05 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Jul 2017 16:30:45 -0300
perf data
On Sat 2017-07-29 22:55:22, David Lang wrote:
> On Sat, 29 Jul 2017, Paul G. Allen wrote:
>
> >>It's not even clear that there is infringement. The GPL merely
> >>requires that people who have been distributed copies of GPL'ed code
> >>must not be restricted from further redistribution of the cod
Hi!
> Screens that don't have a black border around the active area will have
> ugly black bars for the margin when the text background color is not black.
> This is especially noticeable on an LCD screen (not the backlit kind) when
> the terminal colors are inverted.
Are you sure? It is quite co
Hi!
On Sat 2017-07-29 17:20:52, Paul G. Allen wrote:
> > It's not even clear that there is infringement. The GPL merely
> > requires that people who have been distributed copies of GPL'ed code
> > must not be restricted from further redistribution of the code. It
> > does not require that that s
In this patch we changed the header checks:
perf build: Clarify header version warning message
Unfortunately the header checks were copied to various places and thus the
message got
out of sync. Fix some of them here.
Note that there's still old, misleading messages remaining in:
tools/obj
Sync up (copy) the following v4.13 kernel headers to the tooling headers:
arch/arm/include/uapi/asm/kvm.h:
arch/arm64/include/uapi/asm/kvm.h:
arch/powerpc/include/uapi/asm/kvm.h:
arch/s390/include/uapi/asm/kvm.h:
- KVM ABI extensions, which do not affect perf tooling
arch/x86/includ
>> Have you considered using ip_route_output_key() for IPv4 or
>> ip6_route_output() for IPv6 to decide if this is a loopback?
>> For reference you can check the flow starting at rdma_resolve_ip()
>>
>
> Hi Moni,
>
> Yes, I had looked into it, but I haven't seen how I can find
> out if the destin
On Fri, Jul 28, 2017 at 11:26:46PM +0100, Salil Mehta wrote:
> This patch adds the support of the HNAE3 (Hisilicon Network
> Acceleration Engine 3) framework support to the HNS3 driver.
>
> Framework facilitates clients like ENET(HNS3 Ethernet Driver), RoCE
> and user-space Ethernet drivers (like O
Hi,
I saw that netif_err is more common in code, is it preferred on netdev_err?
What is the preferred style, netif_ or netdev_?
Best Regards,
Aviad
On 7/27/2017 1:33 AM, Andrew Lunn wrote:
> On Wed, Jul 19, 2017 at 03:36:28PM +0300, Aviad Krawczyk wrote:
>> Hi Joe,
>>
>> I tried to be consistent
Hi Jaegeuk,
On 2017/7/30 15:35, Jaegeuk Kim wrote:
> Hi Chao,
>
> When I add this patch, xfstests/fsstress are giving some weird kernel hang
> or panic now. Without only this patch, I can't see any problem. Can you review
> this patch one more time in terms of memory and lock usages.
Recently, i
On 2017-07-29 20:07, Theodore Ts'o wrote:
It's not even clear that there is infringement. The GPL merely...
Yes it is.
Here's a posting from before that explains it:
GPL v2
Section 6 states simply
"You may not impose any further restrictions on the recipients' exercise
of
Kees, Manfred,
on Linus' most recent kernel (v4.13-rc2+, git head 0a07b238e5f48), lsipc(1)
works as expected in initramfs and before gnome starts up. Afterwards,
running lsipc as user(!) results in the following general protection fault
and a quite unusable system:
[ 183.018415] general protecti
Hi,
Here are the series of patches to fix kprobes not
to optimize on the functions in irqentry text ([4/4]).
To check the irqentry text always, [3/4] makes irqentry
text section unconditional.
This involves some other cleanups on h8300, xtensa,
because those sources declare section start/end symb
Hi Jaegeuk,
On 2017/7/30 15:31, Jaegeuk Kim wrote:
> On 07/29, Yunlong Song wrote:
>> f2fs_balance_fs of dentry pages is skipped in __write_data_page due to
>> deadlock
>> of gc_mutex in write_checkpoint flow. This patch enables f2fs_balance_fs for
>> normal dentry page writeback to ensure there
Mark _stext and _etext as character arrays instead of
single character, as same as include/asm-generic/sections.h
does.
Signed-off-by: Masami Hiramatsu
---
arch/h8300/include/asm/traps.h |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/h8300/include/asm/traps.h b
Mark _stext and _end as character arrays instead of single
character, as same as include/asm-generic/sections.h does.
Signed-off-by: Masami Hiramatsu
---
arch/xtensa/kernel/setup.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/xtensa/kernel/setup.c b/arch/xten
Or as Bruce Perens put it (and yes Bruce Perens is correct, and yes I am
an attorney)
Bruce Perens wrote:
"Currently, Grsecurity is a commercial product and is distributed only
to paying customers. Under their Stable Patch Access Agreement,
customers are warned that if they r
Generate irqentry and softirqentry text sections without
any configs. This will add above extra sections, but
no performace impact.
Signed-off-by: Masami Hiramatsu
Suggested-by: Ingo Molnar
---
arch/arm/include/asm/traps.h |7 ---
arch/arm64/include/asm/traps.h|7 ---
a
Since the kernel segment registers are not prepared at the
entry of irq-entry code, if a kprobe on such code is
jump-optimized, accessing per-cpu variables may cause
kernel panic.
However, if the kprobe is not optimized, it kicks int3
exception and set segment registers correctly.
This checks prob
First of all, give some proof of your accusation.
Second of all, prove the relevance of such.
Third of all: identity politics is off-topic in a discussion on
copyright.
Is it not you, thus, who is trolling and attempting to derail the
conversation?
On 2017-07-29 16:49, Adam Borowski wrote
Thank you. When earlier I brought up latches when I started
brainstorming the defenses GRSecurity might raise, Bruce Perens quickly
dismissed me as a "fool".
https://lists.debian.org/debian-user/2017/07/msg00830.html
OK, I apologize to all who were involved in this conversation. I will
block
Hi Robin,
On 27/07/2017 16:54, Robin Murphy wrote:
> If the IOMMU driver advertises 'real' reserved regions for MSIs, but
> still includes the software-managed region as well, we are currently
> blind to the former and will configure the IOMMU domain to map MSIs into
> the latter, which is unlikely
Hi Robin,
On 27/07/2017 16:54, Robin Murphy wrote:
> For ARM-based systems with a GICv3 ITS to provide interrupt isolation,
> but hardware limitations which are worked around by having MSIs bypass
> SMMU translation (e.g. HiSilicon Hip06/Hip07), VFIO neglects to check
> for the IRQ_DOMAIN_FLAG_MSI_
Commit-ID: 57bd1905b228f2a14d7506b0302f69f425131e57
Gitweb: http://git.kernel.org/tip/57bd1905b228f2a14d7506b0302f69f425131e57
Author: Tom Lendacky
AuthorDate: Fri, 28 Jul 2017 11:01:17 -0500
Committer: Ingo Molnar
CommitDate: Sun, 30 Jul 2017 12:09:12 +0200
acpi, x86/mm: Remove encryp
Commit-ID: 4e237903f95db585b976e7311de2bfdaaf0f6e31
Gitweb: http://git.kernel.org/tip/4e237903f95db585b976e7311de2bfdaaf0f6e31
Author: Tom Lendacky
AuthorDate: Fri, 28 Jul 2017 11:01:16 -0500
Committer: Ingo Molnar
CommitDate: Sun, 30 Jul 2017 12:09:12 +0200
x86/mm, kexec: Fix memory c
Hi!
On Tue 2017-07-18 21:51:33, Theodore Ts'o wrote:
> On Tue, Jul 18, 2017 at 09:00:10PM -0400, Sandy Harris wrote:
> > The only really good solution I know of is to find a way to provide a
> > chunk of randomness early in the boot process. John Denker has a good
> > discussion of doing this by m
This fixes missing mfd_remove_devices() call when unload the module.
Signed-off-by: Axel Lin
---
drivers/mfd/lp87565.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/mfd/lp87565.c b/drivers/mfd/lp87565.c
index 340ad0c..32d2a07 100644
--- a/drivers/mfd/lp87565.
On Fri, 02 Jun 2017 09:18:14 +0800
Jia-Ju Bai wrote:
> On 06/02/2017 12:11 AM, Jonathan Corbet wrote:
> > On Thu, 01 Jun 2017 09:05:07 +0800
> > Jia-Ju Bai wrote:
> >
> >> I admit my patches are not well tested, and they may not well fix the bugs.
> >> I am looking forward to opinions and sugg
2017-07-30 18:42 GMT+08:00 :
>> 2017-07-31 0:24 GMT+08:00 Peng Hao :
>
>> > when SMP VM start, AP may lost INIT because of receiving INIT between
>> > kvm_vcpu_ioctl_x86_get/set_vcpu_events.
>> >
>> >vcpu 0 vcpu 1
>> >kvm_vcpu_ioctl_x
The downstream RTD1195 and apparently RTD1295 trees have a modified 8250
serial driver that acknowledges its interrupts using the second reg area,
which is an irq mux.
Drop these unused second reg entries for the UART nodes.
Fixes: 72a7786c0a0d ("ARM64: dts: Add Realtek RTD1295 and Zidoo X9S")
Si
This removes the SoC-specific dependencies on the platform drivers,
as well as SoC-specific selections of platform drivers for the
machine drivers. The rationale behind this change is that the
dependencies are not actual build dependencies but run-time ones.
The previously listed SoCs were also in
This selects both the Tegra20 and Tegra30 I2S interfaces (that were
previously auto-selected by Kconfig but are not anymore) to
multi_v7_defconfig, as modules.
Signed-off-by: Paul Kocialkowski
---
arch/arm/configs/multi_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/
This selects both the Tegra20 and Tegra30 I2S interfaces (that were
previously auto-selected by Kconfig but are not anymore) to
tegra_defconfig, as built-ins.
Signed-off-by: Paul Kocialkowski
---
arch/arm/configs/tegra_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/conf
2017-07-30 19:33 GMT+08:00 :
>
>
>
>
>>2017-07-30 18:42 GMT+08:00 :
>
2017-07-31 0:24 GMT+08:00 Peng Hao :
>>>
> when SMP VM start, AP may lost INIT because of receiving INIT between
> kvm_vcpu_ioctl_x86_get/set_vcpu_events.
>
>vcpu 0 vcpu
On Tue, Jul 18, 2017 at 11:58:36AM -0500, Jintack Lim wrote:
> From: Christoffer Dall
>
> Add functions setting up and restoring the guest's context on each entry
> and exit. These functions will come in handy when we want to use
> different context for normal EL0/EL1 and virtual EL2 execution.
>
On 2017-07-28 23:25, Stephen Boyd wrote:
On 07/28, Abhishek Sahu wrote:
On 2017-07-28 00:14, Stephen Boyd wrote:
>
>It looks like the two UBI clks that messed this up don't have an MN
>counter, so instead of doing this maddness, just add a flag like
I have given example for one of the RCG. IPQ
1 - 100 of 335 matches
Mail list logo
