From: "Steven Rostedt (VMware)"
The functionality between kernel_text_address() and _kernel_text_address()
is the same except that _kernel_text_address() does a little more (that
function needs a rename, but that can be done another time). Instead of
having duplicate code in both, simply have _ke
From: "Paul E. McKenney"
A number of architecture invoke rcu_irq_enter() on exception entry in
order to allow RCU read-side critical sections in the exception handler
when the exception is from an idle or nohz_full CPU. This works, at
least unless the exception happens in an NMI handler. In tha
From: "Steven Rostedt (VMware)"
If kernel_text_address() is called when RCU is not watching, it can cause an
RCU bug because is_module_text_address(), the is_kprobe_*insn_slot()
and is_bpf_text_address() functions require the use of RCU.
Only enable RCU if it is not currently watching before it
From: "Steven Rostedt (VMware)"
Currently the stack tracer calls rcu_irq_enter() to make sure RCU
is watching when it records a stack trace. But if the stack tracer
is triggered while tracing inside of a rcu_irq_enter(), calling
rcu_irq_enter() unconditionally can be problematic.
The reason for
Linus,
Stack tracing and RCU has been having issues with each other and lockdep
has been pointing out constant problems. The changes have been going into
the stack tracer, but it has been discovered that the problem isn't
with the stack tracer itself, but it is with calling save_stack_trace()
fro
On 09/23/2017 10:13 PM, Pavel Machek wrote:
> C++ comments look wrong in kernel tree. Fix one.
AFAIR they are now (sadly) accepted, but this patch works for me.
Would be nice if trivial could pick it.
> Signed-off-by: Pavel Machek
>
> diff --git a/include/linux/mtd/mtd.h b/include/linux/mtd/mtd
A recent pull on Linus' kernel repo triggered a "git gc --auto"
maintenance action that *finally* finished after beating my poor Alpha
PWS 433au to death for 32 hours.
Here's a snapshot of the ".git/objects/pack" directory for the repo:
total 1366084
190535 12 drwxr-xr-x 2 root root 122
Hi people,
Well, after reading those links provided by all of you, I'd like to start
contributing as a Kernel tester.
Have also read this link about testing the Kernel:
http://m.linuxjournal.com/content/linux-kernel-testing-and-debugging?page=0,0
Which are the minimal hardware requirements to
00 0 Merge
'linux-review/Thiebaud-Weksteen/Call-GetEventLog-before-ExitBootServices/20170923-004848'
into devel-spot-201709232001
git bisect good 422c87daea34f0298708f6afdf4591e5a0f9b9ea # 01:13 G 10
00 0 Merge
'linux-review/Colin-King/video-fbdev-radeon
Hi Phil,
> Greg Kroah-Hartman hat am 23. September 2017 um
> 18:15 geschrieben:
>
>
> On Sat, Sep 23, 2017 at 12:57:33PM +0200, Stefan Wahren wrote:
> > Hi Greg,
> >
> > > Phil Elwell hat am 11. August 2017 um 12:20
> > > geschrieben:
> > >
> > >
> > > The previous commit (0adbfd46) fixed
The reported scale was only correct for the default settings of 100 ms
integration time and gain 1.
This aligns the reported scale with the behaviour of any other IIO driver
and the documented ABI, but may require userspace changes if someone uses
non-default settings.
Signed-off-by: Stefan Brüns
Currently, the vl6180 driver reports bogus in_illuminance_scale values
when the integration time or hardware gain are changed from its default
value, i.e. it always reports a fixed value.
To avoid readback of the register values in case integration time, gain
or scale is queried, save the register
Instead of manually iterating the array of allowed gain values, use
find_closest. Storing the current gain setting avoids accessing the
hardware on each query.
Signed-off-by: Stefan Brüns
---
v2: add missing spaces
drivers/iio/light/vl6180.c | 85 --
Instead of reading the value from the register on each query, store the
set value.
Signed-off-by: Stefan Brüns
---
drivers/iio/light/vl6180.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/drivers/iio/light/vl6180.c b/drivers/iio/light/vl6180.c
index 68b9babfd2
This improves code uniformity (range checks for als_gain are also done
in the setter). Also unmangle rounding and calculation of register value.
The calculated integration time it_ms is required in the next patch of
the series.
Signed-off-by: Stefan Brüns
---
v2: removed redundant parenthesis
* Juergen Gross wrote:
> On 23/09/17 15:02, Ingo Molnar wrote:
> >
> > * Ingo Molnar wrote:
> >
> >> So I'd like to push these changes to Linus tomorrow-ish as an RFC pull
> >> request in 1-2 days, because there's now 4 fixes depending on these
> >> changes, and because the result will be mor
On Mittwoch, 20. September 2017 22:53:00 CEST Rob Herring wrote:
> On Sun, Sep 17, 2017 at 05:19:52AM +0200, Stefan Brüns wrote:
> > The A64 is register compatible with the H3, but has a different number
> > of dma channels and request ports.
> >
> > Attach additional properties to the node to all
From: Christophe JAILLET
Date: Fri, 22 Sep 2017 01:01:11 +0200
> All the error handling paths 'goto error', except this one.
> We should also go to error in this case, or some resources will be
> leaking.
>
> Signed-off-by: Christophe JAILLET
Applied, thank you.
Rev 3.1 Sec 2.3.1 Request Handling Rules says a device can issue CRS
following a D3hot->D0 transition. Add pci_dev_wait() call with 1 second
timeout to see if device is available before returning.
Signed-off-by: Sinan Kaya
---
drivers/pci/pci.c | 6 +-
1 file changed, 5 insertions(+), 1 dele
Rev 3.1 Sec 2.3.1 Request Handling Rules indicates that a device can issue
CRS following secondary bus reset. Handle device presence gracefully.
Signed-off-by: Sinan Kaya
---
drivers/pci/pci.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/pci.c b/driver
Rev 3.1 Sec 2.3.1 Request Handling Rules:
Valid reset conditions after which a device is permitted to return CRS
are:
* Cold, Warm, and Hot Resets,
* FLR
* A reset initiated in response to a D3hot to D0 uninitialized
Try to reuse FLR implementation towards other reset types.
Signed-off-by: Sinan
Commit b014e96d1abb ("PCI: Protect pci_error_handlers->reset_notify() usage
with device_lock()") added protection around pci_dev_restore() function so
that device specific remove callback does not cause a race condition
against hotplug.
pci_dev_lock() usage has been forgotten in two different plac
pci_flr_wait() and pci_af_flr() functions assume graceful return even
though the device is inaccessible under error conditions.
Return -ENOTTY in error cases so that __pci_reset_function_locked() can
try other reset types if AF_FLR/FLR reset fails.
Signed-off-by: Sinan Kaya
---
drivers/pci/pci.
On Fri, Sep 22, 2017 at 09:46:28AM +0100, Charles Keepax wrote:
>On Wed, Sep 20, 2017 at 04:45:02AM +, Levin, Alexander (Sasha Levin) wrote:
>> From: Nicholas Mc Guire
>>
>> [ Upstream commit ed784c532a3d0959db488f40a96c5127f63d42dc ]
>>
>> The delay here is not in atomic context and does not
On 9/23/2017 8:16 PM, Sinan Kaya wrote:
> @@ -4056,7 +4056,7 @@ static int pci_parent_bus_reset(struct pci_dev *dev,
> int probe)
>
> pci_reset_bridge_secondary_bus(dev->bus->self);
>
> - return 0;
> + return pci_dev_wait(dev, "bus reset", 1000, 6);
> }
This doesn't solve t
From: Randy Dunlap
Add descriptive info to prompt string so that someone can know what
a Retrode is. Drop an unneeded blank line.
Signed-off-by: Randy Dunlap
Cc: Bastien Nocera
Cc: Jiri Kosina
Cc: Benjamin Tissoires
---
drivers/hid/Kconfig |3 +--
1 file changed, 1 insertion(+), 2 dele
Hi Felix,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: cd4175b11685b11c40e31a03e05084cc212b0649
commit: 70539bd79500245cbb4c7af00572fcce540d0105 drm/amd: Update MEC HQD
loading code for KFD
date: 6 weeks ago
co
Hi Dong,
[auto build test ERROR on clk/clk-next]
[also build test ERROR on v4.14-rc1 next-20170922]
[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/Dong-Aisheng/clk-bulk-add-of_clk_bulk_get/20170
Hi Jaharkes and Coda filesystem developers,
I am resending the email on a potential race condition bug I found in the
Coda filesystem as well as the patch I propose. Please feel free to comment
whether you think this is a serious problem and whether the patch will work.
Thank you.
Best Regards,
M
Signed-off-by: yuzhoujian
---
tools/perf/builtin-script.c | 190 +++-
1 file changed, 100 insertions(+), 90 deletions(-)
diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
index 936af8b..065bea7 100644
--- a/tools/perf/builtin-script.c
Introduce a new option to print trace output to files named by the
monitored events and update perf-script documentation accordingly.
Shown below is output of perf script command with the newly introduced
option.
$perf record -e cycles -e context-switches -ag -- sleep 10
$per
Signed-off-by: yuzhoujian
---
tools/perf/builtin-script.c | 3 +++
tools/perf/util/tool.h | 1 +
2 files changed, 4 insertions(+)
diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
index 9092de0..936af8b 100644
--- a/tools/perf/builtin-script.c
+++ b/tools/perf/builtin-s
Signed-off-by: yuzhoujian
---
tools/perf/builtin-script.c | 178 ++--
1 file changed, 89 insertions(+), 89 deletions(-)
diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
index 065bea7..271dfc4 100644
--- a/tools/perf/builtin-script.c
+
Signed-off-by: yuzhoujian
---
tools/perf/builtin-script.c | 404
1 file changed, 220 insertions(+), 184 deletions(-)
diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
index 271dfc4..6182859 100644
--- a/tools/perf/builtin-script.c
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: cd4175b11685b11c40e31a03e05084cc212b0649
commit: d3202d1981dc5a5f03f9afc96480619b48b60124 media: solo6x10: export
hardware GPIO pins 8:31 to gpiolib interface
date: 7 weeks ago
config: x86_64-randconfig-a0
Hi Huacai,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.14-rc1 next-20170922]
[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/Huacai-Chen/dma-mapping-Introduce-device_is_c
Hi,
On Sep 6 2017 19:22, SF Markus Elfring wrote:
From: Markus Elfring
Date: Wed, 6 Sep 2017 11:40:53 +0200
Add jump targets so that a bit of exception handling can be better reused
at the end of this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus E
This is the remaining "general" change in the security tree for v4.14,
following the direct merging of SELinux (+ TOMOYO), AppArmor, and seccomp.
That's everything now for the security tree except IMA, which will follow
shortly (I've been traveling for the past week with patchy internet).
Ple
Currently, the aes_ccm.c and aes_gcm.c are almost line by line
copy of each other. This patch reduce code redundancy by moving
the code in these two files to crypto/aead_api.c to make it a
higher level aead api. The aes_ccm.c and aes_gcm.c are removed
and all the functions are now implemented in th
Replace all occurences of dev_info/err/dbg with DRM_DEV_INFO/
ERROR/DEBUG as we have DRM_DEV_* variants of drm print macros
Done using following coccinelle semantic patch
@r@
@@
(
-dev_info
+DRM_DEV_INFO
|
-dev_err
+DRM_DEV_ERROR
|
-dev_dbg
+DRM_DEV_DEBUG
)
Signed-off-by: Harsha Sharma
---
dri
If we don't find a matching device node, we must free the memory allocated
in 'omap_dmm' a few lines above.
Fixes: 7cb0d6c17b96 ("drm/omap: fix TILER on OMAP5")
Signed-off-by: Christophe JAILLET
---
drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Looks good,
Reviewed-by: Sagi Grimberg
On Sat, Sep 23, 2017, Yang Shi wrote：
>
> Kernel may panic when oom happens without killable process sometimes it
> is caused by huge unreclaimable slabs used by kernel.
>
> Although kdump could help debug such problem, however, kdump is not
> available on all architectures and it might be malfunc
Hi Daniel,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: cd4175b11685b11c40e31a03e05084cc212b0649
commit: dc11bae78529526605c5c45c369c9512fd012093 clocksource/drivers: Add
timer-of common init routine
date: 3 mo
All sanity checks in this function set 'sdmac->status = DMA_ERROR' if
something looks wrong, except if the byte count or the address don't match
the bus width.
Fix it and report the error in status in such a case.
Signed-off-by: Christophe JAILLET
---
Untested, so please review carefuly.
---
dr
Hi Thomas,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: cd4175b11685b11c40e31a03e05084cc212b0649
commit: d3488649dcd23b7a6e63895274ec69f80e92d4ed um: Fix CONFIG_GCOV for
modules.
date: 10 days ago
config: um-al
On Sun, 24 Sep 2017, Harsha Sharma wrote:
> Replace all occurences of dev_info/err/dbg with DRM_DEV_INFO/
> ERROR/DEBUG as we have DRM_DEV_* variants of drm print macros
> Done using following coccinelle semantic patch
Some calls after under comments. They could be dropped.
Some calls appear
101 - 147 of 147 matches
Mail list logo
