On Mon, 1 Dec 2014 19:51:18 -0600
Felipe Balbi wrote:
> On Tue, Dec 02, 2014 at 01:13:38AM +0200, Aaro Koskinen wrote:
> > Hi,
> >
> > On Mon, Dec 01, 2014 at 02:09:14PM +, One Thousand Gnomes wrote:
> > > > Well the nightmare userspace switch from ttyS to ttyO few years ago is
> > > >
On Thu, Dec 04, 2014 at 02:56:31PM +, Dave Jones wrote:
> On Thu, Dec 04, 2014 at 10:51:03AM +, Will Deacon wrote:
>
> > and, as before, it has a weird child process that I can't backtrace:
> >
> > trinity-c1 R running task0 861811 0x
> > Call trace:
>
>
Hi,
2014-12-05 13:52 GMT+01:00 Yunzhi Li :
> Add dt nodes for rk3288 usb PHY.
Could you give more context about the changes in the long description ?
Usually, you need a short and a long description for a commit.
For example:
short: "ARM: dts: rockchip: add rk3288 usb PHY"
long: "This patch
Disable the Exynos IOMMU on ARMv8-A architecture so the build won't fail.
The Exynos7 is not supported yet by Exynos IOMMU driver.
This fixes following build errors on ARMv8 (allmodconfig, allyesconfig):
drivers/iommu/exynos-iommu.c: In function ‘pgtable_flush’:
Fixed the checkpatch warning:
Missing a blank line after declarations
Signed-off-by: Athira Lekshmi
---
drivers/watchdog/mixcomwd.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/watchdog/mixcomwd.c b/drivers/watchdog/mixcomwd.c
index be86ea3..03b7612e 100644
---
From: Shridhar Rasal
This patch adds a new devfreq governor, watermark simple. The
governor decides next frequency naively by selecting the previous
frequency in the frequency table if we received low watermark
- or the next frequency in case we received high watermark.
Signed-off-by: Shridhar
From: Shridhar Rasal
This patch adds support for watermark events. These events inform
the governor that the device load has gone below (low watermark) or
above (high watermark) certain load value.
Signed-off-by: Shridhar Rasal
Signed-off-by: Arto Merilainen
---
drivers/devfreq/devfreq.c |
(Sorry for the spam. I am resending the series because I noted that
some of the email addresses were mistyped)
Currently main mechanism to implement scaling using devfreq is
polling and the device profile is free to set polling interval.
However, in many cases this approach is not optimal; We may
This patch adds a new watermark governor that actively alters the
watermark values based on the current frequency and target load.
The governor takes target load as a given property (80% by default)
and every time when the governor re-estimation is triggered, the
governor checks the current load
Hi Preeti,
Moving this out of the architecture code looks good to me!
I have a couple of minor comments below.
On Fri, Dec 05, 2014 at 12:47:57PM +, Preeti U Murthy wrote:
> Commit 5d1638acb9f62fa7 added a hrtimer based broadcast mode for those
> platforms in which local timers stop when
Hi,
Some quick comments
2014-12-05 13:52 GMT+01:00 Yunzhi Li :
> This patche to add a generic PHY driver for ROCKCHIP usb PHYs,
> currently this driver can support RK3288. The RK3288 SoC have
> three independent USB PHY IPs which are all configured through a
> set of registers located in the GRF
On Wed, 3 Dec 2014 11:41:44 +0100
Richard Cochran wrote:
> On Wed, Dec 03, 2014 at 09:17:37AM +0100, Richard Weinberger wrote:
> > Come on guys, get a cup of coffee and relax a bit...
>
> I am relaxed, especially after I had a good laugh reading this:
>
>On a less related note, I hope you
From: Shridhar Rasal
This patch adds a new devfreq governor, watermark simple. The
governor decides next frequency naively by selecting the previous
frequency in the frequency table if we received low watermark
- or the next frequency in case we received high watermark.
Signed-off-by: Shridhar
This patch adds a new watermark governor that actively alters the
watermark values based on the current frequency and target load.
The governor takes target load as a given property (80% by default)
and every time when the governor re-estimation is triggered, the
governor checks the current load
From: Shridhar Rasal
This patch adds support for watermark events. These events inform
the governor that the device load has gone below (low watermark) or
above (high watermark) certain load value.
Signed-off-by: Shridhar Rasal
Signed-off-by: Arto Merilainen
---
drivers/devfreq/devfreq.c |
Currently main mechanism to implement scaling using devfreq is
polling and the device profile is free to set polling interval.
However, in many cases this approach is not optimal; We may
unnecessarily use CPU time to determine load on engine that
is idle most of time - or we may simply read load
(I somehow managed to review one patch twice instead of this one ...)
2014-12-04 16:57+0100, Paolo Bonzini:
> From: Wanpeng Li
>
> Expose the XSAVES feature to the guest if the kvm_x86_ops say it is
> available.
>
> Signed-off-by: Wanpeng Li
> Signed-off-by: Paolo Bonzini
> ---
Reviewed-by:
> From: David Hildenbrand [...
> > > This should be likely() instead of unlikely(), no?
> > > I'd rather write this
> > >
> > > if (pagefault_disabled())
> > > return;
> > > __might_sleep(file, line, 0);
> > >
> > > and leave the likely stuff completely away.
> >
> > Makes perfect
Athira,
On Fri, Dec 05, 2014 at 06:29:00PM +0530, Athira Lekshmi wrote:
> Fixed the checkpatch warning:
> Missing a blank line after declarations
>
> Signed-off-by: Athira Lekshmi
> ---
> drivers/watchdog/mixcomwd.c |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
Please wrap your message - replying to a message which looks like this in
my editor is far from easy, and gives me much more work to /manually/
reformat it before I can reply to it:
On Fri, Dec 05, 2014 at 12:56:45PM +, Hante Meuleman wrote:
> The problem is with data coming from device, so
> 2.a. If task A has sufficient capabilities to send signals to task B, then
> task A is already in position to do anything it wants with task B, including
> killing it outright.
Not entirely true.
- We have securirty models like SELinux
- We have namespaces and being able to send an fd between
On Fri, Dec 05, 2014 at 08:55:59AM +0800, weiyj...@163.com wrote:
> From: Wei Yongjun
>
> Add the missing unlock before return from function i915_gem_init_hw()
> in the error handling case.
>
> Signed-off-by: Wei Yongjun
Applied, thanks for the patch. Two minor comments:
- Please mention the
Tanya,
Am 05.12.2014 um 14:09 schrieb Tanya Brokhman:
> On 11/24/2014 3:20 PM, Richard Weinberger wrote:
>> ubi_wl_get_peb() has two problems, it reads the pool
>> size and usage counters without any protection.
>> While reading one value would be perfectly fine it reads multiple
>> values and
> From: Andy Lutomirski [mailto:l...@amacapital.net]
> Sent: Thursday, December 4, 2014 7:10 PM
> To: Berthier, Emmanuel
> Cc: Thomas Gleixner; H. Peter Anvin; X86 ML; Jarzmik, Robert; LKML
> Subject: Re: [PATCH v2] [LBR] Dump LBRs on Exception
> >> And the general problem with this approach (even
I'll fix these (an run sparse).
/Jarkko
On Thu, Dec 04, 2014 at 09:19:21PM +0100, Peter Hüwe wrote:
> Am Donnerstag, 4. Dezember 2014, 06:55:17 schrieb Jarkko Sakkinen:
> > tpm_crb is a driver for TPM 2.0 Command Response Buffer (CRB) Interface
> > as defined in PC Client Platform TPM Profile
On 11/24/2014 3:20 PM, Richard Weinberger wrote:
ubi_wl_get_peb() has two problems, it reads the pool
size and usage counters without any protection.
While reading one value would be perfectly fine it reads multiple
values and compares them. This is racy and can lead to incorrect
pool handling.
On Thu, Dec 04, 2014 at 10:46:25PM +0100, Peter Hüwe wrote:
> Am Donnerstag, 4. Dezember 2014, 06:55:18 schrieb Jarkko Sakkinen:
> > From: Will Arthur
> >
> > Detect TPM 2.0 by using the extended STS (STS3) register. For TPM 2.0,
> > instead of calling tpm_get_timeouts(), assign duration and
On Thu, Dec 04, 2014 at 03:25:12PM +, Scot Doyle wrote:
> Hi Jarkko,
>
> On Thu, 4 Dec 2014, Jarkko Sakkinen wrote:
> > From: Will Arthur
> >
> > Detect TPM 2.0 by using the extended STS (STS3) register. For TPM 2.0,
> > instead of calling tpm_get_timeouts(), assign duration and timeout
> >
On Fri, Dec 5, 2014 at 2:06 PM, Johan Hovold wrote:
> On Fri, Dec 05, 2014 at 01:51:17PM +0200, Octavian Purdila wrote:
>> On Fri, Dec 5, 2014 at 12:17 PM, Johan Hovold wrote:
>> > On Thu, Nov 27, 2014 at 01:57:14PM +0200, Octavian Purdila wrote:
>> >
>> >> @@ -753,11 +759,42 @@ static const
On 05/12/2014 09:50, Gerd Hoffmann wrote:
> A few comments on the kernel stuff (brief look so far, also
> compile-tested only, intel gfx on my test machine is too old).
>
> * Noticed the kernel bits don't even compile when configured as
>module. Everything (vgt, i915, kvm) must be
On 05/12/14 13:34, Javier Martinez Canillas wrote:
> Hello Sylwester,
>
> On 12/05/2014 12:22 PM, Sylwester Nawrocki wrote:
>>> >> Tested-by: Javier Martinez Canillas
>> >
>> > Can you confirm sound works with this patch on exynos5420 ? Or does
>> > your Tested-by refer only to successful
Jani,
On Fri, Dec 05, 2014 at 02:17:42PM +0200, Jani Nikula wrote:
> Release struct_mutex if init_rings() fails.
>
> This is a regression introduced in
> commit 35a57ffbb10840af219eeaf64718434242bb7c76
> Author: Daniel Vetter
> Date: Thu Nov 20 00:33:07 2014 +0100
>
> drm/i915: Only init
On Fri, Dec 05, 2014 at 01:43:01PM +0100, Arend van Spriel wrote:
> Ok. You already had a peek in our code checking the memory barriers, which
> does not have the dma_sync_single_for_cpu() "workaround" yet. So here some
> more background. The problem is in DMA_FROM_DEVICE direction. Because of the
Fixed the checkpatch warning:
Missing a blank line after declarations
Signed-off-by: Athira Lekshmi
---
drivers/watchdog/mixcomwd.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/watchdog/mixcomwd.c b/drivers/watchdog/mixcomwd.c
index be86ea3..03b7612e 100644
---
The problem is with data coming from device, so DMA from device to host. The
DMA takes place from device local memory to host memory, where the host memory
is allocated with dma_alloc_coherent, which we thought should not be cached.
The host is an ARM (as is the device). The data being DMA'ed
This patche to add a generic PHY driver for ROCKCHIP usb PHYs,
currently this driver can support RK3288. The RK3288 SoC have
three independent USB PHY IPs which are all configured through a
set of registers located in the GRF (general register files)
module.
Signed-off-by: Yunzhi Li
---
Hi Hans,
On Fri, Dec 5, 2014 at 12:24 PM, Hans Verkuil wrote:
> Hi Prabhakar,
>
> Sorry, there are still a few items that need to be fixed.
> If you can make a v4 with these issues addressed, then I can still make a
> pull request, although it depends on Mauro whether it is still accepted for
>
Patches to add support for Rockchip usb phys.Add a new Rockchip
usb phy driver and modify dwc2 controller driver to make dwc2
platform devices support a generic PHY framework driver. This
patch set has been tested on my rk3288-evb and power off the usb
phys would reduce about 60mW power budget in
Hi John,
Here's what should be the last bluetooth-next pull request for 3.19.
It's rather large but the majority of it is the Low Energy Secure
Connections feature that's part of the Bluetooth 4.2 specification. The
specification went public only this week so we couldn't publish the
corresponding
Document the bindings of the Rockchip usb PHY driver.
Signed-off-by: Yunzhi Li
---
.../devicetree/bindings/phy/rockchip-usb-phy.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/rockchip-usb-phy.txt
diff --git
Get PHY parameters from devicetree and power off usb PHY during
system suspend.
Signed-off-by: Yunzhi Li
---
drivers/usb/dwc2/gadget.c | 33 -
drivers/usb/dwc2/platform.c | 34 ++
2 files changed, 46 insertions(+), 21
Add dt nodes for rk3288 usb PHY.
Signed-off-by: Yunzhi Li
---
arch/arm/boot/dts/rk3288.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index 874e66d..a663c4c 100644
--- a/arch/arm/boot/dts/rk3288.dtsi
+++
>> The data structure element "sha1" was assigned a null pointer by the
>> mppe_alloc() after a function call "crypto_alloc_hash" failed.
>
> This patch is also buggy.
Do you really want to keep a variable reset after a detected failure?
Regards,
Markus
--
To unsubscribe from this list: send
On 05/12/14 12:23, David Howells wrote:
> Dmitry Kasatkin wrote:
>
>> sign-file.c produce lots of annoying noise.
> How did you get it to produce that?
>
> David
>
With just "make all" on Ubuntu.
- Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
Commit 5d1638acb9f62fa7 added a hrtimer based broadcast mode for those
platforms in which local timers stop when CPUs enter deep idle states. The
commit expected the platforms to register for this mode explicitly when they
lacked a better external device to wake up CPUs in deep idle. Given that
>> The data structure element "arc4" was assigned a null pointer by the
>> mppe_alloc() function if a previous function call "crypto_alloc_blkcipher"
>> failed.
>
> crypto_alloc_blkcipher() returns error pointers and not NULL.
That is true.
> This patch creates a bug.
Please explain: How?
Hi Krzysztof,
On 05/12/14 12:00, Krzysztof Kozlowski wrote:
> Audio subsystem clocks are located in separate block. If clock for this
> block (from main clock domain) 'mau_epll' is gated then any read or
> write to audss registers will block.
>
> This was observed on Exynos 5420 platforms
On 05-12-14 10:45, Russell King - ARM Linux wrote:
On Fri, Dec 05, 2014 at 10:22:22AM +0100, Arend van Spriel wrote:
For our brcm80211 development we are working on getting brcmfmac driver
up and running on a Broadcom ARM-based platform. The wireless device is
a PCIe device, which is hooked up
On 12/5/14, Arseny Solokha wrote:
> From: Arseny Solokha
>
> When DMA-API debugging is enabled in the kernel, it spews the following
> upon upping the link:
>
> WARNING: at lib/dma-debug.c:1135
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW O 3.18.0-rc7 #1
> task:
BTW, the impact of this bug is that the panic cannot reboot the
machine and it prints an infinite stream of the error messages. The
panic goes on forever because there's a for(;;) loop in
__mutex_lock_common(), so we enter __schedule() again and again.
Thanks
Rui
On 12/4/14, ruiv.w...@gmail.com
If the master clock supports programmable rates, program it to generate
the desired frequency. Only apply constraints when the clock is fixed.
This allows proper clock generation for both 44100 and 48000 Hz based
sampling rates if the platform supports it.
The clock frequency must be set before
Hello Sylwester,
On 12/05/2014 12:22 PM, Sylwester Nawrocki wrote:
>> Tested-by: Javier Martinez Canillas
>
> Can you confirm sound works with this patch on exynos5420 ? Or does
> your Tested-by refer only to successful booting ?
>
I tested latest linux-next + "clk: samsung: Fix double add of
>From 8579fc072fda603c4ae472cc3f0390d61556ac01 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Fri, 5 Dec 2014 21:22:22 +0900
Subject: [PATCH] sched: Fix potential call to __ffs(0) in sched_show_task()
"struct task_struct"->state is "volatile long" and __ffs() warns that
"Undefined if no bit
On Fri, Dec 05, 2014 at 12:24:49PM +, Arnd Bergmann wrote:
> On Friday 05 December 2014 11:05:07 Catalin Marinas wrote:
> >
> > > Should we add support for 64k-pages in the arm32 kernel as well now?
> >
> > 32-bit LPAE doesn't support 64K pages but IIRC the classic MMU does
> > (though I
On Thu, Dec 04, 2014 at 10:35:24PM +, Luis de Bethencourt wrote:
> The previous patch switched some dev functions to move the string to a second
> line. Doing this for all similar functions because it makes the driver easier
> to read if all similar lines use the same criteria.
>
>
Hello.
On 12/4/2014 11:23 PM, Al Viro wrote:
Looks like you've erred in the subject as you seem to be getting rid of
copy_page_{to|from}_iter_bvec() instead of bvec_copy_page_{to|from}_iter()...
From: Al Viro
Just have copy_page_{to,from}_iter() fall back to kmap_atomic +
Introduce two helper functions to savely read and write unsigned long
values from or to memory without crashing the system in case of access
failures.
These helpers can be used instead of open coded uses of __get_user()
and __put_user() avoiding the need to do casts to fix sparse warnings.
Use
On Fri, Dec 5, 2014 at 6:40 PM, Mark Rutland wrote:
> Hi,
>
> On Thu, Dec 04, 2014 at 11:34:15AM +, Chunyan Zhang wrote:
>> Spreadtrum is a rapid growing chip vendor providing smart phone total
>> solutions.
>>
>> Sharkl64 Platform is nominated as a SoC infrastructure that supports 4G/3G/2G
On Friday 05 December 2014 11:05:07 Catalin Marinas wrote:
>
> > Should we add support for 64k-pages in the arm32 kernel as well now?
>
> 32-bit LPAE doesn't support 64K pages but IIRC the classic MMU does
> (though I have to check whether it was optional). But it's not feasible
> to enable this
On Fri, Dec 05, 2014 at 09:45:08AM +, Russell King - ARM Linux wrote:
> On Fri, Dec 05, 2014 at 10:22:22AM +0100, Arend van Spriel wrote:
> > For our brcm80211 development we are working on getting brcmfmac driver
> > up and running on a Broadcom ARM-based platform. The wireless device is
> >
Hi Prabhakar,
Sorry, there are still a few items that need to be fixed.
If you can make a v4 with these issues addressed, then I can still make a
pull request, although it depends on Mauro whether it is still accepted for
3.19.
On 12/04/2014 12:12 AM, Lad, Prabhakar wrote:
> From: Benoit Parrot
On Thu, Dec 04, 2014 at 11:20:21PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Thu, 4 Dec 2014 22:42:30 +0100
>
> The data structure element "sha1" was assigned a null pointer by the
> mppe_alloc() after a function call "crypto_alloc_hash" failed.
This patch is also buggy.
On Thu, Dec 04, 2014 at 11:18:41PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Thu, 4 Dec 2014 22:33:34 +0100
>
> The data structure element "arc4" was assigned a null pointer by the
> mppe_alloc() function if a previous function call "crypto_alloc_blkcipher"
> failed.
No.
On 12/03/2014, 08:47 PM, Guenter Roeck wrote:
> On Wed, Dec 03, 2014 at 12:26:07PM +0100, Jiri Slaby wrote:
>> This is the start of the stable review cycle for the 3.12.34 release.
>> There are 101 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues
Hi Thomas,
On Fri, Dec 05, 2014 at 08:48:28AM -, Thomas Gleixner wrote:
> That solves the issue at hand, but the iommu setup stays a tangled
> maze with completely non obvious setup mechanisms depending on the
> options (iommu on/off - irq remapping on/off).
Thanks for this nice cleanup, for
On Fri, 05 Dec 2014, Jeremiah Mahler wrote:
> There are other places in i915_gem_init_hw() where it returns without
> unlocking the mutex. Why is it only necessary here and not any of the
> other places?
There's probably some rebase/merge confusion going on. The following
patch is against
Release struct_mutex if init_rings() fails.
This is a regression introduced in
commit 35a57ffbb10840af219eeaf64718434242bb7c76
Author: Daniel Vetter
Date: Thu Nov 20 00:33:07 2014 +0100
drm/i915: Only init engines once
Reported-by: Wei Yongjun
Signed-off-by: Jani Nikula
---
On Fri, 05 Dec 2014, Jeremiah Mahler wrote:
> There are other places in i915_gem_init_hw() where it returns without
> unlocking the mutex. Why is it only necessary here and not any of the
> other places?
There's probably some rebase/merge confusion going on. The following
patch is against
From: David Hildenbrand [...
> > This should be likely() instead of unlikely(), no?
> > I'd rather write this
> >
> > if (pagefault_disabled())
> > return;
> > __might_sleep(file, line, 0);
> >
> > and leave the likely stuff completely away.
>
> Makes perfect sense!
>From my
On Fri, Dec 05, 2014 at 01:51:17PM +0200, Octavian Purdila wrote:
> On Fri, Dec 5, 2014 at 12:17 PM, Johan Hovold wrote:
> > On Thu, Nov 27, 2014 at 01:57:14PM +0200, Octavian Purdila wrote:
> >
> >> @@ -753,11 +759,42 @@ static const struct usb_device_id dln2_table[] = {
> >>
> >>
On 05.12.14 11:39, Arnd Bergmann wrote:
> On Thursday 04 December 2014 15:48:50 Olof Johansson wrote:
>> On Thu, Dec 4, 2014 at 3:41 PM, Alexander Graf wrote:
>>> On 04.12.14 22:15, Olof Johansson wrote:
On Thu, Dec 4, 2014 at 7:46 AM, Alexander Graf wrote:
> With binutils 2.25 the
This patch adds other ACPI ids from Windows inf driver which should be handled
by dell-smo8800 driver. ACPI devices have same structure -- one IRQ number.
This patch also updates description of module.
Signed-off-by: Pali Rohár
---
drivers/platform/x86/Kconfig|4 ++--
On Thu, Dec 04, 2014 at 12:03:05PM +, Catalin Marinas wrote:
> On Mon, Sep 15, 2014 at 12:33:25PM +0100, Russell King - ARM Linux wrote:
> > On Mon, Sep 15, 2014 at 07:07:20PM +0800, Wang, Yalin wrote:
> > > @@ -636,6 +646,11 @@ static int keep_initrd;
> > > void free_initrd_mem(unsigned long
Hi all,
Changes since 20141204:
New tree: access_once
Dropped tree: access_once
The v4l-dvb tree gained a conflict against the arm-soc tree.
The kbuild tree gained a conflict against the arm-soc tree.
The drm tree gained conflicts against Linus' tree.
The usb tree still had its build
On Fri, Dec 05, 2014 at 01:47:34PM +0900, Joshua I. James wrote:
> From: "Joshua I. James"
>
> Fixed style errors identified by checkpatch.
>
> Output of checkpatch:
> WARNING: Missing a blank line after declarations
> WARNING: line over 80 characters
> ERROR: spaces required around that '=='
This patch adds support for configuring keyboard backlight settings on supported
Dell laptops. It exports kernel leds interface and uses Dell SMBIOS tokens or
keyboard class interface.
With this patch it is possible to set:
* keyboard backlight level
* timeout after which will be backlight
On Fri, Dec 05, 2014 at 04:25:22PM +0530, Athira Lekshmi wrote:
> Fixed the checkpatch warning:
> Missing a blank line after declarations
this is not applying to next-20141204.
sudip
>
> Signed-off-by: Athira Lekshmi
> ---
> drivers/staging/octeon/ethernet-rx.c |1 +
> 1 file changed, 1
On Fri, Dec 5, 2014 at 12:17 PM, Johan Hovold wrote:
> On Thu, Nov 27, 2014 at 01:57:14PM +0200, Octavian Purdila wrote:
>
>> @@ -753,11 +759,42 @@ static const struct usb_device_id dln2_table[] = {
>>
>> MODULE_DEVICE_TABLE(usb, dln2_table);
>
> Place the new callbacks above the device id
Thank you for investigating. Your analysis matches what was intended to be
done. Regarding the cast, you're right, I'll improve it. My idea was that long
long is always 64bit, but when casting directly to long long I get a compiler
(when using C=2) warning: "warning: right shift by bigger than
> On Fri, Dec 05, 2014 at 12:18:07PM +0100, David Hildenbrand wrote:
> > -void might_fault(void)
> > +void __might_fault(const char *file, int line)
> > {
> > /*
> > * Some code (nfs/sunrpc) uses socket ops on kernel memory while
> > @@ -3710,21 +3710,16 @@ void might_fault(void)
> >
On Fri, Dec 05, 2014 at 12:18:07PM +0100, David Hildenbrand wrote:
> -void might_fault(void)
> +void __might_fault(const char *file, int line)
> {
> /*
>* Some code (nfs/sunrpc) uses socket ops on kernel memory while
> @@ -3710,21 +3710,16 @@ void might_fault(void)
>*/
>
> Subject: Re: [E1000-devel] [PATCH] ixgbe, ixgbevf: Add new mbox API to enable
> MC promiscuous mode
>
> On 11/27/2014 02:39 AM, Hiroshi Shimamoto wrote:
> > From: Hiroshi Shimamoto
> >
> > The limitation of the number of multicast address for VF is not enough
> > for the large scale server
On Fri, Dec 05, 2014 at 11:14:55AM +, Catalin Marinas wrote:
> On Thu, Dec 04, 2014 at 09:15:12PM +, Olof Johansson wrote:
> > On Thu, Dec 4, 2014 at 7:46 AM, Alexander Graf wrote:
> > > With binutils 2.25 the default alignment for 32bit arm sections changed to
> > > have everything 64k
Javier,
On 05/12/14 12:00, Krzysztof Kozlowski wrote:
> Audio subsystem clocks are located in separate block. If clock for this
> block (from main clock domain) 'mau_epll' is gated then any read or
> write to audss registers will block.
>
> This was observed on Exynos 5420 platforms (Arndale
include/linux/mm.h: In function 'is_vmalloc_addr':
include/linux/mm.h:367:14: warning: comparison between signed and unsigned
integer expressions [-Wsign-compare]
return addr >= VMALLOC_START && addr < VMALLOC_END;
^
Signed-off-by: Christophe Leroy
---
At the start of the thread we are changing the address limit, restoring it
to the default while exiting.
Signed-off-by: Sanjay Singh Rawat
---
drivers/usb/gadget/function/f_mass_storage.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/gadget/function/f_mass_storage.c
When size is equal to 1, the test is always true so lets eliminate both 0 and 1
at first.
include/asm-generic/termios-base.h: In function 'user_termio_to_kernel_termios':
include/asm-generic/termios-base.h:35:2: warning: comparison of unsigned
expression >= 0 is always true [-Wtype-limits]
if
This patch adds the pagefault_count to the thread_info of all
architectures. It will be used to count the pagefault_disable() levels
on a per-thread basis.
We are not reusing the preempt_count as this is per cpu on x86 and we want to
demangle pagefault_disable() from preemption in the future.
This patch introduces CONFIG_DEBUG_PAGEFAULT_COUNT, to detect over-/underflows
in the pagefault_count resulting from a wrong usage of pagefault_enable() and
pagefault_disable().
Signed-off-by: David Hildenbrand
---
include/linux/uaccess.h | 8 +++-
lib/Kconfig.debug | 9 +
I recently discovered that might_fault() doesn't call might_sleep() anymore.
Therefore bugs like:
spin_lock();
rc = copy_to_user(...);
spin_unlock();
would not be detected with CONFIG_DEBUG_ATOMIC_SLEEP. The code was changed to
disable false positives for code like:
pagefault_disable() and pagefault_enable() have to increment/decrement the
pagefault_count. We keep manipulating the preempt count to retain compability
to existing pagefault handlers. This has to be demangled in separate patches.
It is now possible to verify whether in a pagefault_disable()
Commit 662bbcb2747c ("mm, sched: Allow uaccess in atomic with
pagefault_disable()") removed might_sleep() checks for all user access code
(that uses might_fault()).
The reason was to disable wrong "sleep in atomic" warnings in the following
scenario:
pagefault_disable()
rc =
In general, non-atomic variants of user access functions may not sleep if
pagefaults are disabled.
Let's update all relevant comments in uaccess code. This also refelects the
might_sleep() checks in might_fault().
Signed-off-by: David Hildenbrand
---
arch/avr32/include/asm/uaccess.h | 12
On Thu, Dec 04, 2014 at 09:15:12PM +, Olof Johansson wrote:
> On Thu, Dec 4, 2014 at 7:46 AM, Alexander Graf wrote:
> > With binutils 2.25 the default alignment for 32bit arm sections changed to
> > have everything 64k aligned. Armv7 binaries built with this binutils version
> > run
Should the completely pointless supervisor_stack[] be removed as well?
I had a patch to do that but I never sent it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Fri, Dec 05, 2014 at 10:52:02AM +0100, Arnd Bergmann wrote:
> I'm still puzzled why you'd need a single dma_sync_single_for_cpu()
> after dma_alloc_coherent though, you should not need any. Is it possible
> that the driver accidentally uses __raw_readl() instead of readl()
> in some places and
On Fri, Dec 05, 2014 at 06:21:17PM +0800, Wang, Yalin wrote:
> This patch add KPF_ZERO_PAGE flag for zero_page,
> so that userspace process can notice zero_page from
> /proc/kpageflags, and then do memory analysis more accurately.
>
> Signed-off-by: Yalin Wang
> ---
> fs/proc/page.c
On Fri, Dec 05, 2014 at 10:39:40AM +, Arnd Bergmann wrote:
> On Thursday 04 December 2014 15:48:50 Olof Johansson wrote:
> > On Thu, Dec 4, 2014 at 3:41 PM, Alexander Graf wrote:
> > > On 04.12.14 22:15, Olof Johansson wrote:
> > >> On Thu, Dec 4, 2014 at 7:46 AM, Alexander Graf wrote:
> >
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
tools/testing/selftests/Makefile between commit 3ce51050fadd
("selftest: size: Add size test for Linux kernel") from the
kselftest-fixes tree and commit 4126d336d7c3 ("syscalls: add selftest
for execveat(2)") from the
Joshua,
On Fri, Dec 05, 2014 at 01:47:34PM +0900, Joshua I. James wrote:
> From: "Joshua I. James"
>
> Fixed style errors identified by checkpatch.
>
> Output of checkpatch:
> WARNING: Missing a blank line after declarations
> WARNING: line over 80 characters
> ERROR: spaces required around
601 - 700 of 1580 matches
Mail list logo
