`Specific guidelines for the kernel documentation` section of
`kernel-documentation.rst` suggests to use ``~`` for subsection but
subsections in HOWTO is not marked in the format. This commit marks
them in the format.
Signed-off-by: SeongJae Park
---
Documentation/process/howto.rst | 15 +++
Because few sentences has no whitespace between URL and text, few
document viewers fail to properly parse the URL from it. This commit
adds whitespace between them to fix the problem.
Signed-off-by: SeongJae Park
---
Documentation/ko_KR/HOWTO | 6 +++---
1 file changed, 3 insertions(+), 3 delet
`Specific guidelines for the kernel documentation` section of
`kernel-documentation.rst` suggests to use ``~`` for subsection but
subsections in HOWTO is not marked in the format. This commit marks
them in the format.
Signed-off-by: SeongJae Park
---
Documentation/ko_KR/HOWTO | 12
This commit applies commit 022e04d6f555 ("Documentation/HOWTO: convert
to ReST notation") to Korean translation and fix a trivial ReST build
failure problem.
Signed-off-by: SeongJae Park
---
Documentation/ko_KR/HOWTO | 55 ---
1 file changed, 52 insert
This commit appplies commit f1eebe92c265 ("Documentation/HOWTO: adjust
external link references") to Korean translation.
Signed-off-by: SeongJae Park
---
Documentation/ko_KR/HOWTO | 39 ++-
1 file changed, 18 insertions(+), 21 deletions(-)
diff --git a/Docume
This commit applies commit 1b49ecf2f3be ("docs: Clean up bare :: lines")
to Korean translation.
Signed-off-by: SeongJae Park
---
Documentation/ko_KR/HOWTO | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/Documentation/ko_KR/HOWTO b/Documentation/ko_KR/HOWTO
index
This patchset applies ReST conversion effort for HOWTO document to its Korean
translation. It also contains fixup of trivial nitpicks in the document and
the translation.
Changes from v1:
- Rebased on next-20161028
The base version contains commit 186128f75392 ("docs-rst: add documents to
dev
This commit applies commit 43fb67a5258c ("Documentation/HOWTO: update
information about generating documentation") to Korean translation.
Signed-off-by: SeongJae Park
---
Documentation/ko_KR/HOWTO | 30 ++
1 file changed, 22 insertions(+), 8 deletions(-)
diff --git a
On Mon, Oct 31, 2016 at 06:47:10AM -0600, Greg KH wrote:
> I'm announcing the release of the 4.8.6 kernel.
Hey Greg,
I've put more work into improving my filters to find stable commits upstream.
The list below, taken from v4.8..v4.9-rc2 commits contains mostly commits that
aren't tagged for sta
This commit applies commit 609d99a3b72e ("Documentation/HOWTO: add
cross-references to other documents") to Korean translation.
Signed-off-by: SeongJae Park
---
Documentation/ko_KR/HOWTO | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/Documentation/ko_KR/
Hi Linus,
The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69:
Linux 4.9-rc2 (2016-10-23 17:10:14 -0700)
are available in the git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v4.9-rc4
for you to fetch changes up to 05692d7005a364add85c6e25a6c444
Signed-off-by: SeongJae Park
---
Documentation/ko_KR/HOWTO | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ko_KR/HOWTO b/Documentation/ko_KR/HOWTO
index 025252731af5..4f5778dfeed2 100644
--- a/Documentation/ko_KR/HOWTO
+++ b/Documentation/ko_KR/HOWTO
@@ -231,7 +2
On Monday 31 October 2016 21:22:18 Matt Ranostay wrote:
> On Tue, Oct 25, 2016 at 11:47 AM, Matt Ranostay
> wrote:
> > On Mon, Oct 24, 2016 at 1:14 PM, Pavel Machek wrote:
> >> On Mon 2016-10-24 12:58:25, Matt Ranostay wrote:
> >>> Pavel + Sebastian this is the patchset that need I some input on
On Tue, Sep 27, 2016 at 01:18:00PM +0530, Pratyush Anand wrote:
> +int arch_uprobe_analyze_insn(struct arch_uprobe *auprobe, struct mm_struct
> *mm,
> + unsigned long addr)
> +{
> + probe_opcode_t insn;
> +
> + /* TODO: Currently we do not support AARCH32 instruction probing */
Hi Pratyush,
On Mon, Oct 31, 2016 at 02:10:43PM +0530, Pratyush Anand wrote:
> On Sun, Oct 30, 2016 at 7:39 PM, Catalin Marinas
> wrote:
> > On Tue, Sep 27, 2016 at 01:18:00PM +0530, Pratyush Anand wrote:
> >> --- /dev/null
> >> +++ b/arch/arm64/kernel/probes/uprobes.c
> >> @@ -0,0 +1,221 @@
> >>
On Mon, 31 Oct 2016, Jim Davis wrote:
> On my Ubuntu 16.04 system, make htmldocs works just fine (hurrah!) but
> make cleandocs misses a fair number of files:
>
> HTMLDocumentation/DocBook/index.html
> jim@krebstar:~/linux-rc$ make cleandocs
> jim@krebstar:~/linux-rc$ git status
> HEAD detac
On 10/31/2016 12:55 PM, Scott Branden wrote:
> Florian,
>
> On 16-10-31 07:23 AM, Srinivas Kandagatla wrote:
>>
>> On 24/10/16 20:12, Jonathan Richardson wrote:
>>> From: Jonathan Richardson
>>>
>>> Add support for 32 and 64-bit versions of Broadcom's On-Chip OTP
>>> controller. These controllers
The 'system-power-controller' singleton entry can be used in the
devicetree node of the jz4740-rtc driver to specify that the driver is
granted the right to power off the system through the registers of the
RTC unit.
See the documentation for more details:
Documentation/devicetree/bindings/rtc/ing
The RTC unit present in the JZ4780 works mostly the same as the one in
the JZ4740. The major difference is that register writes need to be
explicitly enabled, by writing a magic code (0xA55A) to a "write
enable" register before each access.
Signed-off-by: Paul Cercueil
Acked-by: Maarten ter Huurn
This commit removes two things:
- The platform_device that corresponds to the RTC driver, since we now
probe this driver from devicetree;
- The platform power-off code, since all the jz4740-based platforms are
now using the jz4740-rtc driver as the system power controller.
Signed-off-by: Paul
See
Documentation/devicetree/bindings/rtc/ingenic,jz4740-rtc.txt
for a description of the bindings.
Signed-off-by: Paul Cercueil
Acked-by: Maarten ter Huurne
---
drivers/rtc/rtc-jz4740.c | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
v2: No change
v3: No change
diff --
Now that the jz4740-rtc driver supports devicetree, we can add a
devicetree node for it.
Signed-off-by: Paul Cercueil
Acked-by: Maarten ter Huurne
---
arch/mips/boot/dts/ingenic/jz4740.dtsi | 11 +++
1 file changed, 11 insertions(+)
v2: Previous patch 5/5 was garbage. This is a new pat
On Wed, Oct 26, 2016 at 04:30:16PM +0200, Johannes Thumshirn wrote:
> The Read Completion Boundary bit must only be set on a device or endpoint if
> it is set on the upstream bridge.
Please include the spec reference and a stable tag (if you think
that's relevant) in the next version.
I know you
This commit adds documentation for the device-tree bindings of the
jz4740-rtc driver, which supports the RTC unit present in the JZ4740 and
JZ4780 SoCs from Ingenic.
Signed-off-by: Paul Cercueil
Acked-by: Maarten ter Huurne
---
.../devicetree/bindings/rtc/ingenic,jz4740-rtc.txt | 37 +++
Since we already have a devicetree node for the jz4740-rtc driver, we
don't have to probe it from platform code.
Besides, using the jz4740-rtc driver as the power controller for the
qi_lb60 platform allows us to remove the jz4740 platform power-off code,
since this is the only jz4740-based board u
Am 2016-10-31 um 16:21 schrieb Joerg Roedel:
> On Mon, Oct 31, 2016 at 11:40:06AM +0100, Martin Kepplinger wrote:
>> In case the screenshot doesn't make it to you, here it is:
>> https://postimg.org/image/5wl2wemt9/
>
> Can you please send a boot-dmesg and 'lspci -v'? We need more
> information ab
* Jann Horn:
> On Mon, Oct 31, 2016 at 09:04:02AM -0700, Kees Cook wrote:
>> On Mon, Oct 31, 2016 at 7:04 AM, Jann Horn wrote:
>> > On machines with sizeof(unsigned long)==8, this ensures that the more
>> > significant 32 bits of stack_canary are random, too.
>> > stack_canary is defined as unsig
I just tried to build 4.9 (rc3) for the first time (x86_64, i7 haswell)
After making my choices in make oldconfig, make -j8 failed in
less than 2 sec.
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
HOSTCC scripts/sortextable
CC scripts/mod/devicetable-offsets.s
In fil
Laurent Pinchart writes:
> Hi Bartosz,
>
> Thank you for the patch.
>
> On Monday 31 Oct 2016 15:45:37 Bartosz Golaszewski wrote:
>> Enable the MSTPRI configuration and DDR2/mDDR memory controller
>> nodes on da850-lcdk. This is needed in order to adjust the memory
>> throughput constraints for b
Up to this point, the USB phy clock configuration was handled manually in
the board files and in the usb drivers. This adds proper clocks so that
the usb drivers can use clk_get and clk_enable and not have to worry about
the details. Also, the related code is removed from the board files and
replac
Add a syscon node for the SoC CFGCHIPn registers. It includes a child node
for the USB PHY that is part of this range of registers.
Also have to add OF_DEV_AUXDATA() entry so that clock lookup will work for
the the USB PHY driver.
Signed-off-by: David Lechner
---
arch/arm/boot/dts/da850.dtsi
From: Axel Haslam
The usb20_phy clock needs to be registered for the driver to be able
to get and enable a clock. Currently the usb phy clocks are registered
form board files, which will not be called during a device tree based
boot.
To be able to probe correctly usb form a device tree boot, reg
I reworked the "[PATCH v6 4/5] ARM: DTS: da850: Add cfgchip syscon node" and
"[PATCH v6 5/5] ARM: DTS: da850: Add usb phy node" patches that were dropped
from linux-davinci into the new "ARM: dts: da850: Add cfgchip syscon node"
patch. This should be OK unless it is decided that the BayLibre guys s
On Mon, Oct 31, 2016 at 11:52:49AM -0600, Greg Kroah-Hartman wrote:
> Based on the discussion at the kernel summit a few hours ago, here's a
> quick bug-fix release for 4.4-stable to resolve an issue with 4.4.29 and
> older kernels. I'll probably release it once the testing systems run on
> it to
On Mon, Oct 31, 2016 at 09:44:51PM +0100, Martin Kepplinger wrote:
> This is one machine booting a bad kernel. I could provide another
> example later this week.
You have an Intel system without any IOMMU (enabled), otherwise you
would have a DMAR-ACPI table, but there is none:
> [0.00] A
On Mon, Oct 31, 2016 at 09:45:59PM +0100, Florian Weimer wrote:
> * Jann Horn:
>
> > On Mon, Oct 31, 2016 at 09:04:02AM -0700, Kees Cook wrote:
> >> On Mon, Oct 31, 2016 at 7:04 AM, Jann Horn wrote:
> >> > On machines with sizeof(unsigned long)==8, this ensures that the more
> >> > significant 32
On Mon, 2016-10-31 at 21:45 +0100, Florian Weimer wrote:
> * Jann Horn:
>
> > On Mon, Oct 31, 2016 at 09:04:02AM -0700, Kees Cook wrote:
> > > On Mon, Oct 31, 2016 at 7:04 AM, Jann Horn wrote:
> > > > On machines with sizeof(unsigned long)==8, this ensures that the
> > > > more
> > > > significan
Em Mon, 31 Oct 2016 14:17:59 -0600
Mauro Carvalho Chehab escreveu:
> Em Mon, 31 Oct 2016 13:15:24 -0600
> Jonathan Corbet escreveu:
>
> > On Mon, 31 Oct 2016 11:51:20 -0700
> > Jim Davis wrote:
> >
> > > Running make pdfdocs on a Ubuntu 16.04 system fails with
> > >
> > > Makefile:58: reci
> It makes a lot of sense on x86_64 where it means the canary is still
> 56
> bits. Also, you want -fstack-check for protecting again stack
> overflows
> rather than stack *buffer* overflow. SSP won't really help you in that
> regard. Sadly, while -fstack-check now works well in GCC 6 with little
>
On Wed, Oct 26, 2016 at 09:02:19AM -0700, Babu Moger wrote:
> This is an attempt to cleanup watchdog handlers. Right now,
> kernel/watchdog.c implements both softlockup and hardlockup detectors.
> Softlockup code is generic. Hardlockup code is arch specific. Some
> architectures don't use hardlocku
VCHI messages between the CPU and firmware use 32-bit
bus addresses. Explicitly set the DMA mask and coherent
on all platforms.
Signed-off-by: Michael Zoran
---
.../staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/s
From: Colin Ian King
Trivial fix to spelling mistake "iternations" to "iterations"
Signed-off-by: Colin Ian King
---
tools/testing/selftests/media_tests/media_device_test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/media_tests/media_device_test
* Daniel Micay:
>> It makes a lot of sense on x86_64 where it means the canary is
>> still 56 bits. Also, you want -fstack-check for protecting again
>> stack overflows rather than stack *buffer* overflow. SSP won't
>> really help you in that regard. Sadly, while -fstack-check now
>> works well in
From: Colin Ian King
Trivial fix to spelling mistake "itertation" to "iteration"
Signed-off-by: Colin Ian King
---
tools/testing/selftests/x86/protection_keys.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/x86/protection_keys.c
b/tools/testing/se
On Mon 2016-10-31 14:47:39, Mark Rutland wrote:
> On Mon, Oct 31, 2016 at 09:27:05AM +0100, Pavel Machek wrote:
> > > On Fri, Oct 28, 2016 at 01:21:36PM +0200, Pavel Machek wrote:
> > > > > Has this been tested on a system vulnerable to rowhammer, and if so,
> > > > > was
> > > > > it reliable in
While we properly disabled the per-CPU timer interrupt, we also need to
make sure that all interrupts that can possibly have this CPU in their
smp_affinity mask also have a chance to see this interrupt migrated to a
CPU not being taken offline.
Fixes: 230b6ff57552 ("MIPS: BMIPS: Mask off timer IRQ
Hi,
These two patches are against Thomas' irq/core branch as of today:
4cd13c21b207e80ddb1144c576500098f2d5f882 ("softirq: Let ksoftirqd do its job")
Patches can be taken indepdently or together, your call.
Florian Fainelli (2):
irqchip/bcm7038-l1: Implement irq_cpu_offline
MIPS: BMIPS: Mig
We did not implement an irq_cpu_offline callback for our irqchip, yet we
support setting a given IRQ's affinity. This resulted in interrupts
whose affinity mask included CPUs being taken offline not to work
correctly once the CPU had been put offline.
Fixes: 5f7f0317ed28 ("IRQCHIP: Add new driver
On Mon, Oct 31, 2016 at 3:39 PM, Paul Cercueil wrote:
> This commit adds documentation for the device-tree bindings of the
> jz4740-rtc driver, which supports the RTC unit present in the JZ4740 and
> JZ4780 SoCs from Ingenic.
>
> Signed-off-by: Paul Cercueil
> Acked-by: Maarten ter Huurne
> ---
Hi,
These two patches are against Thomas' irq/core branch as of today:
4cd13c21b207e80ddb1144c576500098f2d5f882 ("softirq: Let ksoftirqd do its job")
Patches can be taken indepdently or together, your call.
Florian Fainelli (2):
irqchip/bcm7038-l1: Implement irq_cpu_offline
MIPS: BMIPS: Mig
We did not implement an irq_cpu_offline callback for our irqchip, yet we
support setting a given IRQ's affinity. This resulted in interrupts
whose affinity mask included CPUs being taken offline not to work
correctly once the CPU had been put offline.
Fixes: 5f7f0317ed28 ("IRQCHIP: Add new driver
While we properly disabled the per-CPU timer interrupt, we also need to
make sure that all interrupts that can possibly have this CPU in their
smp_affinity mask also have a chance to see this interrupt migrated to a
CPU not being taken offline.
Fixes: 230b6ff57552 ("MIPS: BMIPS: Mask off timer IRQ
On 10/31/2016 02:17 PM, Florian Fainelli wrote:
> Hi,
>
> These two patches are against Thomas' irq/core branch as of today:
>
> 4cd13c21b207e80ddb1144c576500098f2d5f882 ("softirq: Let ksoftirqd do its job")
>
> Patches can be taken indepdently or together, your call.
Resending since I goofed o
On Mon, 2016-10-31 at 22:10 +0100, Florian Weimer wrote:
> * Daniel Micay:
>
> > > It makes a lot of sense on x86_64 where it means the canary is
> > > still 56 bits. Also, you want -fstack-check for protecting again
> > > stack overflows rather than stack *buffer* overflow. SSP won't
> > > really
On Mon, Oct 31, 2016 at 11:58 AM, Joel Holdsworth
wrote:
> Hi Rob,
>
> Thanks for taking the time review the patches.
>
>>> .../bindings/fpga/lattice-ice40-fpga-mgr.txt | 23 +++
>>
>>
>> It's preferred that bindings are a separate patch.
>
>
> Can you just clarify a little? I'm happy to sp
On Mon, Oct 31, 2016 at 10:10:41PM +0100, Florian Weimer wrote:
> * Daniel Micay:
>
> >> It makes a lot of sense on x86_64 where it means the canary is
> >> still 56 bits. Also, you want -fstack-check for protecting again
> >> stack overflows rather than stack *buffer* overflow. SSP won't
> >> rea
John Heenan writes:
> The rtl8723bu wireless IC shows evidence of a more agressive approach to
> power saving, powering down its RF side when there is no wireless
> interfacing but leaving USB interfacing intact. This makes the wireless
> IC more suitable for use in devices which need to keep thei
On Mon, 2016-10-31 at 22:22 +0100, Jann Horn wrote:
> On Mon, Oct 31, 2016 at 10:10:41PM +0100, Florian Weimer wrote:
> > * Daniel Micay:
> >
> > > > It makes a lot of sense on x86_64 where it means the canary is
> > > > still 56 bits. Also, you want -fstack-check for protecting again
> > > > stac
On Tue, Nov 1, 2016 at 3:37 AM, Hannes Reinecke wrote:
> Signed-off-by: Hannes Reinecke
> Reviewed-by: Christoph Hellwig
> ---
> drivers/block/loop.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/block/loop.c b/drivers/block/loop.c
> index fa1b7a9..3008dec
* Jann Horn:
> Until recently: Zero, no guard pages below stacks, stack overflow
> goes straight into some other allocation.
> Now: One guard page, thanks to a lot of work by Andy Lutomirski.
> (I think that change is in the current 4.9-rc3 kernel, but not in
> any stable kernel yet.)
Sorry, I me
On 10/31/2016 4:00 PM, Don Zickus wrote:
On Wed, Oct 26, 2016 at 09:02:19AM -0700, Babu Moger wrote:
This is an attempt to cleanup watchdog handlers. Right now,
kernel/watchdog.c implements both softlockup and hardlockup detectors.
Softlockup code is generic. Hardlockup code is arch specific. S
On 10/31/2016 07:15 AM, Masahiro Yamada wrote:
Hi Matthias,
Can you pick up this for your next pull request?
Sure, pushed to v4.9-next/kconfig
Next time please don't forget to send your patches to the mediatek
mailinglist:
linux-media...@lists.infradead.org
This makes it easier for me
When root activates a swap partition whose header has the wrong endianness,
nr_badpages elements of badpages are swabbed before nr_badpages has been
checked, leading to a buffer overrun of up to 8GB.
This normally is not a security issue because it can only be exploited by
root (more specifically,
On 10/31/2016 4:00 PM, Don Zickus wrote:
On Wed, Oct 26, 2016 at 09:02:19AM -0700, Babu Moger wrote:
This is an attempt to cleanup watchdog handlers. Right now,
kernel/watchdog.c implements both softlockup and hardlockup detectors.
Softlockup code is generic. Hardlockup code is arch specific. S
On Mon, Oct 31, 2016 at 07:34:49PM +0100, Willy Tarreau wrote:
> On Mon, Oct 31, 2016 at 11:52:49AM -0600, Greg Kroah-Hartman wrote:
> > Based on the discussion at the kernel summit a few hours ago, here's a
> > quick bug-fix release for 4.4-stable to resolve an issue with 4.4.29 and
> > older kern
On Mon, Oct 31, 2016 at 01:49:28PM -0700, Guenter Roeck wrote:
> On Mon, Oct 31, 2016 at 11:52:49AM -0600, Greg Kroah-Hartman wrote:
> > Based on the discussion at the kernel summit a few hours ago, here's a
> > quick bug-fix release for 4.4-stable to resolve an issue with 4.4.29 and
> > older kern
On Mon, Oct 31, 2016 at 06:21:12PM -0200, Marcos Paulo de Souza wrote:
> Without this patch, the Asus X45U wireless card can't be turned
> on (hard-blocked), but after a suspend/resume it just starts working.
>
> Following this bug report[1], there are other cases like this one, but
> this Asus is
* Daniel Micay:
> -fstack-stack is supposed to handle a single guard by default, and
> that's all there is for thread stacks by default.
Okay, then I'll really have to look at the probing offsets again.
It's been on my to-do list since about 2012, and arguably, it *is* a
user-space thing.
And I
On Mon 2016-10-31 13:22:18, Matt Ranostay wrote:
> On Tue, Oct 25, 2016 at 11:47 AM, Matt Ranostay wrote:
> > On Mon, Oct 24, 2016 at 1:14 PM, Pavel Machek wrote:
> >> On Mon 2016-10-24 12:58:25, Matt Ranostay wrote:
> >>> Pavel + Sebastian this is the patchset that need I some input on :)
> >>
>
On 10/31/2016 4:19 AM, Felipe Balbi wrote:
>
> Hi,
>
> John Stultz writes:
>> I had seen some odd behavior with HiKey's usb-gadget interface
>> that I finally seemed to have chased down. Basically every other
>> time I pluged in the OTG port, the gadget interface would
>> properly initialize. Th
On Wed, Sep 21, 2016 at 06:38:05PM -0400, Christopher Covington wrote:
> The Qualcomm Technologies QDF2432 SoC does not support accesses smaller
> than 32 bits to the PCI configuration space. Register the appropriate
> quirk.
>
> Signed-off-by: Christopher Covington
Hi Christopher,
Can you reba
An early preview release Git v2.11.0-rc0 is now available for
testing at the usual places. It is comprised of 617 non-merge
commits since v2.10.0, contributed by 64 people, 14 of which are
new faces.
An updated, slightly slipped from the original, schedule is found at
http://tinyurl.com/gitCal an
On Mon, Oct 31, 2016 at 04:21:55PM +, Deucher, Alexander wrote:
> > -Original Message-
> > From: Larry Finger [mailto:larry.fin...@gmail.com] On Behalf Of Larry Finger
> > Sent: Monday, October 31, 2016 12:41 AM
> > To: Linus Torvalds
> > Cc: linux-kernel@vger.kernel.org; driver-de...@v
On Mon, Oct 31, 2016 at 03:41:44PM -0500, Bjorn Helgaas wrote:
> On Wed, Oct 26, 2016 at 04:30:16PM +0200, Johannes Thumshirn wrote:
> > The Read Completion Boundary bit must only be set on a device or endpoint if
> > it is set on the upstream bridge.
>
> Please include the spec reference and a st
Ok, Ubuntu 16.04.1 is running on the box now, no issues so far. Any
special workload I should run?
No, will simply crash without running something special! If you get no
issues then that is bad news. I get frequent and repeatable crashes. I
forgot to mention that all those crashes occur at pro
Smack has always used extended attributes to identify
the security information used to make access control
decisions on packet delivery. The two attributes
security.SMACK64_IPIN and security.SMACK64_IPOUT
contain the label used for inbound and outbound
checks respectively. A process with CAP_MAC_AD
On Mon, Oct 31, 2016 at 03:22:36PM -0400, Yazen Ghannam wrote:
> For both patches?
Yap, I ran them both. But since you're going to change stuff again, I'll
run v3 too so don't add the tag yet.
Thanks.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham No
On Mon, 2016-10-31 at 22:38 +0100, Florian Weimer wrote:
> * Daniel Micay:
>
> > -fstack-stack is supposed to handle a single guard by default, and
> > that's all there is for thread stacks by default.
>
> Okay, then I'll really have to look at the probing offsets again.
> It's been on my to-do l
On Mon, Oct 31, 2016 at 1:58 PM, Mauro Carvalho Chehab
wrote:
> Em Mon, 31 Oct 2016 14:17:59 -0600
> Mauro Carvalho Chehab escreveu:
>
>> Em Mon, 31 Oct 2016 13:15:24 -0600
>> Jonathan Corbet escreveu:
>>
>> > On Mon, 31 Oct 2016 11:51:20 -0700
>> > Jim Davis wrote:
>> >
>> > > Running make pdf
On Mon, Oct 31, 2016 at 10:13:03PM +0100, Pavel Machek wrote:
> On Mon 2016-10-31 14:47:39, Mark Rutland wrote:
> > On Mon, Oct 31, 2016 at 09:27:05AM +0100, Pavel Machek wrote:
> > > > On Fri, Oct 28, 2016 at 01:21:36PM +0200, Pavel Machek wrote:
> > > > > > Has this been tested on a system vulner
* Daniel Micay:
> On Mon, 2016-10-31 at 22:38 +0100, Florian Weimer wrote:
>> * Daniel Micay:
>>
>> > -fstack-stack is supposed to handle a single guard by default, and
>> > that's all there is for thread stacks by default.
>>
>> Okay, then I'll really have to look at the probing offsets again.
On Mon, Oct 31, 2016 at 06:21:12PM -0200, Marcos Paulo de Souza wrote:
> Without this patch, the Asus X45U wireless card can't be turned
> on (hard-blocked), but after a suspend/resume it just starts working.
>
> Following this bug report[1], there are other cases like this one, but
> this Asus is
On 10/31/2016 09:34 PM, Adrian Hunter wrote:
> On 31/10/16 13:59, Jaehoon Chung wrote:
>> On 10/28/2016 05:12 PM, Ulf Hansson wrote:
>>> On 25 October 2016 at 21:58, Zach Brown wrote:
On some systems the sdhci capabilty registers are incorrect for one
reason or another.
The sdh
On 1 November 2016 at 07:25, Jes Sorensen wrote:
> John Heenan writes:
>> The rtl8723bu wireless IC shows evidence of a more agressive approach to
>> power saving, powering down its RF side when there is no wireless
>> interfacing but leaving USB interfacing intact. This makes the wireless
>> IC
--
Geschäftsvorschlag!!!
Ich vermute das diese E-Mail eine Überraschung für Sie sein wird, aber
es ist wahr.Ich bin bei einer routinen Überprüfung in meiner Bank (First
National Bank von Süd Afrika) wo ich arbeite, auf einem Konto gestoßen,
was nicht in anspruch genommen worden ist, wo derz
CR0.TS is cleared by a direct CR0 write in fpu__init_cpu_generic().
We don't need to call clts() two more times right after that.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/fpu/init.c | 18 --
1 file changed, 18 deletions(-)
diff --git a/arch/x86/kernel/fpu/init.c b/arch
Now that lazy FPU is gone, we don't use CR0.TS (except possibly in
KVM guest mode). Remove irq_ts_save(), irq_ts_restore(), and all of
their callers.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/fpu/api.h | 10 --
arch/x86/kernel/fpu/core.c | 29 --
don't use CR0.TS. Make it an error rather than making nonsensical
changes to the FPU state.
(The cond_local_irq_enable() appears to have been pointless, too.)
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/traps.c | 20
1 file changed, 16 insertions(+), 4 deletions(-)
It has no callers any more, and it was always a bit confusing, as
there is no STTS instruction.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/special_insns.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/include/asm/special_insns.h
b/arch/x86/include/asm/special_insns.
Now that Linux never sets CR0.TS, lguest doesn't need to support it.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/lguest_hcall.h | 1 -
arch/x86/lguest/boot.c | 17 +++--
drivers/lguest/hypercalls.c | 4
drivers/lguest/lg.h | 1
fpu__init_check_bugs() runs long after the early FPU init, so CR0.TS
will be clear by the time it runs. The save-and-restore dance would
have been unnecessary anyway, though, as kernel_fpu_begin() would
have been good enough.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/fpu/bugs.c | 7 ---
Now that x86 always uses eager fpu switching on the host, there's no
need for KVM to manipulate the host's CR0.TS.
This should be both simpler and faster.
Signed-off-by: Andy Lutomirski
---
arch/x86/kvm/vmx.c | 12
arch/x86/kvm/x86.c | 5 -
2 files changed, 4 insertions(+), 13
The kernel doesn't use clts() any more. Remove it and all of its
paravirt infrastructure.
A careful reader may notice that xen_clts() appears to have been
buggy -- it didn't update xen_cr0_value.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/paravirt.h | 5 -
arch/x86/incl
Hi,
On 10/30/2016 02:43 PM, Steven Haigh wrote:
Thanks for the feedback.
The difficult part here is that these are not my drivers, but are both
GPL - and I feel should be included upstream.
While I'm not a C coder, I may be able to do minor changes, but this was
my best effort of putting somet
We don't do anything useful with CR0.TS anymore, so remove most of
our support for it.
I havne't meaningfully tested lguest because I can't get it to work
even without these patches.
Andy Lutomirski (8):
fpu/init: Get rid of two redundant clts() calls
fpu/bugs: Stop saving and restoring CR0.T
Hi Lee,
On 10/31/2016 03:02 AM, Lee Jones wrote:
On Thu, 27 Oct 2016, ttha...@opensource.altera.com wrote:
From: Thor Thayer
Add the Altera Arria10 DevKit System Resource Monitor functionality
to the MFD device.
Signed-off-by: Thor Thayer
---
v2 Change from -mon to -monitor for clarity
--
On Mon, Oct 31, 2016 at 05:25:12PM -0400, Jes Sorensen wrote:
> As mentioned previously, if this is to be changed here, it has to be
> matched in the _stop section too. It also has to be investigated exactly
> why this matters for 8723bu. It is possible this matters for other
> devices, but we need
On Thu 27 Oct 16:23 PDT 2016, Stephen Boyd wrote:
> From what I can tell by looking at the android 3.10 kernel
> sources for msm8974, this isn't actually a reserved region.
> Instead it's marked as "unused" for reserved regions. Let's
> remove it so we get back a good chunk of memory.
Acked-by: B
On Mon, Oct 31, 2016 at 2:32 PM, Jann Horn wrote:
> When root activates a swap partition whose header has the wrong endianness,
> nr_badpages elements of badpages are swabbed before nr_badpages has been
> checked, leading to a buffer overrun of up to 8GB.
>
> This normally is not a security issue
Hello Russell,
On 10/31/2016 4:02 AM, Russell King - ARM Linux wrote:
The subject line on this patch is misleading - it's not only ARM64
specific...
Thank you for the feedback!
I only put ARM64 in the subject line because this patch only really adds
guest SEA support for the ARM64 KVM code. T
501 - 600 of 761 matches
Mail list logo
