|
[PATCH 4.4-cip 2/6] arm: mm: support ARCH_MMAP_RND_BITS
From: Daniel Cashman <dcashman@...>
commit e0c25d958f78acfd5c97df5776eeba3e0684101b upstream.
arm: arch_mmap_rnd() uses a hard-code value of 8 to generate the random
offset for the mmap base
From: Daniel Cashman <dcashman@...>
commit e0c25d958f78acfd5c97df5776eeba3e0684101b upstream.
arm: arch_mmap_rnd() uses a hard-code value of 8 to generate the random
offset for the mmap base
|
By
Ben Hutchings <ben.hutchings@...>
·
#90
·
|
|
[PATCH 4.4-cip 1/6] mm: mmap: add new /proc tunable for mmap_base ASLR
From: Daniel Cashman <dcashman@...>
commit d07e22597d1d355829b7b18ac19afa912cf758d1 upstream.
Address Space Layout Randomization (ASLR) provides a barrier to
exploitation of user-space
From: Daniel Cashman <dcashman@...>
commit d07e22597d1d355829b7b18ac19afa912cf758d1 upstream.
Address Space Layout Randomization (ASLR) provides a barrier to
exploitation of user-space
|
By
Ben Hutchings <ben.hutchings@...>
·
#89
·
|
|
[PATCH 4.4-cip 0/6] Extend user-space ASLR range
This is a backport of changes in 4.5 to extend the range of Address
Space Layout Randomisation for user-space processes. When enabled, this
should make some user-space vulnerabilities harder to
This is a backport of changes in 4.5 to extend the range of Address
Space Layout Randomisation for user-space processes. When enabled, this
should make some user-space vulnerabilities harder to
|
By
Ben Hutchings <ben.hutchings@...>
·
#88
·
|
|
The Problem with build.log
Hi Robert,
I may have found the problem with the links to the build.log,
kernel.config and zImage files.
As you can see from the attached Screenshots, when I hover over the
links, the URL has some
Hi Robert,
I may have found the problem with the links to the build.log,
kernel.config and zImage files.
As you can see from the attached Screenshots, when I hover over the
links, the URL has some
|
By
Don Brown <don.brown@...>
·
#125
·
|
|
Re: Features backports
Hi,
Since the Intel Apollo Lake has already released, we started to check the
patches for that. I think the basic functionality has already upstreamed
and it might be enough for expected use
Hi,
Since the Intel Apollo Lake has already released, we started to check the
patches for that. I think the basic functionality has already upstreamed
and it might be enough for expected use
|
By
Yoshitake Kobayashi
·
#87
·
|
|
Re: Open Source OPC UA
If you have a link (and the project has a proper license), maybe send a
PR to the open62541.org to extend their list.
If we only had higher languages, that would be a major limitation. It's
not so
If you have a link (and the project has a proper license), maybe send a
PR to the open62541.org to extend their list.
If we only had higher languages, that would be a major limitation. It's
not so
|
By
Jan Kiszka
·
#86
·
|
|
Re: Open Source OPC UA
Am 29/11/2016 um 20:36 schrieb Jan Kiszka:
there's another tiny implementation from some of the Ostwestfalen-Lippe
(OWL) group of people in Germany, but since it targets devices with
only 10s of KiB
Am 29/11/2016 um 20:36 schrieb Jan Kiszka:
there's another tiny implementation from some of the Ostwestfalen-Lippe
(OWL) group of people in Germany, but since it targets devices with
only 10s of KiB
|
By
Wolfgang Mauerer <wm@...>
·
#85
·
|
|
Open Source OPC UA
Hi all,
does anyone already have some experience with OSS OPC UA
implementations, specifically for resource constrained devices? We
stumbled over
http://open62541.org
which seems like being on the
Hi all,
does anyone already have some experience with OSS OPC UA
implementations, specifically for resource constrained devices? We
stumbled over
http://open62541.org
which seems like being on the
|
By
Jan Kiszka
·
#83
·
|
|
Re: Features backports
Hi,
I think we have a good chance once they see we are testing Beaglebone Black in the open. That would be a good opportunity we might add value to them.
Definitely I would talk to them before. If
Hi,
I think we have a good chance once they see we are testing Beaglebone Black in the open. That would be a good opportunity we might add value to them.
Definitely I would talk to them before. If
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#82
·
|
|
Re: [Fuego] Update week 47
By
Bird, Timothy <Tim.Bird@...>
·
#84
·
|
|
Re: Update week 47
Hi,
(Cc'ed to Fuego and LTSI mailing lists).
Hi,
(Cc'ed to Fuego and LTSI mailing lists).
|
By
Daniel Sangorrin <daniel.sangorrin@...>
·
#81
·
|
|
Re: Features backports
Hi,
Regarding to Altera Socfpga Cyclone V, we might want to backport from 4.9;
- L2cache ECC(./arch/arm/mm/cache-l2x0.c)
- QSPI Flash controller(drivers/mtd/spi-nor/cadence-quadspi.c)
4.9 is still
Hi,
Regarding to Altera Socfpga Cyclone V, we might want to backport from 4.9;
- L2cache ECC(./arch/arm/mm/cache-l2x0.c)
- QSPI Flash controller(drivers/mtd/spi-nor/cadence-quadspi.c)
4.9 is still
|
By
Takuo Koguchi
·
#80
·
|
|
Re: Features backports
Hi,
This is good. It allows us to dig a little and provide some light.
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...
Hi,
This is good. It allows us to dig a little and provide some light.
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#79
·
|
|
Re: Features backports
To add two features areas from our requirement list:
- Distributed Switch Architecture, basically the level of 4.8 would be
sufficient. However, there might be too many dependencies on
networking
To add two features areas from our requirement list:
- Distributed Switch Architecture, basically the level of 4.8 would be
sufficient. However, there might be too many dependencies on
networking
|
By
Jan Kiszka
·
#78
·
|
|
Re: Proposal: send gitlab notifications to this list
Hi Agustin,
Thanks for the suggestion. I think it is a nice idea.
Best regards,
Yoshi
Hi Agustin,
Thanks for the suggestion. I think it is a nice idea.
Best regards,
Yoshi
|
By
Yoshitake Kobayashi
·
#77
·
|
|
Re: Proposal: send gitlab notifications to this list
Hi Agustin,
Am 28/11/2016 um 10:47 schrieb Agustin Benito Bethencourt:
That's a good idea, albeit we could also think about doing development
completely kernel-style, with a review of patches on the
Hi Agustin,
Am 28/11/2016 um 10:47 schrieb Agustin Benito Bethencourt:
That's a good idea, albeit we could also think about doing development
completely kernel-style, with a review of patches on the
|
By
Wolfgang Mauerer <wm@...>
·
#76
·
|
|
Proposal: send gitlab notifications to this list
Hi,
I think it would be positive to activate the mail notifications from gitlab and send them to this list.
By activating them, you will be able to follow what is happening in our repos through
Hi,
I think it would be positive to activate the mail notifications from gitlab and send them to this list.
By activating them, you will be able to follow what is happening in our repos through
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#75
·
|
|
Update week 47
Hi,
++ Meetings
* This week the team at Codethink working on CIP has met f2f for the first time in Manchester, since three of us work remotely from home.
** Agreed on basic management processes we
Hi,
++ Meetings
* This week the team at Codethink working on CIP has met f2f for the first time in Manchester, since three of us work remotely from home.
** Agreed on basic management processes we
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#74
·
|
|
Features backports
Hi,
as you probably know, the more features we backport, the higher will be the maintenance cost overtime so as a strategy, we need to be very conservative.
I sent a mail some days ago about the
Hi,
as you probably know, the more features we backport, the higher will be the maintenance cost overtime so as a strategy, we need to be very conservative.
I sent a mail some days ago about the
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#73
·
|
|
Common Vulnerabilities and Exposures
Hi,
one of the key parts of the maintenance work is to follow the Common Vulnerabilities and Exposures (CVE)[1] and the fixes that comes out of them, in this case, to the kernel.
We can check
Hi,
one of the key parts of the maintenance work is to follow the Common Vulnerabilities and Exposures (CVE)[1] and the fixes that comes out of them, in this case, to the kernel.
We can check
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#72
·
|