Hi,
[auto build test WARNING on pm/linux-next]
[also build test WARNING on v4.7-rc7 next-20160722]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Jisheng-Zhang/PM-OPP-optimize
Em Thu, Jul 21, 2016 at 10:41:18PM -0500, Josh Poimboeuf escreveu:
> On Fri, Jul 22, 2016 at 09:23:02AM +1000, Stephen Rothwell wrote:
> > It just looks like objtool was not written with cross compilation in
> > mind?
> I don't know yet what the specific problem is, but objtool should work
> fine
Greetings Guenter,
Thank you for reviewing my submission.
On 07/15/2016 06:40 PM, Guenter Roeck wrote:
> On 07/15/2016 05:18 PM, Joshua Clayton wrote:
>> Add new driver for Texas Instruments ADS1118 and and ADS1018.
>> This driver works with ADS1018, because of code borrowed
>> from asd1015, whic
Hi,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on next-20160722]
[cannot apply to v4.7-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/James-Simmons/staging
On Fri, Jul 15, 2016 at 10:29 PM, Arnd Bergmann wrote:
> Building without CONFIG_OF gives us these warnings for the broadcom
> pinctrl drivers:
>
> drivers/pinctrl/bcm/pinctrl-nsp-mux.c:356:20: error:
> 'pinconf_generic_dt_node_to_map_group' undeclared here (not in a function)
> drivers/pinctrl/
On Mon, Jul 18, 2016 at 7:20 PM, Ray Jui wrote:
> Update the iProc GPIO binding document to add new compatible strings
> "brcm,iproc-nsp-gpio" and "brcm,iproc-stingray-gpio" to support the
> iProc based GPIO controller used in the NSP and Stingray SoCs,
> respectively
>
> Signed-off-by: Ray Jui
On Mon, Jul 18, 2016 at 7:20 PM, Ray Jui wrote:
> The iProc GPIO controller is shared among multiple iProc based SoCs.
> In the NSP integration, the drive strength pinctrl function is
> disabled. In the integration of Stingray, pinctrl is handled by another
> block and this GPIO controller is sol
On 07/22/2016 04:32 PM, Alexander Potapenko wrote:
> On Thu, Jul 21, 2016 at 10:48 AM, Andrey Ryabinin
> wrote:
>>
>>
>> On 07/20/2016 09:43 PM, a...@linux-foundation.org wrote:
>>>
>>> The patch titled
>>> Subject:
>>> mm-kasan-switch-slub-to-stackdepot-enable-memory-quarantine-for-slub-f
On Fri, 22 Jul 2016 17:28:13 +1000
Greg Ungerer wrote:
> On 22/07/16 00:48, Nicolas Pitre wrote:
> > On Thu, 21 Jul 2016, Greg Ungerer wrote:
> >> Hi Nicolas,
> >>
> >> On 21/07/16 05:22, Nicolas Pitre wrote:
> >>> This series provides the necessary changes to allow "flat" executable
> >>> bi
On Thu, Jul 14, 2016 at 8:08 AM, Andrew Duggan wrote:
> Signed-off-by: Andrew Duggan
> ---
> This version includes Nick's suggestion of adding force to the device tree
> parameters so make it obvious that these parameters overwrite the
> default values set in the firware config.
Looks neat.
Rev
On Thu, Jul 21, 2016 at 9:00 PM, Yakir Yang wrote:
> Sean,
>
> Thanks for your fast respond :-)
>
> But this patch is not the latest one, I have upgraded this to "v1.1" version
> to fix the eDP can't be disabled problem:
> [PATCH v1.1 2/2] drm/bridge: analogix_dp: turn off the panel when eDP
>
On Sat, Jul 16, 2016 at 5:07 PM, Andreas Klinger wrote:
> On Marvell mv88f6180 with pin control driver one can not use multi
> purpose pins 35 through 44.
> I'm using this controller on an embedded board and i found that the
> pin multiplexing is not the same as in the hardware spezification.
> T
On Jul 22, 2016, at 6:55 AM, J. Bruce Fields wrote:
> On Fri, Jul 22, 2016 at 02:35:26AM -0400, Oleg Drokin wrote:
>>
>> On Jul 21, 2016, at 9:57 PM, J. Bruce Fields wrote:
>>
>>> On Thu, Jul 21, 2016 at 04:37:40PM -0400, Oleg Drokin wrote:
On Jul 21, 2016, at 4:34 PM, J. Bruce Field
On 21-07-16, 17:34, Steve Muckle wrote:
> On Fri, Jul 22, 2016 at 02:18:54AM +0200, Rafael J. Wysocki wrote:
> > > My thinking was that one of these two would be preferable:
> > >
> > > - Forcing ->target() drivers to install a ->resolve_freq callback,
> > > enforcing this at cpufreq driver init
This reverts commit 790d849bf811a8ab5d4cd2cce0f6fda92f6aebf2.
Using a v4.7-rc7 kernel on a HP ProLiant triggered following messages
pcc-cpufreq: (v1.10.00) driver loaded with frequency limits: 1200 MHz, 2800 MHz
cpufreq: ondemand governor failed, too long transition latency of HW, fallback
to
Hi Bharat,
On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote:
> Hi,
>
> I'm observing that on x86 BIOS successfully assigns memory if an End point
> requests
> BAR of size 16byte.
>
> But as per Spec:
> The minimum memory address range requested by a BAR is 128 bytes.
Can you
On 21-07-16, 17:44, Steve Muckle wrote:
> Going back and checking I see I was thinking of your suggestion that
> cpufreq_register_driver() check that only target() drivers offer a
> resolve_freq() callback. I put a comment for this in cpufreq.h but not a
> check - I could add a check in another pat
On Thu, Jul 21, 2016 at 10:31:46PM -0700, Alison Schofield wrote:
> Triggered buffer support uses the HDC100X's dual acquisition mode
> to read both humidity and temperature in one shot.
>
> Signed-off-by: Alison Schofield
> Cc: Daniel Baluta
> ---
Reviewing myself, changes coming in v3
- don't
Hi Thomas,
On Fri, Jul 22, 2016 at 3:04 PM, Thomas Gleixner wrote:
>
> Well, this really depends on the TIMEOUT value you have. The code now does
> implicit batching for larger timeouts by queueing the timers into wheels with
> coarse grained granularity. As long as your new TIMEOUT value ends up
On Fri, Jul 22, 2016 at 3:22 AM, Lee Jones wrote:
> Since 0b52297f228 ("reset: Add support for shared reset controls") the
> new Reset API now demands consumers choose either an *_exclusive or
> a *_shared line when requesting reset lines.
>
> Signed-off-by: Lee Jones
> ---
> drivers/gpu/drm/sti
On Wed, Jul 20, 2016 at 5:24 PM, Sebastian Andrzej Siewior
wrote:
> There is no need the ledtriger to be called *that* early in the hotplug
> process (+ with disabled interrupts). As explained by Jacek Anaszewski [0]
> there is no need for it.
> Therefore this patch moves it to the ONLINE/PREPARE
On Fri, Jul 22, 2016 at 7:45 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Fri, 22 Jul 2016 13:31:00 +0200
>
> The vfree() function performs also input parameter validation.
> Thus the test around the call is not needed.
>
> This issue was detected by using the Coccinelle software.
On Fri, Jul 22, 2016 at 5:32 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Fri, 22 Jul 2016 11:20:27 +0200
>
> The drm_gem_object_unreference_unlocked() function tests whether
> its argument is NULL and then returns immediately.
> Thus the test around the call is not needed.
>
> Thi
On Fri, Jul 22, 2016 at 8:54 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Fri, 22 Jul 2016 14:45:51 +0200
>
> The backlight_device_unregister() function tests whether its argument
> is NULL and then returns immediately.
> Thus the test around the call is not needed.
>
> This issue
On Fri, Jul 22, 2016 at 8:22 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Fri, 22 Jul 2016 14:14:54 +0200
>
> The drm_gem_object_unreference_unlocked() function tests whether
> its argument is NULL and then returns immediately.
> Thus the test around the call is not needed.
>
> Thi
On Tue, Jul 19, 2016 at 2:30 AM, Paul Gortmaker
wrote:
> This reverts commit b8c2b10a9bc0272a20e096852f8fbbf361749dda.
>
> This patch was in my queue at the same time that a conversion of
> the same driver from bool --> tristate was pending and merged.
>
> That is commit 337ea0fb1535 ("pinctrl: T
On Wed, Jul 20, 2016 at 6:13 AM, Paul Gortmaker
wrote:
> While working on some for-4.9 cleanups of linux/gpio/driver.h it was
> found that changes there caused build failures when walking all the
> ARM defconfigs, in ARM specific mach-* files.
(...)
> Paul Gortmaker (3):
> ARM: mach-omap2: remo
On Tue, Jul 19, 2016 at 11:08:24PM +0200, SF Markus Elfring wrote:
> > From: Markus Elfring
> > Date: Mon, 16 Nov 2015 08:20:36 +0100
> >
> > The mempool_destroy() function tests whether its argument is NULL
> > and then returns immediately. Thus the test around the calls is not needed.
> >
> >
Looks good. Thanks!
Reviewed-by: Sinclair Yeh
On Fri, Jul 22, 2016 at 01:45:40PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 22 Jul 2016 13:31:00 +0200
>
> The vfree() function performs also input parameter validation.
> Thus the test around the call is not needed.
>
On Thu, Jul 21, 2016 at 7:09 PM, James Morris wrote:
> On Thu, 21 Jul 2016, Paul Moore wrote:
>> James, assuming the overlayfs-next branch is pulled during the merge
>> window, can you rebase your linux-security#next branch to v4.8-rc1
>> once Linus tags it?
>
> Yep.
On Fri, Jul 22, 2016 at 3:05
If the call to acpi_ds_init_aml_walk() fails, then we have to undo the
walk state push done by acpi_ds_create_walk_state(). Otherwise, the new
walk state (which has just been freed) will remain on the thread's
walk_state_list and be dereferenced in acpi_ps_parse_aml() when we try
to get the new sta
On 22-07-16, 17:14, Andreas Herrmann wrote:
> diff --git a/drivers/cpufreq/pcc-cpufreq.c b/drivers/cpufreq/pcc-cpufreq.c
> index a7ecb9a..3f0ce2a 100644
> --- a/drivers/cpufreq/pcc-cpufreq.c
> +++ b/drivers/cpufreq/pcc-cpufreq.c
> @@ -555,8 +555,6 @@ static int pcc_cpufreq_cpu_init(struct cpufreq_p
From: Markus Elfring
Date: Fri, 22 Jul 2016 17:34:32 +0200
Further update suggestions were taken into account
after a patch was applied from static source code analysis.
Markus Elfring (4):
Delete unnecessary checks before two function calls
Delete unnecessary if statement in __etnaviv_gem_n
A typo in the previous commit to this file needs fixing.
Cc: Amitoj Kaur Chawla
Reported-by: kbuild test robot
Fixes: 6b4316aecec0 ("pinctrl: xway: Change structure initialisation to c99
style")
Signed-off-by: Linus Walleij
---
drivers/pinctrl/pinctrl-xway.c | 2 +-
1 file changed, 1 insertio
From: Markus Elfring
Date: Fri, 22 Jul 2016 15:56:15 +0200
The functions drm_gem_object_unreference_unlocked() and vunmap() perform
also input parameter validation.
Thus the tests around their calls are not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus
From: Markus Elfring
Date: Fri, 22 Jul 2016 16:45:22 +0200
Move a return statement into a block for successful function execution.
Omit a duplicate check for the local variable "ret" then at the end.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/etnaviv/etnaviv_gem.c | 6 +-
1 file cha
Paolo Bonzini writes:
>> Paolo Bonzini writes:
>>
>> > On 21/07/2016 00:25, Bandan Das wrote:
>> >> vmentry should check whether the vmcs provided by
>> >> the guest hypervisor is a shadow vmcs and fail.
>> >
>> > How can this happen, since vmptrld checks the revision_id as you said
>> > below?
From: Markus Elfring
Date: Fri, 22 Jul 2016 17:17:48 +0200
Refactor this function implementation so that the
drm_gem_object_unreference_unlocked() function will only be called once
in case of a failure according to the Linux coding style recommendation
for centralized exiting of functions.
Signe
On 07/22/2016 06:16 AM, Catalin Marinas wrote:
On Thu, Jul 21, 2016 at 02:33:52PM -0400, David Long wrote:
On 07/21/2016 01:23 PM, Marc Zyngier wrote:
On 21/07/16 17:33, David Long wrote:
On 07/20/2016 12:09 PM, Marc Zyngier wrote:
On 08/07/16 17:35, David Long wrote:
+#define MAX_INSN_SIZE
On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> Hi Bharat,
>
> On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote:
> > Hi,
> >
> > I'm observing that on x86 BIOS successfully assigns memory if an End point
> > requests
> > BAR of size 16byte.
> >
> > But as per
On Thu, Jul 21, 2016 at 03:10:57PM +0100, Mel Gorman wrote:
> From: Minchan Kim
>
> While I did stress test with hackbench, I got OOM message frequently which
> didn't ever happen in zone-lru.
>
> gfp_mask=0x26004c0(GFP_KERNEL|__GFP_REPEAT|__GFP_NOTRACK), order=0
> ..
> ..
> [] __alloc_pages_no
On Tue, Jul 12, 2016 at 3:12 PM, Dan Williams wrote:
> On Tue, Jul 12, 2016 at 7:57 AM, Peter Zijlstra wrote:
>> On Sat, Jul 09, 2016 at 08:25:54PM -0700, Dan Williams wrote:
>>> The pcommit instruction is being deprecated in favor of either ADR
>>> (asynchronous DRAM refresh: flush-on-power-fail
From: Markus Elfring
Date: Fri, 22 Jul 2016 16:51:00 +0200
Adjust jump targets according to the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/etnaviv/etnaviv_gem.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/
On Thu, Jul 21, 2016 at 10:13:03PM -0700, Andy Lutomirski wrote:
> On Thu, Jul 21, 2016 at 8:30 PM, Josh Poimboeuf wrote:
> > On Thu, Jul 21, 2016 at 03:32:32PM -0700, Andy Lutomirski wrote:
> >> On Thu, Jul 21, 2016 at 2:21 PM, Josh Poimboeuf
> >> wrote:
> >> > Now that we can find pt_regs regi
On Thu, Jul 21, 2016 at 03:10:59PM +0100, Mel Gorman wrote:
> If per-zone LRU accounting is available then there is no point
> approximating whether reclaim and compaction should retry based on pgdat
> statistics. This is effectively a revert of "mm, vmstat: remove zone and
> node double accounting
There is no point in having an explicit case that does nothing but falls
through to the default, simply remove the redundant case.
Signed-off-by: Charles Keepax
---
drivers/mfd/arizona-irq.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.
On Fri, Jul 22, 2016 at 11:53:52AM +0200, Daniel Borkmann wrote:
> On 07/22/2016 04:14 AM, Alexei Starovoitov wrote:
> >On Thu, Jul 21, 2016 at 06:09:17PM -0700, Sargun Dhillon wrote:
> >>This allows user memory to be written to during the course of a kprobe.
> >>It shouldn't be used to implement a
On Thu, Jul 21, 2016 at 03:11:01PM +0100, Mel Gorman wrote:
> Page reclaim determines whether a pgdat is unreclaimable by examining how
> many pages have been scanned since a page was freed and comparing that to
> the LRU sizes. Skipped pages are not reclaim candidates but contribute to
> scanned.
Paolo Bonzini writes:
...
>> Yeah, that's close. Though I would have done the same for the other side of
>> the if's too.
>> (Still evaluating which mode is actually more useful for us).
>
> For Linux guests, there should be no reason to use ignore_msrs. Linux
> is pretty resilient to "missing" M
Hi,
[auto build test WARNING on net-next/master]
[also build test WARNING on v4.7-rc7 next-20160722]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Grygorii-Strashko/drivers-net-cpsw-fix-driver
On Fri, 22 Jul 2016, Sean Paul wrote:
> On Fri, Jul 22, 2016 at 3:22 AM, Lee Jones wrote:
> > Since 0b52297f228 ("reset: Add support for shared reset controls") the
> > new Reset API now demands consumers choose either an *_exclusive or
> > a *_shared line when requesting reset lines.
> >
> > Sig
[+cc perf folks]
On Fri, Jul 22, 2016 at 05:59:51PM +0530, Muni Sekhar wrote:
> Hi All,
>
>
> We have xilinx PCIe endpoint with DMA reference block.
>
>
> The DMA-REF block provides a mechanism to DMA(also supports
> Scatter-Gather DMA) transfer data at the maximum rate between host
> (CPU) me
On Thu, Jul 21, 2016 at 03:10:58PM +0100, Mel Gorman wrote:
> With the reintroduction of per-zone LRU stats, highmem_file_pages is
> redundant so remove it.
>
> Signed-off-by: Mel Gorman
Acked-by: Johannes Weiner
According to the datasheet we have to set some bits as 0 and others as 1.
Make sure we do this for CFG1 and CFG3.
Signed-off-by: Michael Walle
---
drivers/hwmon/adt7411.c | 53 +
1 file changed, 49 insertions(+), 4 deletions(-)
diff --git a/driver
If the EXT_TDM bit is set and ain[12]_input will be switch to a temp2_input
attribute.
Signed-off-by: Michael Walle
---
drivers/hwmon/adt7411.c | 51 +
1 file changed, 43 insertions(+), 8 deletions(-)
diff --git a/drivers/hwmon/adt7411.c b/drivers
On 22-07-16, 20:42, Jisheng Zhang wrote:
> static int _set_opp_voltage(struct device *dev, struct regulator *reg,
> unsigned long u_volt, unsigned long u_volt_min,
> unsigned long u_volt_max)
> @@ -586,9 +565,24 @@ int dev_pm_opp_set_rate(struct
> >> Paolo, would you prefer this, or the other approach you already ack'd ?
> >
> > I think I prefer the other, because vcpu_debug is not ratelimited.
> > If the guest can trigger a printk it should always be ratelimited.
>
> Agree with rate limiting, but making this the default for everything d
Hi Guenter,
On Thu, Jul 21, 2016 at 6:30 PM, Guenter Roeck wrote:
> On 07/21/2016 03:37 PM, Hoan Tran wrote:
>>
>> This patch set adds hardware temperature and power reading support for
>> APM X-Gene SoC using the mailbox communication interface.
>> For device tree, it is the standard DT mailbox.
Paolo Bonzini writes:
>> >> Paolo, would you prefer this, or the other approach you already ack'd ?
>> >
>> > I think I prefer the other, because vcpu_debug is not ratelimited.
>> > If the guest can trigger a printk it should always be ratelimited.
>>
>> Agree with rate limiting, but making this
> Subject: Re: Why does BIOS assign memory to 16 byte BAR
>
> On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> > Hi Bharat,
> >
> > On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote:
> > > Hi,
> > >
> > > I'm observing that on x86 BIOS successfully assigns memory
Am 22.07.2016 17:48, schrieb SF Markus Elfring:
> From: Markus Elfring
> Date: Fri, 22 Jul 2016 16:45:22 +0200
>
> Move a return statement into a block for successful function execution.
> Omit a duplicate check for the local variable "ret" then at the end.
>
> Signed-off-by: Markus Elfring
>
On Tue, Jul 19, 2016 at 01:36:49PM -0700, Mitchel Humpherys wrote:
> The following patch to the ARM SMMU driver:
>
> commit d346180e70b91b3d5a1ae7e5603e65593d4622bc
> Author: Robin Murphy
> Date: Tue Jan 26 18:06:34 2016 +
>
> iommu/arm-smmu: Treat all device transa
On Wed, Jul 13, 2016 at 11:08:42PM -0700, Andrew Duggan wrote:
> Signed-off-by: Andrew Duggan
> ---
> This version includes Nick's suggestion of adding force to the device tree
> parameters so make it obvious that these parameters overwrite the
> default values set in the firware config.
Why do w
* Dan Williams wrote:
> On Tue, Jul 12, 2016 at 3:12 PM, Dan Williams
> wrote:
> > On Tue, Jul 12, 2016 at 7:57 AM, Peter Zijlstra
> > wrote:
> >> On Sat, Jul 09, 2016 at 08:25:54PM -0700, Dan Williams wrote:
> >>> The pcommit instruction is being deprecated in favor of either ADR
> >>> (asy
> +virtual context
> +virtual org
> +virtual report
> +
> +@cond@
> +statement S1;
> +position p;
> +@@
> +
> +<+...
> +* if@p (...) S1 else S1
> +...+>
You don't need the <+... ...+>. Just put the if by itself.
julia
> +
> +@script:python depends on org@
> +p << cond.p;
> +@@
> +
> +cocci.prin
On 16.07.2016 17:07, Andreas Klinger wrote:
On Marvell mv88f6180 with pin control driver one can not use multi
purpose pins 35 through 44.
I'm using this controller on an embedded board and i found that the
pin multiplexing is not the same as in the hardware spezification.
This patch alters the p
On Fri, Jul 22, 2016 at 08:55:00AM +0200, Benjamin Tissoires wrote:
> On Fri, Jul 22, 2016 at 6:37 AM, Dmitry Torokhov
> wrote:
> > Hi Lv,
> >
> > On Fri, Jul 22, 2016 at 12:24:50AM +, Zheng, Lv wrote:
> >> Hi, Dmitry
> >>
> >>
> >> Thanks for the review.
> >>
> >> > From: Dmitry Torokhov [mai
From: Markus Elfring
Date: Fri, 22 Jul 2016 18:58:14 +0200
The release_firmware() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
Hi,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 47ef4ad2684d380dd6d596140fb79395115c3950
commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation
of a VDSO
date: 8 months ago
config: mips-
On Fri, Jul 22, 2016 at 08:37:50AM +, Zheng, Lv wrote:
> Hi, Dmitry
>
> Thanks for the review.
>
> > From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> > Subject: Re: [PATCH v4 2/2] ACPI / button: Add document for ACPI control
> > method lid device restrictions
> >
> > Hi Lv,
> >
>
To create a baseline, I'll pick up the changes from the extcon
repository and make them available in chromeos-4.4.
Guenter
On Fri, Jul 22, 2016 at 2:40 AM, Chris Zhong wrote:
> Hi Chanwoo Choi
>
> Thanks for your help, I am going to post V7 next week base on these latest
> extcon patch.
>
> Rega
As discussed in the previous patch, there is a reliability
benefit to allowing an init value for the Protection Keys Rights
User register (PKRU) which differs from what the XSAVE hardware
provides.
But, having PKRU be 0 (its init value) provides some nonzero
amount of optimization potential to th
Andy Lutomirski brought this up as a potential issue. It's
straightforward to fix, but has potential performance
implications.
This applies on top of the previous pkeys syscall code that I
posted, but I think we should probably discuss these on their own
and not as a part of the larger series.
Hi,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 47ef4ad2684d380dd6d596140fb79395115c3950
commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error
with binutils 2.24 and earlier
date: 7 mo
Hi Linus,
Please consider pulling the following changes for the GFS2 file system.
Since I'll be on vacation / holiday all next week, I'm doing the merge
window processing for GFS2 early this time, before the merge window has
been officially opened: I'd rather post the patches a little early than
Move things around a little in __etnaviv_gem_new() to make it
more readable.
Reported-by: Markus Elfring
Reported-by: walter harms
Signed-off-by: Sean Paul
---
drivers/gpu/drm/etnaviv/etnaviv_gem.c | 25 +++--
1 file changed, 11 insertions(+), 14 deletions(-)
diff --git a/
On Thu, Jul 21, 2016 at 11:34:25AM -0700, Kees Cook wrote:
> On Wed, Jul 20, 2016 at 11:52 PM, Michael Ellerman
> wrote:
> > Kees Cook writes:
> >
> >> diff --git a/mm/usercopy.c b/mm/usercopy.c
> >> new file mode 100644
> >> index ..e4bf4e7ccdf6
> >> --- /dev/null
> >> +++ b/mm/user
On Fri, Jul 22, 2016 at 11:50 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Fri, 22 Jul 2016 16:51:00 +0200
>
> Adjust jump targets according to the Linux coding style convention.
>
I'm not convinced the old labels are really that bad, tbh.
Sean
> Signed-off-by: Markus Elfring
>
From: "J. Bruce Fields"
There's some odd logic in nfsd_create() that allows it to be called with
the parent directory either locked or unlocked. The only already-locked
caller is NFSv2's nfsd_proc_create(). It's less confusing to split out
the unlocked case into a separate function which the NF
On Fri, Jul 22, 2016 at 08:16:42AM -0700, Viresh Kumar wrote:
> > Long term as I was mentioning in the other thread I think it'd be good
> > if the current target() drivers were modified to supply resolve_freq(),
> > and that cpufreq_register_driver() were again changed to require it for
> > those
From: "J. Bruce Fields"
I'm not sure why this was added. It doesn't seem necessary, and no
other caller does this.
Signed-off-by: J. Bruce Fields
---
fs/nfsd/vfs.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
index fba8e7e521e0..7ae3b5a72a4d 100644
--- a
From: "J. Bruce Fields"
lookup_one_len already has this check.
The only effect of this patch is to return access instead of perm in the
0-length-filename case. I actually prefer nfserr_perm (or _inval?), but
I doubt anyone cares.
The isdotent check seems redundant too, but I worry that some cl
From: Oleg Drokin
When doing a create (mkdir/mknod) on a name, it's worth
checking the name exists first before returning EACCES in case
the directory is not writeable by the user.
This makes return values on the client more consistent
regardless of whenever the entry there is cached in the local
From: "J. Bruce Fields"
Minor cleanup, no change in behavior.
Signed-off-by: J. Bruce Fields
---
fs/nfsd/vfs.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
index d45b39b408a1..cd06c6511cfc 100644
--- a/fs/nfsd/vfs.c
+++ b/fs/nfsd
From: "J. Bruce Fields"
On Fri, Jul 22, 2016 at 11:13:20AM -0400, Oleg Drokin wrote:
> Hm, in fact indeed. I was just too worked up about the client side,
> but on the server side there was a real lookup already, so it does
> look workable.
So I end up with the following. This is all (after you
From: "J. Bruce Fields"
We need an fh_verify to make sure we at least have a dentry, but actual
permission checks happen later.
Signed-off-by: J. Bruce Fields
---
fs/nfsd/nfs4proc.c | 7 +--
fs/nfsd/vfs.c | 6 +-
2 files changed, 2 insertions(+), 11 deletions(-)
diff --git a/fs/n
From: "J. Bruce Fields"
vfs_{create,mkdir,mknod} each begin with a call to may_create(), which
returns EEXIST if the object already exists.
This check is therefore unnecessary.
(In the NFSv2 case, nfsd_proc_create also has such a check. Contrary to
RFC 1094, our code seems to believe that a CR
On Fri, Jul 22, 2016 at 11:47 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Fri, 22 Jul 2016 15:56:15 +0200
>
> The functions drm_gem_object_unreference_unlocked() and vunmap() perform
> also input parameter validation.
> Thus the tests around their calls are not needed.
>
> This is
On Fri, Jul 22, 2016 at 11:51 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Fri, 22 Jul 2016 17:17:48 +0200
>
> Refactor this function implementation so that the
> drm_gem_object_unreference_unlocked() function will only be called once
> in case of a failure according to the Linux c
On 07/21/2016 04:57 PM, Jason Low wrote:
On Wed, 2016-07-20 at 16:29 +0300, Imre Deak wrote:
On ti, 2016-07-19 at 21:39 -0700, Jason Low wrote:
On Tue, 2016-07-19 at 16:04 -0700, Jason Low wrote:
Hi Imre,
Here is a patch which prevents a thread from spending too much "time"
waiting for a mute
Hi Rafael,
On 21 July 2016 at 21:28, Rafael J. Wysocki wrote:
> On Wednesday, July 20, 2016 02:18:00 AM fu@linaro.org wrote:
>> From: Fu Wei
>>
>> This patch adds support for parsing arch timer in GTDT,
>> provides some kernel APIs to parse all the PPIs and
>> always-on info in GTDT and expo
On 07/21/2016 06:29 PM, Jason Low wrote:
On Wed, 2016-07-20 at 14:37 -0400, Waiman Long wrote:
On 07/20/2016 12:39 AM, Jason Low wrote:
On Tue, 2016-07-19 at 16:04 -0700, Jason Low wrote:
Hi Imre,
Here is a patch which prevents a thread from spending too much "time"
waiting for a mutex in the
From: Markus Elfring
Date: Fri, 22 Jul 2016 19:54:20 +0200
The iput() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
mm/zsmalloc.
On Fri, 22 Jul 2016, Waiman Long wrote:
I think making mutex_trylock() fail maybe a bit too far. Do we really
have any real workload that cause starvation problem because of that.
Code that does mutex_trylock() in a loop can certainly cause lock
starvation, but it is not how mutex_trylock() i
From: Dave Hansen
probe_kernel_address() has an unfortunate name since it is used
to probe kernel *and* userspace addresses. Add a comment
explaining some of the situation to help the next developer who
might make the silly assumption that it is for probing kernel
addresses.
Signed-off-by: Dav
From: Dave Hansen
The various tracing headers pass some variables into the tracing
code itself to indicate things like the name of the tracing
directory where the tracepoints should be located in debugfs.
The general pattern is to #undef them before redefining them.
But, if all instances don't
The first two patches here are useful in any case, I think.
But, as for the third: There are no known prefetch errata on
processors that support memory protection keys. There have not
been any that I can find in any recent generations, either.
But, if there were a future erratum, we would need
From: Dave Hansen
Thanks to Andy Lutomirski for pointing out the potential issue
here.
Memory protection keys only affect data access. They do not
affect instruction fetches. So, an instruction may not be
readable, while it *is* executable.
The fault prefetch checking code directly reads ins
From: Colin Ian King
The check for a -ve error is redundant, remove it and just
immediately return the return value from the call to
seq_open_net.
Signed-off-by: Colin Ian King
---
net/kcm/kcmproc.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/net/kcm/kcmproc.c b/ne
insertion(+)
--- linux-next-20160722.orig/drivers/pinctrl/bcm/Kconfig
+++ linux-next-20160722/drivers/pinctrl/bcm/Kconfig
@@ -60,6 +60,7 @@ config PINCTRL_IPROC_GPIO
config PINCTRL_CYGNUS_MUX
bool "Broadcom Cygnus IOMUX driver"
depends on (ARCH_BCM_CYGNUS || COMPILE_TEST)
+
201 - 300 of 502 matches
Mail list logo
