Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return -ENODEV
Signed-off-by: Gustavo A. R. Silva
---
drivers/mtd/nand/vf610_nfc.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/mtd/nand/
Hi Maddy/Anju,
Comments below :)
Anju T Sudhakar writes:
> Code to create platform device for the IMC counters.
> Paltform devices are created based on the IMC compatibility
> string.
>
> New Config flag "CONFIG_HV_PERF_IMC_CTRS" add to contain the
> IMC counter changes.
I don't think we need a
Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return -ENODEV
Signed-off-by: Gustavo A. R. Silva
---
drivers/iio/adc/rockchip_saradc.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/iio/
On Thu, 6 Jul 2017, Shivappa Vikas wrote:
> On Sun, 2 Jul 2017, Thomas Gleixner wrote:
> > On Mon, 26 Jun 2017, Vikas Shivappa wrote:
> > > +static void mbm_update(struct rdt_domain *d, int rmid)
> > > +{
> > > + struct rmid_read rr;
> > > +
> > > + rr.first = false;
> > > + rr.d = d;
> > > +
> > >
Keep supporting proprietary "xlnx,phy-type" attribute and add support for
MII connectivity to the PHY.
Signed-off-by: Alvaro Gamez Machado
---
Changes since v1:
* Renamed phy_type to phy_mode. No other instances of this struct
member were found except for those we wanted to c
---
include/linux/platform_device.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/include/linux/platform_device.h b/include/linux/platform_device.h
index 98c2a7c7108e..723c209d3760 100644
--- a/include/linux/platform_device.h
+++ b/include/linux/platform_device.h
@@ -368,4 +368,11 @@
On Thu, 6 Jul 2017, Shivappa Vikas wrote:
> On Sun, 2 Jul 2017, Thomas Gleixner wrote:
> > > INIT_LIST_HEAD(&r->evt_list);
> > >
> > > if (rdt_mon_features & (1 << QOS_L3_OCCUP_EVENT_ID))
> > > list_add_tail(&llc_occupancy_event.list, &r->evt_list);
> > > + if (is_mbm_total_enabled()
Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return -ENODEV
Signed-off-by: Gustavo A. R. Silva
---
drivers/iio/adc/meson_saradc.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/iio/adc
On Thu, 6 Jul 2017, Shivappa Vikas wrote:
> On Sun, 2 Jul 2017, Thomas Gleixner wrote:
> > > + /* Check whether cpus belong to parent ctrl group */
> > > + cpumask_andnot(tmpmask, newmask, &pr->cpu_mask);
> > > + if (cpumask_weight(tmpmask)) {
> > > + ret = -EINVAL;
> > > + goto out
On 2017-07-04 10:34, Patrick Bellasi wrote:
Currently the utilization of the FAIR class is collected before locking
the policy. Although that should not be a big issue for most cases, we
also don't really know how much latency there can be between the
utilization reading and its usage.
Let's get
Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return -ENODEV
Signed-off-by: Gustavo A. R. Silva
---
drivers/pwm/pwm-sun4i.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/pwm/pwm-sun4i.c
On Wed, 2017-07-05 at 11:28 -0400, Tejun Heo wrote:
> Hello, Abdul.
>
> Thanks for the debug info. Can you please see whether the following
> patch fixes the issue?
It is my pleasure and yes the patch fixes the problem.
> If the problem is too difficult to reproduce
The problem was reproduci
On Thu, Jul 6, 2017 at 10:49 PM, Kees Cook wrote:
> On Thu, Jul 6, 2017 at 10:39 PM, Linus Torvalds
>> And I think the credentials switch (which is the point of no return
>> anyway) happens before we start mmap'ing the executable etc. We used
>> to have some odd code there and do it in the complet
Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return -ENODEV
Signed-off-by: Gustavo A. R. Silva
---
drivers/crypto/bcm/cipher.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/crypto/bcm
On Thu, 2017-07-06 at 15:52 -0600, Ross Zwisler wrote:
> Quick Summary
>
> Platforms in the very near future will have multiple types of memory
> attached to a single CPU. These disparate memory ranges will have some
> characteristics in common, such as CPU cache coherence, but they can
Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return -ENODEV
Signed-off-by: Gustavo A. R. Silva
---
drivers/input/keyboard/tegra-kbc.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/inpu
In hotplug logic, it always indicates non-specific failure to
platform through _OST when handing acpi hot-remove event failed. Then
platform terminates the hot-remove process but it can not identify
the reason.
Base on current hot-remove code, there have two situations that it
returns busy:
- OSP
Kernel should decrements the reference count of acpi device
when the scheduling of acpi hotplug work failed, and evaluates
_OST to notify BIOS the failure.
v3:
More simplify the code. (Rafael J. Wysocki)
v2:
To simplify the code. (Andy Shevchenko)
Cc: "Rafael J. Wysocki"
Cc: Len Brown
Cc: Mich
On Thu, 6 Jul 2017, Shivappa Vikas wrote:
> On Sun, 2 Jul 2017, Thomas Gleixner wrote:
> > > +static bool __mon_event_count(u32 rmid, struct rmid_read *rr)
> > > +{
> > > + u64 tval;
> > > +
> > > + tval = __rmid_read(rmid, rr->evtid);
> > > + if (tval & (RMID_VAL_ERROR | RMID_VAL_UNAVAIL)) {
> > >
IRQ_NOAUTOEN cannot be used with shared IRQs, since commit 04c848d39879
("genirq: Warn when IRQ_NOAUTOEN is used with shared interrupts") and
kernel now throws a warn dump. But OMAP DWC3 driver uses this flag. As
per commit 12a7f17fac5b ("usb: dwc3: omap: fix race of pm runtime with
irq handler in
Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return -ENODEV
Signed-off-by: Gustavo A. R. Silva
---
drivers/fpga/altera-hps2fpga.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/fpga/al
Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return.
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/tegra/vic.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/tegra/vic
On Fri, Jul 07, 2017 at 11:07:59AM +0800, Baoquan He wrote:
> On 07/06/17 at 03:57pm, Matt Fleming wrote:
> > On Thu, 06 Jul, at 08:31:07AM, Naoya Horiguchi wrote:
> > > + for (i = 0; i < nr_desc; i++) {
> > > + md = (efi_memory_desc_t *)(pmap + (i * e->efi_memdesc_size));
> > > +
> > > +
From: Chao Yu
generic/361 reports below warning, this is because: once, there is
someone entering into critical region of sbi.cp_lock, if write_end_io.
f2fs_stop_checkpoint is invoked from an triggered IRQ, we will encounter
deadlock.
So this patch changes to use spin_{,un}lock_irq{save,restore}
Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return.
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/tegra/sor.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/tegra/sor.
On Thu, Jul 6, 2017 at 11:02 PM, Linus Torvalds
wrote:
> So 2+MB is still definitely something people can do (and probably *do* do).
With the default 8MB stack, most people are already limited to 2MB
here. I guess the question is, do people raise their stack rlimit to
gain more arguments? Should
Hi Roman,
[auto build test WARNING on mmotm/master]
[also build test WARNING on next-20170706]
[cannot apply to v4.12]
[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/Roman-Gushchin/mm-make
On Thu, Jul 6, 2017 at 10:45 PM, Kees Cook wrote:
> On Thu, Jul 6, 2017 at 10:36 PM, Andy Lutomirski wrote:
>>
>> Aren't there real use cases that use many megs of arguments?
>
> They'd be relatively new since the args were pretty limited before.
> I'd be curious to see them.
"megs" yes. "many m
On 07/07/2017 07:30 AM, Andy Duan wrote:
From: Richard Leitner Sent: Thursday, July 06,
2017 9:06 PM
To: Andy Duan ; robh...@kernel.org;
mark.rutl...@arm.com
Cc: net...@vger.kernel.org; devicet...@vger.kernel.org; linux-
ker...@vger.kernel.org; d...@g0hl1n.net; Richard Leitner
Subject: [PATC
platform_get_irq() returns an error code, but the mxcmmc driver
ignores it and always returns -EINVAL. This is not correct,
and prevents -EPROBE_DEFER from being propagated properly.
Print error message and propagate the return value of
platform_get_irq on failure.
Signed-off-by: Gustavo A. R. Si
On Tue, Jul 4, 2017 at 10:34 AM, Patrick Bellasi
wrote:
> Currently the utilization of the FAIR class is collected before locking
> the policy. Although that should not be a big issue for most cases, we
> also don't really know how much latency there can be between the
> utilization reading and it
On 07/06/2017 02:52 PM, Ross Zwisler wrote:
[...]
> diff --git a/drivers/acpi/Makefile b/drivers/acpi/Makefile
> index b1aacfc..31e3f20 100644
> --- a/drivers/acpi/Makefile
> +++ b/drivers/acpi/Makefile
> @@ -72,6 +72,7 @@ obj-$(CONFIG_ACPI_PROCESSOR)+= processor.o
> obj-$(CONFIG_ACPI)
In page_flip vblank is sent with no delay. Driver does not know when the
actual update is present on the display and has no means for getting
this information from a device. It is practically impossible to say
exactly *when* as there is also i.e. a usb delay.
When we are unable to determine when t
On Thu, Jul 6, 2017 at 10:39 PM, Linus Torvalds
wrote:
> On Thu, Jul 6, 2017 at 10:15 PM, Kees Cook wrote:
>>
>> I always say this backwards. :P Default is top-down (allocate at high
>> addresses and work down toward low). With unlimited stack, allocations
>> start at low addresses and work up. H
On Fri, Jul 07, 2017 at 10:31:10AM +0900, Jaechul Lee wrote:
> This driver can support more frequencies over 96KHz. There are no reasons
> to limit the frequency range below 96KHz. If codecs/amps or something else
> can't support higher resolution rates, the constraints would be set rates
> properl
On Thu, Jul 6, 2017 at 10:36 PM, Andy Lutomirski wrote:
> On Thu, Jul 6, 2017 at 10:15 PM, Kees Cook wrote:
>> On Thu, Jul 6, 2017 at 10:10 PM, Kees Cook wrote:
>>> On Thu, Jul 6, 2017 at 9:48 PM, Andy Lutomirski wrote:
How about a much simpler solution: don't read rlimit at all in
co
Fix checkpatch issues: "CHECK: Alignment should match open parenthesis".
Signed-off-by: Arushi Singhal
---
drivers/staging/rtl8712/mlme_linux.c| 4 ++--
drivers/staging/rtl8712/rtl8712_cmd.c | 2 +-
drivers/staging/rtl8712/rtl8712_efuse.c | 2 +-
3 files changed, 4 insertions(+), 4 deletio
On Thu, Jul 6, 2017 at 10:15 PM, Kees Cook wrote:
>
> I always say this backwards. :P Default is top-down (allocate at high
> addresses and work down toward low). With unlimited stack, allocations
> start at low addresses and work up. Here's the results (shown with
> randomize_va_space sysctl set
On Thu, Jul 6, 2017 at 10:15 PM, Kees Cook wrote:
> On Thu, Jul 6, 2017 at 10:10 PM, Kees Cook wrote:
>> On Thu, Jul 6, 2017 at 9:48 PM, Andy Lutomirski wrote:
>>> How about a much simpler solution: don't read rlimit at all in
>>> copy_strings(), let alone try to enforce it. Instead, just befor
Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return.
Signed-off-by: Gustavo A. R. Silva
---
drivers/regulator/qcom_smd-regulator.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/regula
On 07/06/2017 02:52 PM, Ross Zwisler wrote:
[...]
>
> The naming collision between Jerome's "Heterogeneous Memory Management
> (HMM)" and this "Heterogeneous Memory (HMEM)" series is unfortunate, but I
> was trying to stick with the word "Heterogeneous" because of the naming of
> the ACPI 6.2 Hete
Check return value from call to of_match_device()
in order to prevent a NULL pointer dereference.
In case of NULL print error message and return.
Signed-off-by: Gustavo A. R. Silva
---
drivers/regulator/qcom_rpm-regulator.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/regula
From: Richard Leitner Sent: Thursday, July 06,
2017 9:06 PM
>To: Andy Duan ; robh...@kernel.org;
>mark.rutl...@arm.com
>Cc: net...@vger.kernel.org; devicet...@vger.kernel.org; linux-
>ker...@vger.kernel.org; d...@g0hl1n.net; Richard Leitner
>
>Subject: [PATCH 2/2] net: ethernet: fsl: add phy rese
Hi,
On Wed, Jul 5, 2017 at 6:41 AM, Patrick Bellasi wrote:
[..]
>
>> But what about clearing the sched-class's flag from .pick_next_task()
>> callback
>> when they return NULL ?
>>
>> What about something like this instead (completely untested), with which we
>> don't need the 2/3 patch as well:
On Thu, Jul 6, 2017 at 2:11 AM, Al Viro wrote:
> uaccess str...() dead code removals.
Side note: you left a couple of references to strlen_user() still in the tree.
None of them *matter* (two comments and one declaration for the
function that no longer exists), but it just strikes me as
On Thu, Jul 6, 2017 at 10:10 PM, Kees Cook wrote:
> On Thu, Jul 6, 2017 at 9:48 PM, Andy Lutomirski wrote:
>> How about a much simpler solution: don't read rlimit at all in
>> copy_strings(), let alone try to enforce it. Instead, just before the
>> point of no return, check how much stack space
Check return value from call to devm_kmemdup()
in order to prevent a NULL pointer dereference.
Signed-off-by: Gustavo A. R. Silva
---
drivers/hid/hid-logitech-hidpp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
index
Hi Arnaldo,
Could this patch be merged?
Otherwise the jump arrow is broken when it's displayed at the row 0 in
annotate view.
Thanks
Jin Yao
On 6/8/2017 2:01 PM, Jin Yao wrote:
When the jump instruction is displayed at the row 0 in annotate view,
the arrow is broken. An example:
16.86 │
On Thu, Jul 6, 2017 at 9:48 PM, Andy Lutomirski wrote:
> How about a much simpler solution: don't read rlimit at all in
> copy_strings(), let alone try to enforce it. Instead, just before the
> point of no return, check how much stack space is already used and, if
> it's more than an appropriate
On Thu, Jul 6, 2017 at 2:20 PM, Al Viro wrote:
>
> Linus, could you hold that one back until tomorrow? I want to tweak the
> last commit in there a bit, but I want to give it a local beating first...
Ok, dropping this one. All your other branches are merged now.
Linus
On Thu, Jul 6, 2017 at 9:48 PM, Andy Lutomirski wrote:
>
> How about a much simpler solution: don't read rlimit at all in
> copy_strings(), let alone try to enforce it.
People have historically relied on E2BIG and then splitting things
into multiple chunks (ie do the whole 'xargs' thing).
But I
On Wed, Jul 5, 2017 at 9:19 PM, Sinan Kaya wrote:
> According to extended tags ECN document, all PCIe receivers are expected
> to support extended tags support. It should be safe to enable extended
> tags on endpoints without checking compatibility.
>
> This assumption seems to be working fine exc
For marking the fused instructions clearly, This patch adds a
line before the first instruction of pair and joins it with the
arrow of the jump.
For example, when je is selected in annotate view, the line
before cmpl is displayed and joins the arrow of je.
│ ┌──cmpl $0x0,argp_program_v
Macro fusion merges two instructions to a single micro-op. Intel
core platform performs this hardware optimization under limited
circumstances.
For example, CMP + JCC can be "fused" and executed /retired
together. While with sampling this can result in the sample
sometimes being on the JCC and som
Macro fusion merges two instructions to a single micro-op. Intel
core platform performs this hardware optimization under limited
circumstances. For example, CMP + JCC can be "fused" and executed
/retired together. While with sampling this can result in the
sample sometimes being on the JCC and some
On 2017-07-07 06:53, Gustavo A. R. Silva wrote:
> Check return values from call to devm_kzalloc() and devm_kmemup()
If someone cares enough: s/devm_kmemup/evm_kmemdup/
> in order to prevent a NULL pointer dereference.
>
> This issue was detected using Coccinelle and the following semantic patch
Hi all,
Please do not add any v4.14 material to you linux-next included branches
until after v4.13-rc1 has been released.
Changes since 20170706:
The f2fs tree gained a conflict against Linus' tree.
The akpm tree lost a patch that turned up elsewhere.
Non-merge commits (relative to
If this memory allocation fails, we should go through the error handling
path as done everywhere else in this function before returning.
Signed-off-by: Christophe JAILLET
---
drivers/net/arcnet/com20020-pci.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/net/a
Check return values from call to devm_kzalloc() and devm_kmemup()
in order to prevent a NULL pointer dereference.
This issue was detected using Coccinelle and the following semantic patch:
@@
expression x;
identifier fld;
@@
* x = devm_kzalloc(...);
... when != x == NULL
x->fld
Cc: Peter
Quoting Peter Rosin :
On 2017-07-07 06:35, Gustavo A. R. Silva wrote:
Hi Peter,
Quoting Peter Rosin :
On 2017-07-07 00:08, Gustavo A. R. Silva wrote:
Check return value from call to devm_kzalloc()
in order to prevent a NULL pointer dereference.
Right, thanks for finding that one! There's
On Thu, Jul 6, 2017 at 12:12 PM, Kees Cook wrote:
> On Thu, Jul 6, 2017 at 10:52 AM, Linus Torvalds
> wrote:
>> On Thu, Jul 6, 2017 at 10:29 AM, Kees Cook wrote:
(a) minimal: just use our existing default stack (and stack _only_)
limit value for suid binaries that actually get ex
Okay Kees. I will take a look at it.
Best,
Shubham Bansal
On Fri, Jul 7, 2017 at 10:12 AM, Kees Cook wrote:
> On Wed, Jul 5, 2017 at 8:49 PM, Shubham Bansal
> wrote:
>> Hi Kees,
>>
>> Problem is my ARM machine don't have clang and iproute2 which is
>> keeping me from testing the bpf tail calls.
On (07/06/17 11:38), Matt Redfearn wrote:
> All early console drivers that may be registered as the earlycon are
> marked __init to be placed in the init section. The drivers' code and
> data are freed during free_initmem_default() but the early console is
> not unregistered in printk_late_init() a
On 2017-07-07 06:35, Gustavo A. R. Silva wrote:
> Hi Peter,
>
> Quoting Peter Rosin :
>
>> On 2017-07-07 00:08, Gustavo A. R. Silva wrote:
>>> Check return value from call to devm_kzalloc()
>>> in order to prevent a NULL pointer dereference.
>>
>> Right, thanks for finding that one! There's anoth
Hi Thomas,
At 07/07/2017 11:04 AM, Ye Xiaolong wrote:
On 07/07, Dou Liyang wrote:
Hi xiaolong,
Really thanks for your testing.
At 07/07/2017 09:54 AM, Ye Xiaolong wrote:
On 07/06, Thomas Gleixner wrote:
On Thu, 6 Jul 2017, kernel test robot wrote:
commit: 03fa63cc96ab35592e0a7d522b8edbc1e
On (07/06/17 11:38), Matt Redfearn wrote:
> Commit 4c30c6f566c0 ("kernel/printk: do not turn off bootconsole in
> printk_late_init() if keep_bootcon") added a check on keep_bootcon to
> ensure that boot consoles were kept around until the real console is
> registered.
> This can lead to problems if
On Tue, Jul 4, 2017 at 10:34 AM, Patrick Bellasi
wrote:
> Currently, sg_cpu's flags are set to the value defined by the last call of
> the cpufreq_update_util()/cpufreq_update_this_cpu(); for RT/DL classes
> this corresponds to the SCHED_CPUFREQ_{RT/DL} flags always being set.
>
> When multiple CP
On Wed, Jul 5, 2017 at 8:49 PM, Shubham Bansal
wrote:
> Hi Kees,
>
> Problem is my ARM machine don't have clang and iproute2 which is
> keeping me from testing the bpf tail calls.
>
> You should do the following to test it,.
>
> 1. tools/testing/selftests/bpf/
> 2. make
> 3. sudo ./test_progs
>
>
Hi Peter,
Quoting Peter Rosin :
On 2017-07-07 00:08, Gustavo A. R. Silva wrote:
Check return value from call to devm_kzalloc()
in order to prevent a NULL pointer dereference.
Right, thanks for finding that one! There's another one inside the
for loop that is just starting in the context of t
On Wed, 2017-07-05 at 13:15 -0500, Mike Christie wrote:
> On 07/04/2017 03:44 AM, Colin King wrote:
> > From: Colin Ian King
> >
> > Variables device_mutex and device_list static are local to the source,
> > so make them static.
> >
> > Cleans up sparse warnings:
> > "symbol 'device_list' was no
On 2017년 07월 07일 01:55, Arvind Yadav wrote:
> acpi_device_id are not supposed to change at runtime. All functions
> working with acpi_device_id provided by work with
> const acpi_device_id. So mark the non-const structs as const.
>
> File size before:
>text data bss dec h
On 2017-07-07 00:08, Gustavo A. R. Silva wrote:
> Check return value from call to devm_kzalloc()
> in order to prevent a NULL pointer dereference.
Right, thanks for finding that one! There's another one inside the
for loop that is just starting in the context of this patch. Care
to fix checking th
From: Sean Wang
The old place is Documentation/devicetree/bindings/clock/ that would
let people hard to find how to use MediaTek cpufreq driver, so moving
it to the appropriate place as other cpufreq drivers done would be
better.
Signed-off-by: Sean Wang
Acked-by: Viresh Kumar
---
.../binding
From: Sean Wang
Changes since v2:
- correct the typo in the binding document
Changes since v1:
- drop those patches already accepted
- refine the commit messages and Kconfig dependency
- Kconfig menu entry and file name itself are updated with more
generic name to drop "MT8173" since this driver
From: Sean Wang
Update binding document with adding operating-points-v2 as the required
property and the cooling level as the optional properties and adding more
examples guiding people how to use MediaTek cpufreq driver for MediaTek
SoCs.
Signed-off-by: Sean Wang
Acked-by: Viresh Kumar
---
.
From: Sean Wang
MT2701/MT7623 is a 32-bit ARMv7 based quad-core (4 * Cortex-A7) with
single cluster and this hardware is also compatible with the existing
driver through enabling CPU frequency feature with operating-points-v2
bindings. Also, this driver actually supports all MediaTek SoCs, the
Kc
Hi Juri,
On Wed, Jul 5, 2017 at 1:59 AM, Juri Lelli wrote:
> Worker kthread needs to be able to change frequency for all other
> threads.
>
> Make it special, just under STOP class.
>
> Signed-off-by: Juri Lelli
> Cc: Peter Zijlstra
> Cc: Ingo Molnar
> Cc: Rafael J. Wysocki
> Cc: Viresh Kumar
On 2017/7/6 21:05, Marc Zyngier wrote:
> On 06/07/17 10:01, Hanjun Guo wrote:
>> Hi Marc,
>>
>> On 2017/7/6 15:43, Marc Zyngier wrote:
>>> On 06/07/17 05:35, Hanjun Guo wrote:
From: Hanjun Guo
commit d59f6617eef0 (genirq: Allow fwnode to carry name information only)
forgot to d
On Thu, Jul 06, 2017 at 11:23:50PM +, Linux Kernel wrote:
> Make HWSPINLOCK a menuconfig to ease disabling
>
> So that there's no need to get into the submenu to disable all related
> config
> entries.
Here's how that looks on x86...
*
* Hardware Spinlock drivers
*
Har
Hi Juri,
On Wed, Jul 5, 2017 at 1:59 AM, Juri Lelli wrote:
> To be able to treat utilization signals of different scheduling classes
> in different ways (e.g., CFS signal might be stale while DEADLINE signal
> is never stale by design) we need to split sugov_cpu::util signal in two:
> util_cfs an
From: Wanpeng Li
BUG: using smp_processor_id() in preemptible [] code: 99-trinity/181
caller is debug_smp_processor_id+0x17/0x19
CPU: 0 PID: 181 Comm: 99-trinity Not tainted 4.12.0-01059-g2a42eb9 #1
Call Trace:
dump_stack+0x82/0xb8
check_preemption_disabled+0xd1/0xe3
debug_smp_p
ddebug_remove_module() use mod->name to find the ddebug_table of the
module and remove it. But dynamic_debug_setup() use the first
_ddebug->modname to create ddebug_table for the module. It's ok when
the _ddebug->modname is the same with the mod->name.
But livepatch module is special, it may conta
On 07/06/17 at 03:57pm, Matt Fleming wrote:
> On Thu, 06 Jul, at 08:31:07AM, Naoya Horiguchi wrote:
> > + for (i = 0; i < nr_desc; i++) {
> > + md = (efi_memory_desc_t *)(pmap + (i * e->efi_memdesc_size));
> > +
> > + /*
> > +* EFI_BOOT_SERVICES_{CODE|DATA} are avo
On 07/07, Dou Liyang wrote:
>Hi xiaolong,
>
>Really thanks for your testing.
>
>At 07/07/2017 09:54 AM, Ye Xiaolong wrote:
>>On 07/06, Thomas Gleixner wrote:
>>>On Thu, 6 Jul 2017, kernel test robot wrote:
>>>
commit: 03fa63cc96ab35592e0a7d522b8edbc1e6b02d22 ("x86/time: Initialize
interrup
2017-07-07 10:09 GMT+08:00 kernel test robot :
>
> FYI, we noticed the following commit:
>
> commit: 2a42eb9594a1480b4ead9e036e06ee1290e5fa6d ("sched/cputime: Accumulate
> vtime on top of nsec clocksource")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git sched/urgent
>
> in testcase: bo
add clk_fractional_divider_special_ops for rockchip specific requirements,
fractional divider must set that denominator is 20 times larger than
numerator to generate precise clock frequency.
Otherwise the CLK jitter is very big, poor quality of the clock signal.
RK document description:
3.1.9 Fra
We don't need to adjust prio before new pi_waiter adding. The prio
only need update after pi_waiter change or task priority change.
Signed-off-by: Alex Shi
Cc: Steven Rostedt
Cc: Sebastian Siewior
Cc: Mathieu Poirier
Cc: Juri Lelli
Cc: Thomas Gleixner
To: linux-kernel@vger.kernel.org
To: Ing
The rtmutex remove a pending owner bit in in rt_mutex::owner, in
commit 8161239a8bcc ("rtmutex: Simplify PI algorithm and make highest prio task
get lock")
But the document was changed accordingly. Updating it to a meaningful
state.
BTW, as 'Steven Rostedt' mentioned:
There is still technically a
The rt-mutex-design documents didn't gotten meaningful update from its
first version. Even after owner's pending bit was removed in commit 8161239a8bcc
("rtmutex: Simplify PI algorithm and make highest prio task get lock")
and priority list 'plist' changed to rbtree. And Peter Zijlstra did some
cle
On 07/06/2017 09:25 PM, Steven Rostedt wrote:
>
> This looks fine.
>
Thanks a lot!
>>
>>
>>
>> -Reviewers: Ingo Molnar, Thomas Gleixner, Thomas Duetsch, and Randy Dunlap
>> +Reviewers: Ingo Molnar, Thomas Gleixner, Thomas Duetsch, Randy Dunlap
>> + and Sebastian Siewior
Hi xiaolong,
Really thanks for your testing.
At 07/07/2017 09:54 AM, Ye Xiaolong wrote:
On 07/06, Thomas Gleixner wrote:
On Thu, 6 Jul 2017, kernel test robot wrote:
commit: 03fa63cc96ab35592e0a7d522b8edbc1e6b02d22 ("x86/time: Initialize interrupt
mode behind timer init")
+--
(Reposting without html subpart, second attempt)
On Thu, Jul 6, 2017 at 11:09 PM, Marcelo "Marc" Ranolfi
wrote:
Hi Zoltán and all,
I _was_ testing the patch series (the latest version), system worked
OK for two days, but then I got a system crash (probably hardware
related) and lost my files in
-邮件原件-
发件人: Jaegeuk Kim [mailto:jaeg...@kernel.org]
发送时间: 2017年7月7日 10:12
收件人: gaoxiang (P)
抄送: Chao Yu; linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
linux-f2fs-de...@lists.sourceforge.net
主题: Re: 答复: [f2fs-dev] [PATCH] f2fs: relax permission for atomic/volatile ioctls
O
On 07/07, gaoxiang (P) wrote:
> Hi,
> I think Sdcardfs should override task_struct cred fsuid/fsgid before calling
> the underlay fs operation.
> And it seems sdcardfs implementations misses override cred fsuid/fsgid before
> the ioctl operation.
Oh, good catch!
Thank you. ;)
>
> Thanks.
>
>
On Thu, Jul 06, 2017 at 06:04:13PM -0700, Palmer Dabbelt wrote:
[...]
> >> +#define __smp_load_acquire(p)
> >> \
> >> +do {
> >> \
> >> + union { typeof(*p) __val; char __c[1]; } __u
From: Jun Gao
The speed of sending i2c master code in high-speed mode depends on
source clock, clock-div and TIMING register. The source clock and
clock-div of different SoC are not all the same. In order to send
i2c master code at 400k in high-speed mode, a appropriate value
should be set to TIM
FYI, we noticed the following commit:
commit: 2a42eb9594a1480b4ead9e036e06ee1290e5fa6d ("sched/cputime: Accumulate
vtime on top of nsec clocksource")
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git sched/urgent
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -cpu Has
On Wed, Jul 05, 2017 at 07:23:26PM -0700, Jaegeuk Kim wrote:
> This patch allows atomic/volatile ioctls for sqlite under sdcardfs.
>
> Signed-off-by: Jaegeuk Kim
> ---
> fs/f2fs/file.c | 15 ---
> 1 file changed, 15 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> ind
On 07/07/17 10:34 AM, Michel Dänzer wrote:
> On 07/07/17 12:04 AM, Keith Packard wrote:
>> Michel Dänzer writes:
>>
@@ -317,6 +317,9 @@ int via_driver_irq_postinstall(struct drm_device *dev)
if (!dev_priv)
return -EINVAL;
+ if (dev->driver->get_vblank_coun
It's fine unless create_discard_cmd_control is used in remount flow in the
future.
On 2017/7/6 21:16, Chao Yu wrote:
> Hi Yunlong,
>
> It looks there is no way to create discard thread redundantly,
> so here we don't need to check this?
>
> Thanks,
>
> On 2017/7/6 19:05, Yunlong Song wrote:
>> Si
1 - 100 of 919 matches
Mail list logo
