Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Thursday, October 4, 2018 6:18 PM, Kees Cook wrote:
>
> I don't want to overload "security=", but we can if we want. It would
> be as above, but a trailing comma would be needed to trigger the
> "ordering" behavior. e.g.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Thursday, October 4, 2018 6:18 PM, Kees Cook wrote:
>
> I don't want to overload "security=", but we can if we want. It would
> be as above, but a trailing comma would be needed to trigger the
> "ordering" behavior. e.g.
On 04/10/18 17:43, Lorenzo Pieralisi wrote:
On Fri, Sep 21, 2018 at 04:08:01PM +0100, Shameer Kolothum wrote:
From: Neil Leeder
Add support for the SMMU Performance Monitor Counter Group
information from ACPI. This is in preparation for its use
in the SMMUv3 PMU driver.
Signed-off-by: Neil
On 04/10/18 17:43, Lorenzo Pieralisi wrote:
On Fri, Sep 21, 2018 at 04:08:01PM +0100, Shameer Kolothum wrote:
From: Neil Leeder
Add support for the SMMU Performance Monitor Counter Group
information from ACPI. This is in preparation for its use
in the SMMUv3 PMU driver.
Signed-off-by: Neil
Dear Respectfully,
I write to seek for your indulgence on a US$9.7 Million deal, I am an Insurance
agent by profession, this funds was supposed be paid to my late client as Life
Assurance policy, he died interstate without any next of kin in case of
eventuality and now the paying institution
Dear Respectfully,
I write to seek for your indulgence on a US$9.7 Million deal, I am an Insurance
agent by profession, this funds was supposed be paid to my late client as Life
Assurance policy, he died interstate without any next of kin in case of
eventuality and now the paying institution
On Thu, Sep 27, 2018 at 10:13:05AM -0700, Matthias Kaehlcke wrote:
> On Thu, Sep 27, 2018 at 12:47:06PM -0400, Sinan Kaya wrote:
> > On 9/27/2018 12:41 PM, Balakrishna Godavarthi wrote:
> > > void bt_sock_reclassify_lock(struct sock *sk, int proto);
> > >
> > > +int device_get_bd_address(struct
On Friday 05 October 2018 01:21:00 chenchacha wrote:
> Signed-off-by: chenchacha
> ---
> fs/fat/file.c | 22 ++
> include/uapi/linux/msdos_fs.h | 1 +
> 2 files changed, 23 insertions(+)
>
> diff --git a/fs/fat/file.c b/fs/fat/file.c
> index
On Thu, Sep 27, 2018 at 10:13:05AM -0700, Matthias Kaehlcke wrote:
> On Thu, Sep 27, 2018 at 12:47:06PM -0400, Sinan Kaya wrote:
> > On 9/27/2018 12:41 PM, Balakrishna Godavarthi wrote:
> > > void bt_sock_reclassify_lock(struct sock *sk, int proto);
> > >
> > > +int device_get_bd_address(struct
On Friday 05 October 2018 01:21:00 chenchacha wrote:
> Signed-off-by: chenchacha
> ---
> fs/fat/file.c | 22 ++
> include/uapi/linux/msdos_fs.h | 1 +
> 2 files changed, 23 insertions(+)
>
> diff --git a/fs/fat/file.c b/fs/fat/file.c
> index
On Fri, Oct 05, 2018 at 02:26:11AM +1000, Aleksa Sarai wrote:
> On 2018-09-29, Jann Horn wrote:
> > You attempt to open "C/../../etc/passwd" under the root "/A/B".
> > Something else concurrently moves /A/B/C to /A/C. This can result in
> > the following:
> >
> > 1. You start the path walk and
On Fri, Oct 05, 2018 at 02:26:11AM +1000, Aleksa Sarai wrote:
> On 2018-09-29, Jann Horn wrote:
> > You attempt to open "C/../../etc/passwd" under the root "/A/B".
> > Something else concurrently moves /A/B/C to /A/C. This can result in
> > the following:
> >
> > 1. You start the path walk and
This patch add fat ioctl command FAT_IOCTL_GET_VOLUME_LABEL.
We can get the volume label with this command:
ioctl(fd, FAT_IOCTL_GET_VOLUME_LABEL, _label);
FAT volume label (volume name) is exactly same stored in boot sector and root
directory. And this patch read label only from the
On Friday 05 October 2018 01:21:01 chenchacha wrote:
> Signed-off-by: chenchacha
> ---
> fs/fat/dir.c | 13 +
> fs/fat/fat.h | 2 ++
> 2 files changed, 15 insertions(+)
>
> diff --git a/fs/fat/dir.c b/fs/fat/dir.c
> index 7f5f3699fc6c..4fdcc1200f2b 100644
> --- a/fs/fat/dir.c
> +++
This patch add fat ioctl command FAT_IOCTL_GET_VOLUME_LABEL.
We can get the volume label with this command:
ioctl(fd, FAT_IOCTL_GET_VOLUME_LABEL, _label);
FAT volume label (volume name) is exactly same stored in boot sector and root
directory. And this patch read label only from the
On Friday 05 October 2018 01:21:01 chenchacha wrote:
> Signed-off-by: chenchacha
> ---
> fs/fat/dir.c | 13 +
> fs/fat/fat.h | 2 ++
> 2 files changed, 15 insertions(+)
>
> diff --git a/fs/fat/dir.c b/fs/fat/dir.c
> index 7f5f3699fc6c..4fdcc1200f2b 100644
> --- a/fs/fat/dir.c
> +++
Signed-off-by: chenchacha
---
fs/fat/dir.c | 13 +
fs/fat/fat.h | 2 ++
2 files changed, 15 insertions(+)
diff --git a/fs/fat/dir.c b/fs/fat/dir.c
index 7f5f3699fc6c..4fdcc1200f2b 100644
--- a/fs/fat/dir.c
+++ b/fs/fat/dir.c
@@ -881,6 +881,19 @@ static int
Signed-off-by: chenchacha
---
fs/fat/dir.c | 13 +
fs/fat/fat.h | 2 ++
2 files changed, 15 insertions(+)
diff --git a/fs/fat/dir.c b/fs/fat/dir.c
index 7f5f3699fc6c..4fdcc1200f2b 100644
--- a/fs/fat/dir.c
+++ b/fs/fat/dir.c
@@ -881,6 +881,19 @@ static int
On Tue, Oct 02, 2018 at 02:18:33AM +1000, Aleksa Sarai wrote:
> On 2018-10-01, Jann Horn wrote:
> > > If this is an issue for AT_THIS_ROOT, I believe this might also be an
> > > issue for AT_BENEATH since they are effectively both using the same
> > > nd->root trick (so you could similarly trick
On Tue, Oct 02, 2018 at 02:18:33AM +1000, Aleksa Sarai wrote:
> On 2018-10-01, Jann Horn wrote:
> > > If this is an issue for AT_THIS_ROOT, I believe this might also be an
> > > issue for AT_BENEATH since they are effectively both using the same
> > > nd->root trick (so you could similarly trick
On Friday 05 October 2018 01:20:59 chenchacha wrote:
> This patch add fat ioctl command FAT_IOCTL_GET_VOLUME_LABEL.
>
> We can get the volume label with this command:
>
> ioctl(fd, FAT_IOCTL_GET_VOLUME_LABEL, _label);
Hi! What is purpose of having such functionality in kernel? Userspace
On Friday 05 October 2018 01:20:59 chenchacha wrote:
> This patch add fat ioctl command FAT_IOCTL_GET_VOLUME_LABEL.
>
> We can get the volume label with this command:
>
> ioctl(fd, FAT_IOCTL_GET_VOLUME_LABEL, _label);
Hi! What is purpose of having such functionality in kernel? Userspace
- irq-csky-apb-intc is a simple SOC interrupt controller which is
used in a lot of C-SKY CPU SOC products.
Changelog:
- pass checkpatch.pl.
- use "bool ret" instead of "int ret"
- add support-pulse-signal in irq-csky-apb-intc.c
- change name with upstream feed-back
- add INTC_IFR to
- Dt-bindings doc about C-SKY apb bus interrupt controller.
Signed-off-by: Guo Ren
Reviewed-by: Rob Herring
---
.../interrupt-controller/csky,apb-intc.txt | 62 ++
1 file changed, 62 insertions(+)
create mode 100644
Dt-bindings doc about C-SKY Multi-processors interrupt controller.
Changelog:
- Should be: '#interrupt-cells' not 'interrupt-cells'
Signed-off-by: Guo Ren
---
.../bindings/interrupt-controller/csky,mpintc.txt | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
On 09/20/2018 12:16 PM, Florian Fainelli wrote:
> The Broadcom BCM963138DVT board has an eSATA port which is fully
> functional, turn on the AHCI controller and the companion SATA PHY.
>
> Signed-off-by: Florian Fainelli
Applied to devicetree/next
--
Florian
- irq-csky-apb-intc is a simple SOC interrupt controller which is
used in a lot of C-SKY CPU SOC products.
Changelog:
- pass checkpatch.pl.
- use "bool ret" instead of "int ret"
- add support-pulse-signal in irq-csky-apb-intc.c
- change name with upstream feed-back
- add INTC_IFR to
- Dt-bindings doc about C-SKY apb bus interrupt controller.
Signed-off-by: Guo Ren
Reviewed-by: Rob Herring
---
.../interrupt-controller/csky,apb-intc.txt | 62 ++
1 file changed, 62 insertions(+)
create mode 100644
Dt-bindings doc about C-SKY Multi-processors interrupt controller.
Changelog:
- Should be: '#interrupt-cells' not 'interrupt-cells'
Signed-off-by: Guo Ren
---
.../bindings/interrupt-controller/csky,mpintc.txt | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
On 09/20/2018 12:16 PM, Florian Fainelli wrote:
> The Broadcom BCM963138DVT board has an eSATA port which is fully
> functional, turn on the AHCI controller and the companion SATA PHY.
>
> Signed-off-by: Florian Fainelli
Applied to devicetree/next
--
Florian
Dt-bingdings doc for C-SKY SMP system setting.
Changelog:
- Drop the interrupt-parent.
Signed-off-by: Guo Ren
---
.../devicetree/bindings/timer/csky,mptimer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Dt-bingdings doc for C-SKY SMP system setting.
Changelog:
- Drop the interrupt-parent.
Signed-off-by: Guo Ren
---
.../devicetree/bindings/timer/csky,mptimer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Dt-bindings doc for gx6605s SOC's system timer.
Signed-off-by: Guo Ren
---
.../bindings/timer/csky,gx6605s-timer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Documentation/devicetree/bindings/timer/csky,gx6605s-timer.txt
diff --git
This is about 10th patchset for C-SKY linux drivers. All patches have
been checked by checkpatch.pl.
Any feedback is welcome, thx for all people review my patchset.
If you finish the review for the patchset, please give a Reviewed-By
/ Acked-By and I'll record it in the commit-msg.
Guo Ren (8):
This timer is used by SMP system and use mfcr/mtcr instruction
to access the regs.
Changelog:
- Add rollback for timer_of_cleanup.
- Use request_percpu_irq separate from time_of.
- Remove #define CPUHP_AP_CSKY_TIMER_STARTING.
- Add CPUHP_AP_CSKY_TIMER_STARTING in cpuhotplug.h.
- Support csky
Dt-bindings doc for gx6605s SOC's system timer.
Signed-off-by: Guo Ren
---
.../bindings/timer/csky,gx6605s-timer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Documentation/devicetree/bindings/timer/csky,gx6605s-timer.txt
diff --git
This is about 10th patchset for C-SKY linux drivers. All patches have
been checked by checkpatch.pl.
Any feedback is welcome, thx for all people review my patchset.
If you finish the review for the patchset, please give a Reviewed-By
/ Acked-By and I'll record it in the commit-msg.
Guo Ren (8):
This timer is used by SMP system and use mfcr/mtcr instruction
to access the regs.
Changelog:
- Add rollback for timer_of_cleanup.
- Use request_percpu_irq separate from time_of.
- Remove #define CPUHP_AP_CSKY_TIMER_STARTING.
- Add CPUHP_AP_CSKY_TIMER_STARTING in cpuhotplug.h.
- Support csky
Changelog:
- pass checkpatch.pl
- Add COMIPLE_TEST in Kconfig
- no cast is needed for "struct clock_event_device *ce = dev"
- remove: extra space after (u64)
- Add License and Copyright
- Use timer-of framework
- Change name with upstream feedback
- Use clksource_mmio framework
- Irq-csky-mpintc is C-SKY smp system interrupt controller and it
could support 16 soft irqs, 16 private irqs, and 992 max common
irqs.
Changelog:
- pass checkpatch.pl
- Move IPI_IRQ into the driver
- Remove irq_set_default_host() and use set_ipi_irq_mapping()
- Change name with
- Irq-csky-mpintc is C-SKY smp system interrupt controller and it
could support 16 soft irqs, 16 private irqs, and 992 max common
irqs.
Changelog:
- pass checkpatch.pl
- Move IPI_IRQ into the driver
- Remove irq_set_default_host() and use set_ipi_irq_mapping()
- Change name with
Changelog:
- pass checkpatch.pl
- Add COMIPLE_TEST in Kconfig
- no cast is needed for "struct clock_event_device *ce = dev"
- remove: extra space after (u64)
- Add License and Copyright
- Use timer-of framework
- Change name with upstream feedback
- Use clksource_mmio framework
On 09/20/2018 12:16 PM, Florian Fainelli wrote:
> Add Device Tree entries for the Broadcom AHCI and SATA PHY controller
> found on BCM63138 SoCs
>
> Signed-off-by: Florian Fainelli
Applied to devicetree/next.
--
Florian
On 09/20/2018 12:16 PM, Florian Fainelli wrote:
> Add Device Tree entries for the Broadcom AHCI and SATA PHY controller
> found on BCM63138 SoCs
>
> Signed-off-by: Florian Fainelli
Applied to devicetree/next.
--
Florian
From: Borislav Petkov
When booting with "nosmt=force" a message is issued into dmesg to
confirm that SMT has been force-disabled but such a message is not
issued when only "nosmt" is on the kernel command line.
Fix that.
Signed-off-by: Borislav Petkov
Cc: Peter Zijlstra
Cc: x...@kernel.org
From: Borislav Petkov
When booting with "nosmt=force" a message is issued into dmesg to
confirm that SMT has been force-disabled but such a message is not
issued when only "nosmt" is on the kernel command line.
Fix that.
Signed-off-by: Borislav Petkov
Cc: Peter Zijlstra
Cc: x...@kernel.org
On Tue, Oct 02, 2018 at 02:04:31AM +1000, Aleksa Sarai wrote:
> On 2018-10-01, Christian Brauner wrote:
> > On Mon, Oct 01, 2018 at 02:28:03PM +0200, Jann Horn wrote:
> > > On Sat, Sep 29, 2018 at 4:28 PM Aleksa Sarai wrote:
> > > > * AT_BENEATH: Disallow ".." or absolute paths (either in the
On Tue, Oct 02, 2018 at 02:04:31AM +1000, Aleksa Sarai wrote:
> On 2018-10-01, Christian Brauner wrote:
> > On Mon, Oct 01, 2018 at 02:28:03PM +0200, Jann Horn wrote:
> > > On Sat, Sep 29, 2018 at 4:28 PM Aleksa Sarai wrote:
> > > > * AT_BENEATH: Disallow ".." or absolute paths (either in the
On Thu, Oct 04, 2018 at 07:07:27PM +0200, Rafael J. Wysocki wrote:
[...]
> > > I don't see any dependency there, so I'll queue up the 1-3 in
> > > pm-domains and the 4-6 in pm-cpuidle.
> >
> > I do not see why we should merge patches 4-6 for v4.20; they add legacy
> > (DT bindings and related
On Thu, Oct 04, 2018 at 07:07:27PM +0200, Rafael J. Wysocki wrote:
[...]
> > > I don't see any dependency there, so I'll queue up the 1-3 in
> > > pm-domains and the 4-6 in pm-cpuidle.
> >
> > I do not see why we should merge patches 4-6 for v4.20; they add legacy
> > (DT bindings and related
On Thu, Oct 4, 2018 at 4:51 PM Daniel Lezcano wrote:
>
> On Tue, Oct 02, 2018 at 11:44:06PM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Rearrange the code in menu_select() so that the loop over idle states
> > always starts from 0 and get rid of the first_idx variable.
>
On Thu, Oct 4, 2018 at 4:51 PM Daniel Lezcano wrote:
>
> On Tue, Oct 02, 2018 at 11:44:06PM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Rearrange the code in menu_select() so that the loop over idle states
> > always starts from 0 and get rid of the first_idx variable.
>
Attempting to mmap to a memory mapped IO space returns -1s because the
memory encryption bit is set for these pages. According to the AMD spec,
this bit should not be set for non-DRAM space. The patch checks if this
is an memory IO region being accessed and decrypts accordingly.
Signed-off-by:
Attempting to mmap to a memory mapped IO space returns -1s because the
memory encryption bit is set for these pages. According to the AMD spec,
this bit should not be set for non-DRAM space. The patch checks if this
is an memory IO region being accessed and decrypts accordingly.
Signed-off-by:
On AMD based systems, mmap'ing a PCI MMIO region does not return proper
values. This is because the mmap_mem function does not consider the fact
that IO regions are not to be encrypted.
In the failing kernel, here's the output --
[root@foo]# ./memaccess 0xd000 -t pmem -l 32
0(0 ) :
On AMD based systems, mmap'ing a PCI MMIO region does not return proper
values. This is because the mmap_mem function does not consider the fact
that IO regions are not to be encrypted.
In the failing kernel, here's the output --
[root@foo]# ./memaccess 0xd000 -t pmem -l 32
0(0 ) :
> On Oct 2, 2018, at 1:12 AM, Peter Zijlstra wrote:
>
> On Mon, Oct 01, 2018 at 10:36:36PM -0700, Song Liu wrote:
>> Changes v1 -> v2: Fix PMU_FORMAT_ATTR as Peter suggested
>>
>> This patch enables uprobes with reference counter in fd-based uprobe.
>> Highest 32 bits of
> On Oct 2, 2018, at 1:12 AM, Peter Zijlstra wrote:
>
> On Mon, Oct 01, 2018 at 10:36:36PM -0700, Song Liu wrote:
>> Changes v1 -> v2: Fix PMU_FORMAT_ATTR as Peter suggested
>>
>> This patch enables uprobes with reference counter in fd-based uprobe.
>> Highest 32 bits of
On Thu, 2018-10-04 at 10:40 +0200, Daniel Lezcano wrote:
> On 04/10/2018 10:22, Rafael J. Wysocki wrote:
> > On Thu, Oct 4, 2018 at 9:42 AM Daniel Lezcano
> > wrote:
> > > The function get_loadavg() returns almost always zero. To be more
> > > precise, statistically speaking for a total of
On Thu, 2018-10-04 at 10:40 +0200, Daniel Lezcano wrote:
> On 04/10/2018 10:22, Rafael J. Wysocki wrote:
> > On Thu, Oct 4, 2018 at 9:42 AM Daniel Lezcano
> > wrote:
> > > The function get_loadavg() returns almost always zero. To be more
> > > precise, statistically speaking for a total of
On Thu, Oct 4, 2018 at 12:48 AM Michal Hocko wrote:
>
> On Wed 03-10-18 19:15:24, Dan Williams wrote:
> > Some data exfiltration and return-oriented-programming attacks rely on
> > the ability to infer the location of sensitive data objects. The kernel
> > page allocator, especially early in
Hi,
On 03.10.2018 20:01, Jann Horn wrote:
> On Mon, Oct 1, 2018 at 10:53 PM Alexey Budankov
> wrote:
>> 3. Every time an event for ${PMU} is created over perf_event_open():
>>a) the calling thread's euid is checked to belong to ${PMU}_users group
>> and if it does then the event's fd
On Thu, Oct 4, 2018 at 12:48 AM Michal Hocko wrote:
>
> On Wed 03-10-18 19:15:24, Dan Williams wrote:
> > Some data exfiltration and return-oriented-programming attacks rely on
> > the ability to infer the location of sensitive data objects. The kernel
> > page allocator, especially early in
Hi,
On 03.10.2018 20:01, Jann Horn wrote:
> On Mon, Oct 1, 2018 at 10:53 PM Alexey Budankov
> wrote:
>> 3. Every time an event for ${PMU} is created over perf_event_open():
>>a) the calling thread's euid is checked to belong to ${PMU}_users group
>> and if it does then the event's fd
On Thu, Oct 4, 2018 at 7:00 AM Greg Kroah-Hartman wrote:
> We should just get rid of the "unused" fields entirely. They aren't
> needed here as this is not a structure that anyone really cares about.
> We can move things around a bit if the padding is an issue.
>
> I've reverted this patch
On Thu, Oct 4, 2018 at 7:00 AM Greg Kroah-Hartman wrote:
> We should just get rid of the "unused" fields entirely. They aren't
> needed here as this is not a structure that anyone really cares about.
> We can move things around a bit if the padding is an issue.
>
> I've reverted this patch
On Thu, Oct 4, 2018 at 5:50 PM Daniel Lezcano wrote:
>
> On Tue, Oct 02, 2018 at 11:46:28PM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > If the next timer event (with the tick excluded) is closer than the
> > target residency of the second state or the PM QoS latency
On Thu, Oct 4, 2018 at 5:50 PM Daniel Lezcano wrote:
>
> On Tue, Oct 02, 2018 at 11:46:28PM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > If the next timer event (with the tick excluded) is closer than the
> > target residency of the second state or the PM QoS latency
On Thu, Oct 04, 2018 at 06:47:01PM +0200, Philipp Zabel wrote:
> Hi Leonard,
>
> On Thu, 2018-10-04 at 16:34 +, Leonard Crestez wrote:
> > This is required for the imx pci driver to send the PME_Turn_Off TLP.
> >
> > Signed-off-by: Leonard Crestez
> > Acked-by: Rob Herring
> > ---
> >
On Thu, Oct 04, 2018 at 06:47:01PM +0200, Philipp Zabel wrote:
> Hi Leonard,
>
> On Thu, 2018-10-04 at 16:34 +, Leonard Crestez wrote:
> > This is required for the imx pci driver to send the PME_Turn_Off TLP.
> >
> > Signed-off-by: Leonard Crestez
> > Acked-by: Rob Herring
> > ---
> >
On Thu, Oct 4, 2018 at 5:58 PM Lorenzo Pieralisi
wrote:
>
> On Thu, Oct 04, 2018 at 11:32:41AM +0200, Rafael J. Wysocki wrote:
> > On Thu, Oct 4, 2018 at 11:04 AM Rafael J. Wysocki
> > wrote:
> > >
> > > On Thursday, October 4, 2018 10:58:53 AM CEST Ulf Hansson wrote:
> > > > On 4 October 2018
On Thu, Oct 4, 2018 at 5:58 PM Lorenzo Pieralisi
wrote:
>
> On Thu, Oct 04, 2018 at 11:32:41AM +0200, Rafael J. Wysocki wrote:
> > On Thu, Oct 4, 2018 at 11:04 AM Rafael J. Wysocki
> > wrote:
> > >
> > > On Thursday, October 4, 2018 10:58:53 AM CEST Ulf Hansson wrote:
> > > > On 4 October 2018
On Thu, Oct 04, 2018 at 06:34:31AM -1000, Steve Sakoman wrote:
> Interesting indeed. Who would have thought someone would be using the
> "unused" padding variable!
Ugh :(
> How would folks prefer we fix this, in the referenced patch or by
> eliminating the use of "unused" in samsung.c?
We
On Thu, Oct 04, 2018 at 06:34:31AM -1000, Steve Sakoman wrote:
> Interesting indeed. Who would have thought someone would be using the
> "unused" padding variable!
Ugh :(
> How would folks prefer we fix this, in the referenced patch or by
> eliminating the use of "unused" in samsung.c?
We
On Thu, Oct 4, 2018 at 9:31 AM Nadav Amit wrote:
>
> at 7:11 AM, Andy Lutomirski wrote:
>
> >
> >
> > On Oct 3, 2018, at 9:59 PM, Nadav Amit wrote:
> >
> >> This RFC proposes to return part of the entry-area back to the fixmap to
> >> improve system-call performance. Currently, since the
Hello Dear,
how are you today,I hope you are doing great.
It is my great pleasure to contact you,I want to make a new and special
friend,I hope you don't mind. My name is Tracy William from the United States,
Am a french and English nationality. I will give you pictures and more details
On Thu, Oct 4, 2018 at 9:31 AM Nadav Amit wrote:
>
> at 7:11 AM, Andy Lutomirski wrote:
>
> >
> >
> > On Oct 3, 2018, at 9:59 PM, Nadav Amit wrote:
> >
> >> This RFC proposes to return part of the entry-area back to the fixmap to
> >> improve system-call performance. Currently, since the
Hello Dear,
how are you today,I hope you are doing great.
It is my great pleasure to contact you,I want to make a new and special
friend,I hope you don't mind. My name is Tracy William from the United States,
Am a french and English nationality. I will give you pictures and more details
> On Oct 4, 2018, at 9:45 AM, Rik van Riel wrote:
>
> On Thu, 2018-10-04 at 16:05 +0200, Sebastian Andrzej Siewior wrote:
>
>
>> In v3 I dropped that decouple idea. I also learned that the wrpkru
>> instruction is not privileged and so caching it in kernel does not
>> work.
>
> Wait, so
> On Oct 4, 2018, at 9:45 AM, Rik van Riel wrote:
>
> On Thu, 2018-10-04 at 16:05 +0200, Sebastian Andrzej Siewior wrote:
>
>
>> In v3 I dropped that decouple idea. I also learned that the wrpkru
>> instruction is not privileged and so caching it in kernel does not
>> work.
>
> Wait, so
On Thu, Oct 04, 2018 at 06:23:38PM +0200, Nicolas Cavallari wrote:
> Many users of restart_handlers are sleeping in their callbacks. Some
> are doing infinite loops or calling driver code that may sleep or
> perform operation on slow busses, like i2c.
>
> This is not allowed in an atomic
On Thu, Oct 04, 2018 at 06:23:38PM +0200, Nicolas Cavallari wrote:
> Many users of restart_handlers are sleeping in their callbacks. Some
> are doing infinite loops or calling driver code that may sleep or
> perform operation on slow busses, like i2c.
>
> This is not allowed in an atomic
On Thu, Oct 04, 2018 at 11:03:12AM +1000, Dave Chinner wrote:
> Hi Greg,
>
> Can you please pull the XFS from the tag listed below. It's a bit
> bigger than that I'd like this late in the cycle, but we've had a
> few challenges getting ourselves sorted out this cycle. Details
> of the contents
On Thu, Oct 04, 2018 at 11:03:12AM +1000, Dave Chinner wrote:
> Hi Greg,
>
> Can you please pull the XFS from the tag listed below. It's a bit
> bigger than that I'd like this late in the cycle, but we've had a
> few challenges getting ourselves sorted out this cycle. Details
> of the contents
On Thu, Oct 04, 2018 at 02:55:42PM +1000, Dave Airlie wrote:
> Hi Greg,
>
> Nothing too much happening at this point,
>
> 3 i915 fixes:
> compressed error handling zlib fix
> compiler warning cleanup
> and a minor code cleanup
>
> 2 tda9950:
> Two fixes for the HDMI CEC
>
> 1 exynos:
> A fix
On Thu, Oct 04, 2018 at 02:55:42PM +1000, Dave Airlie wrote:
> Hi Greg,
>
> Nothing too much happening at this point,
>
> 3 i915 fixes:
> compressed error handling zlib fix
> compiler warning cleanup
> and a minor code cleanup
>
> 2 tda9950:
> Two fixes for the HDMI CEC
>
> 1 exynos:
> A fix
Hi Leonard,
On Thu, 2018-10-04 at 16:34 +, Leonard Crestez wrote:
> This is required for the imx pci driver to send the PME_Turn_Off TLP.
>
> Signed-off-by: Leonard Crestez
> Acked-by: Rob Herring
> ---
> drivers/reset/reset-imx7.c | 1 +
>
Hi arm-soc maintainers,
Please merge the following updates for next.
PS. One of the patches is depending on the last pull request for fixes to build
https://patchwork.kernel.org/patch/10622883/
I didn't include the fix patches directly in this pull request to prevent a
complicated merge.
Hi Leonard,
On Thu, 2018-10-04 at 16:34 +, Leonard Crestez wrote:
> This is required for the imx pci driver to send the PME_Turn_Off TLP.
>
> Signed-off-by: Leonard Crestez
> Acked-by: Rob Herring
> ---
> drivers/reset/reset-imx7.c | 1 +
>
Hi arm-soc maintainers,
Please merge the following updates for next.
PS. One of the patches is depending on the last pull request for fixes to build
https://patchwork.kernel.org/patch/10622883/
I didn't include the fix patches directly in this pull request to prevent a
complicated merge.
Hi,
On Wed, Oct 3, 2018 at 5:14 PM Matthias Kaehlcke wrote:
>
> Add a channel node for the die temperature to the ADC.
>
> Signed-off-by: Matthias Kaehlcke
> Reviewed-by: Douglas Anderson
> ---
> Changes in v4:
> - added unit address to 'die-temp' node
This probably should have been "changes
From: Nathan Chancellor
Sent: Thursday, October 04, 2018 7:39 PM
> Clang warns when one enumerated type is implicitly converted to another.
>
> drivers/net/ethernet/qlogic/qed/qed_ll2.c:799:32: warning: implicit
> conversion from enumeration type 'enum core_tx_dest' to different
> enumeration
Hi,
On Wed, Oct 3, 2018 at 5:14 PM Matthias Kaehlcke wrote:
>
> Add a channel node for the die temperature to the ADC.
>
> Signed-off-by: Matthias Kaehlcke
> Reviewed-by: Douglas Anderson
> ---
> Changes in v4:
> - added unit address to 'die-temp' node
This probably should have been "changes
From: Nathan Chancellor
Sent: Thursday, October 04, 2018 7:39 PM
> Clang warns when one enumerated type is implicitly converted to another.
>
> drivers/net/ethernet/qlogic/qed/qed_ll2.c:799:32: warning: implicit
> conversion from enumeration type 'enum core_tx_dest' to different
> enumeration
On Thu, 2018-10-04 at 16:05 +0200, Sebastian Andrzej Siewior wrote:
> In v3 I dropped that decouple idea. I also learned that the wrpkru
> instruction is not privileged and so caching it in kernel does not
> work.
Wait, so any thread can bypass its memory protection
keys, even if there is a
On Thu, 2018-10-04 at 16:05 +0200, Sebastian Andrzej Siewior wrote:
> In v3 I dropped that decouple idea. I also learned that the wrpkru
> instruction is not privileged and so caching it in kernel does not
> work.
Wait, so any thread can bypass its memory protection
keys, even if there is a
From: David Howells
Date: Thu, 04 Oct 2018 14:50:31 +0100
> Here are some development patches for AF_RXRPC. The most significant points
> are:
...
> The patches are tagged here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-nex
From: David Howells
Date: Thu, 04 Oct 2018 14:50:31 +0100
> Here are some development patches for AF_RXRPC. The most significant points
> are:
...
> The patches are tagged here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-nex
Hi Michal,
On Thu, Oct 4, 2018 at 12:53 AM Michal Hocko wrote:
>
> On Wed 03-10-18 19:15:18, Dan Williams wrote:
> > Changes since v1:
> > * Add support for shuffling hot-added memory (Andrew)
> > * Update cover letter and commit message to clarify the performance impact
> > and relevance to
On Thu, Oct 4, 2018 at 4:40 AM Laurentiu Tudor wrote:
>
> Hi Leo,
>
> On 02.10.2018 01:58, Li Yang wrote:
> > Hi arm-soc maintainers,
> >
> > Please merge the updated fix for the following issue.
> >
> > Regards,
> > Leo
> >
> > The following changes since commit
401 - 500 of 1300 matches
Mail list logo
