On Fri, Oct 20, 2017 at 12:20:19PM -0500, Alex Elder wrote:
> No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove
> the code, and remove the config option from the arm64 defconfig.
>
> Suggested-by: Stephen Boyd
> Signed-off-by: Alex Elder
> Acked-by: Bjorn Andersson
Acked-by:
On Wed, Oct 25, 2017 at 10:15:35AM +0800, taoyuhong wrote:
> From: Yuhong Tao
>
> When tty_open() is opening a serial tty at the first time, after
> alloc_tty_struct() is called, before tty->ops->open() is finished.
> Serial driever like pl011 on ARM is ready to setup kworker threads
> to receive
On Fri, Oct 20, 2017 at 12:20:21PM -0500, Alex Elder wrote:
> No Qualcomm SoC requires the "phy-qcom-8x16-usb.c" USB phy driver
> support any more. Remove the code, and remove the config option
> from the arm64 defconfig.
>
> Suggested-by: Stephen Boyd
> Signed-off-by: Alex Elder
> Acked-by: Bj
On Fri, Oct 20, 2017 at 12:20:20PM -0500, Alex Elder wrote:
> No Qualcomm SoC requires the "phy-msm-usb.c" USB phy driver support
> any more. Remove the code, and remove the config option from the
> arm64 defconfig.
>
> Suggested-by: Stephen Boyd
> Signed-off-by: Alex Elder
> Acked-by: Bjorn An
On Tue, Oct 24, 2017 at 05:26:53PM -0500, Tom Gall wrote:
>
> > On Oct 24, 2017, at 8:03 AM, Greg Kroah-Hartman
> > wrote:
> >
> > This is the start of the stable review cycle for the 4.9.59 release.
> > There are 48 patches in this series, all will be posted as a response
> > to this one. If
On Tue, Oct 24, 2017 at 05:20:20PM -0700, Stephen Boyd wrote:
> On 10/20, Alex Elder wrote:
> > This series deletes three config options related to USB on Qualcomm
> > SoCs from the arm64 "defconfig", along with the code that they
> > enable. The code is no longer needed by any Qualcomm hardware.
This patch just simply moves tegra_thermctl_set_trip_temp() behind
those function implementations so that it can remove those forward
declarations.
Signed-off-by: Nicolin Chen
---
drivers/thermal/tegra/soctherm.c | 103 ++-
1 file changed, 47 insertions(+), 56
Hi Claudiu,
Thanks for your comments.
I updated this file, according to your suggestions.
Please have a review.
Regards
Zhi
On Tue, 2017-10-24 at 16:25 +0300, m18063 wrote:
> Hi Zhi,
>
> Please see my answer below.
>
> On 23.10.2017 14:13, Zhi Mao wrote:
> > Hi Claudiu
> >
> > please check th
On Mon, Oct 23, 2017 at 03:53:00PM +0100, David Howells wrote:
> j...@suse.com wrote:
>
> > hm... patch 4 only prevents write_mem() but not read_mem().
> > Or I missed anything?
>
> Actually, yes, as it happens, patch 11 prevents you from even opening /dev/mem
> and /dev/kmem by locking down open
On Mon, 2017-10-23 at 11:08 +0900, Byungchul Park wrote:
> On Sun, Oct 22, 2017 at 02:34:56PM +, Bart Van Assche wrote:
> > On Sat, 2017-10-21 at 11:23 +0900, Byungchul Park wrote:
> > > On Sat, Oct 21, 2017 at 4:58 AM, Bart Van Assche
> > > wrote:
> > > > As explained in another e-mail threa
On 2017/10/25 14:56, Greg KH wrote:
> On Wed, Oct 25, 2017 at 02:30:56PM +0800, Chen Feng wrote:
>> Hi Ted,
>>
>> On 2017/10/24 18:25, Theodore Ts'o wrote:
>>> On Tue, Oct 24, 2017 at 11:09:27AM +0200, Greg KH wrote:
On Tue, Oct 24, 2017 at 03:44:17PM +0800, Chen Feng wrote:
> [pid:11940
On Tue 24-10-17 23:51:30, Greg Thelen wrote:
> Michal Hocko wrote:
[...]
> > I am definitely not pushing that thing right now. It is good to discuss
> > it, though. The more kernel allocations we will track the more careful we
> > will have to be. So maybe we will have to reconsider the current
>
On Tue, Oct 24, 2017 at 11:40:38AM -0700, Andrey Smirnov wrote:
> On Tue, Oct 24, 2017 at 8:13 AM, Johan Hovold wrote:
> > On Mon, Oct 23, 2017 at 11:30:54AM +0200, Pavel Machek wrote:
> >> Hi!
> >>
> >> > > drivers/platform/Kconfig| 2 +
> >> > > drivers/platform/Makefile | 1 +
Hi Huacai,
On 2017-10-25 03:22, 陈华才 wrote:
Hi, Marek
Patch3 is needed for stable, but Patch3 depend on Patch1 and Patch2.
Then patch #3 has to be reworked. First change scsi to align the block
queue to dma_get_cache_alignment(). This will be safe in all cases and
it will not hurt memory usa
On 2017-10-24 at 13:35:05 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
[cut]
> @@ -63,10 +60,14 @@ static bool default_suspend_ok(struct de
>
> spin_unlock_irqrestore(&dev->power.lock, flags);
>
> - if (constraint_ns < 0)
> + if (constraint_ns == 0)
>
A spin lock is used in the irq-mvebu-gicp driver, but it is never
initialized. This patch adds the missing spin_lock_init() call in the
driver's probe function.
Fixes: a68a63cb4dfc ("irqchip/irq-mvebu-gicp: Add new driver for Marvell GICP")
Signed-off-by: Antoine Tenart
---
drivers/irqchip/irq-m
On Tue, Oct 24, 2017 at 05:25:16PM -0700, Andrei Vagin wrote:
> On Wed, Oct 25, 2017 at 12:48:14AM +0300, Cyrill Gorcunov wrote:
> > Currently unix_diag_vfs structure reports unix socket inode
> > as u32 value which of course doesn't fit to ino_t type and
>
> BTW: As far as I understand, it is not
On Wed, Oct 25, 2017 at 01:22:22PM +0900, David Miller wrote:
> From: Herbert Xu
> Date: Wed, 25 Oct 2017 12:05:41 +0800
>
> > On Tue, Oct 24, 2017 at 05:48:42PM +0900, David Miller wrote:
> >>
> >> This discussion has happened before.
> >>
> >> But I'll explain the conclusion here for your ben
Reviewed-by: Matthew Wilcox
> -Original Message-
> From: Clement Courbet [mailto:cour...@google.com]
> Sent: Tuesday, October 24, 2017 6:52 AM
> To: Arnd Bergmann ; Rasmus Villemoes
> ; Andrew Morton ;
> Matthew Wilcox ; Yury Norov
>
> Cc: Clement Courbet ; Ingo Molnar
> ; linux-a...@vge
On 10/24/2017 08:58 PM, Rob Herring wrote:
On Wed, Oct 18, 2017 at 02:47:00PM +0200, Maciej Purski wrote:
Some regulators require keeping their voltage spread below defined
max_spread.
Add properties to provide information on regulators' coupling.
Signed-off-by: Maciej Purski
---
Document
On Wed, Oct 25, 2017 at 08:44:38AM +0200, SF Markus Elfring wrote:
> >> The script “checkpatch.pl” pointed information out like the following.
> >>
> >> Comparison to NULL could be written !…
> >>
> >> Thus fix the affected source code places.
> >>
> >
> > This one is fine
>
> This kind of feedba
On 2017-10-24 at 13:23:23 +0200, Rafael J. Wysocki wrote:
> On Tue, Oct 24, 2017 at 10:49 AM, Rafael J. Wysocki
> wrote:
> > On Tuesday, October 24, 2017 7:54:09 AM CEST Ramesh Thomas wrote:
> >> On 2017-10-20 at 13:27:34 +0200, Rafael J. Wysocki wrote:
> >> > From: Rafael J. Wysocki
> >> >
>
>
Hi Juergen,
[...]
I like your original method.
So, I try to fix it by moving the native_pv_lock_init() from
native_smp_prepare_boot_cpu() to native_smp_prepare_cpus().
Hmm, this might work, but the Xen case has to be modified (same for
my more general solution), as xen_init_spinlocks() is sti
Hi Antoine,
On mer., oct. 25 2017, Antoine Tenart
wrote:
> A spin lock is used in the irq-mvebu-gicp driver, but it is never
> initialized. This patch adds the missing spin_lock_init() call in the
> driver's probe function.
>
> Fixes: a68a63cb4dfc ("irqchip/irq-mvebu-gicp: Add new driver for
On Oct 24 2017 or thereabouts, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 24 Oct 2017 20:52:19 +0200
>
> * Replace the specification of data structures by pointer dereferences
> as the parameter for the operator "sizeof" to make the corresponding size
> determination a bit s
Add generated scsi_devinfo_tbl.c into .gitignore.
Signed-off-by: Jeffy Chen
---
drivers/scsi/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/scsi/.gitignore b/drivers/scsi/.gitignore
index c89ae9a04399..e2956741fbd1 100644
--- a/drivers/scsi/.gitignore
+++ b/drivers/scsi/
>> Would you like to support Unicode characters there?
>
> Multiple people have answered this question already and I have answered
> it multiple times.
I found the corresponding feedback not sufficient so far to reach
a final consensus.
Will this topic evolve any further?
Regards,
Markus
On Wed, 25 Oct 2017, 冯锐 wrote:
> > On Tue, 24 Oct 2017, Arnd Bergmann wrote:
> >
> > > On Mon, Oct 23, 2017 at 11:35 AM, Lee Jones wrote:
> > > > On Thu, 19 Oct 2017, Arnd Bergmann wrote:
> > > >
> > > >> On Thu, Oct 19, 2017 at 5:22 AM, wrote:
> > > >> > From: Rui Feng
> > > >> >
> > > >> >
On Wed, Oct 25, 2017 at 11:50:58AM +0800, Nickey Yang wrote:
> Replace the hardcoded register address numerical values with macros to
> clarify the code.
>
> Signed-off-by: Nickey Yang
Reviewed-by: Sean Paul
> ---
> drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 129
> ++---
On Wed, Oct 25, 2017 at 11:50:59AM +0800, Nickey Yang wrote:
> As MIPI PHY document show, icpctrl<3..0> and lpfctrl<5..0>
> should depend on frequency,so fix it.
>
> Reviewed-by: Sean Paul
> Reviewed-by: Matthias Kaehlcke
> Signed-off-by: Nickey Yang
> ---
In future, please list the difference
Is this a patch you might consider?
Thanks
...Juerg
On 10/04/2017 10:24 AM, Juerg Haefliger wrote:
> alloc_metapage can return a NULL pointer so check for that. And also emit
> an error message if that happens.
>
> Signed-off-by: Juerg Haefliger
> ---
> fs/jfs/jfs_metapage.c | 20
On Wed, Oct 25 2017 at 9:23:26 am BST, Antoine Tenart
wrote:
> A spin lock is used in the irq-mvebu-gicp driver, but it is never
> initialized. This patch adds the missing spin_lock_init() call in the
> driver's probe function.
>
> Fixes: a68a63cb4dfc ("irqchip/irq-mvebu-gicp: Add new driver for
On 25/10/17 09:35, Dou Liyang wrote:
> Hi Juergen,
>
> [...]
>>> I like your original method.
>>> So, I try to fix it by moving the native_pv_lock_init() from
>>> native_smp_prepare_boot_cpu() to native_smp_prepare_cpus().
>>
>> Hmm, this might work, but the Xen case has to be modified (same for
On Wed, Oct 25, 2017 at 11:51:00AM +0800, Nickey Yang wrote:
> This patch correct Feedback divider setting:
> 1、Set Feedback divider [8:5] when HIGH_PROGRAM_EN
> 2、Due to the use of a "by 2 pre-scaler," the range of the
> feedback multiplication Feedback divider is limited to even
> division number
From: rui_feng
Because Realtek PCIE card reader driver is a pcie driver,
and it bridges mmc subsystem and memstick subsystem, it's
not a mfd driver. Greg and Lee Jones had a discussion about
where to put the driver, the result is that misc is a good
place for it, so I move all files to misc. If I
On Fri, Oct 20, 2017 at 09:38:05AM +0200, Linus Walleij wrote:
> On Fri, Oct 20, 2017 at 4:57 AM, Andrew Jeffery wrote:
>
> > Literally.
> >
> > I expect "lose" was meant here, rather than "loose", though you could
> > feasibly
> > use a somewhat uncommon definition of "loose" to mean what would
On Wed, Oct 25, 2017 at 11:51:01AM +0800, Nickey Yang wrote:
> This patch add dual mipi channel support:
> 1.add definition of dsi1 register and grf operation.
> 2.dsi0 and dsi1 will work in master and slave mode
> when driving dual mipi panel.
>
> Signed-off-by: Nickey Yang
> ---
In the last re
On 10/24/2017 08:42 PM, Jonathan Cameron wrote:
>
>
> On 24 October 2017 17:41:38 BST, Rob Herring wrote:
>> On Tue, Oct 17, 2017 at 03:15:43PM +0200, Fabrice Gasnier wrote:
>>> STM32H7 ADC channels may be configured either as single-ended or
>>> differential.
>>> Add 'st,adc-diff-channels' prop
On Wed, Oct 25, 2017 at 01:56:02AM +, Levin, Alexander (Sasha Levin) wrote:
> When regulators are successfully registered, we check to see if the
> regulator is a supply for any other registered regulator and if so
> add the new regulator as the supply for the existing regulator(s).
This had
Hi Juergen,
How about moving the check of xen_pvspin into native_pv_lock_init()
like below?
This would leak xen_pvspin to non-Xen code. I'd rather do the
Oops, yes, I made the mistake. Please ignore it.
static_branch_disable() in xen_init_lock_cpu() if cpu == 0.
Yes. I will test it. :-
> I run Gentoo Linux on my alphas, with latest git kernels for test.
> 4.13.0 worked well on 3 alphas but 4.13.0-09217-g5969d1bb3082 hangs on
> boot on all 3 of them. Tried bisecting on PC164, got into unrelated
> stuff, so probably it does not trigger always. Retried bisecting on
> DS10L. On t
On Fri, Oct 20, 2017 at 07:02:27PM +1030, Andrew Jeffery wrote:
> On Fri, 2017-10-20 at 09:43 +0200, Linus Walleij wrote:
> > On Fri, Oct 20, 2017 at 9:17 AM, Linus Walleij
> > wrote:
> > > > > On Fri, Oct 20, 2017 at 5:37 AM, Andrew Jeffery
> > > > > wrote:
> > >
> > > > GPIO state reset tole
On Fri, Oct 20, 2017 at 07:32:53PM +1030, Andrew Jeffery wrote:
> On Fri, 2017-10-20 at 09:27 +0200, Linus Walleij wrote:
> > I don't see it as helpful to give userspace control over whether the line
> > is persistent or not. It is more reasonable to assume persistance for
> > userspace use cases,
From: Rui Feng
Because Realtek PCIE card reader driver is a pcie driver,
and it bridges mmc subsystem and memstick subsystem, it's
not a mfd driver. Greg and Lee Jones had a discussion about
where to put the driver, the result is that misc is a good
place for it, so I move all files to misc. If I
On 10/25/2017 12:36 AM, Andrea Scian - DAVE Embedded Systems wrote:
>
> Il 24/10/2017 07:51, Cédric Le Goater ha scritto:
>> On 10/17/2017 11:16 AM, Andrea Scian - DAVE Embedded Systems wrote:
>>>
On 10/17/2017 10:20 AM, Andrea Scian - DAVE Embedded Systems wrote:
>
> Il 17/10/2017 10
On Wed, Sep 13, 2017 at 10:34:26PM +0200, Paolo Bonzini wrote:
> On 13/09/2017 19:23, Zdenek Kaspar wrote:
> > On 03/27/2017 02:38 PM, Paolo Bonzini wrote:
> >> Virtual NMIs are only missing in Prescott and Yonah chips. Both are
> >> obsolete
> >> for virtualization usage---Yonah is 32-bit only e
On Wed, 25 Oct 2017, rui_f...@realsil.com.cn wrote:
> From: rui_feng
>
> Because Realtek PCIE card reader driver is a pcie driver,
> and it bridges mmc subsystem and memstick subsystem, it's
> not a mfd driver. Greg and Lee Jones had a discussion about
> where to put the driver, the result is th
Bjorn,
On Wednesday 25 October 2017 01:29 AM, Bjorn Helgaas wrote:
> On Thu, Oct 19, 2017 at 06:13:29PM +0530, Faiz Abbas wrote:
>> Enable support for printing the LTSSM link state for debugging PCI
>> when link is down.
>>
>> Signed-off-by: Faiz Abbas
>
> Applied with Kishon's ack to pci/host-d
On Oct 4, 2017, nol...@jabra.com wrote:
> On Oct 3, 2017, benjamin.tissoi...@redhat.com wrote:
>
> > Niels found an issue with v1 of the series, while compiling the usbhid
> > module as a separate .ko.
> >
> > Sending a v2 with the proper From: field fixed now.
> >
>
> I have built it on for-next
I run Gentoo Linux on my alphas, with latest git kernels for test.
4.13.0 worked well on 3 alphas but 4.13.0-09217-g5969d1bb3082 hangs on
boot on all 3 of them. Tried bisecting on PC164, got into unrelated
stuff, so probably it does not trigger always. Retried bisecting on
DS10L. On the first t
On Tue, Oct 24, 2017 at 07:50:06PM +0530, Ravi Bangoria wrote:
> Perf top is often crashing at very random locations on powerpc.
> After investigating, I found the crash only happens when sample
> is of zero length symbol. Powerpc kernel has many such symbols
> which does not contain length details
From: Yael Chemla
Current implementation makes multiple crypto API calls for a single
block, forcing underlying crypto tfm implementation to "stop & go",
leading to under utilization of CPU (e.g. SIMD state saves) or HW
engines. To fix it unify calls to crypto init/update/final into a digest
call
On Wed, Oct 25, 2017 at 03:34:16PM +1030, Andrew Jeffery wrote:
> Reset tolerance is added to gpiolib with the introduction of a new
> pinconf parameter propagating the request to hardware. The existing
> persistence support for sleep is augmented to include reset tolerance
> if the GPIO driver pro
Hi Zhi,
I added few cosmetic things below.
Thanks,
Claudiu
On 25.10.2017 09:55, Zhi Mao wrote:
> Add support to MT2712 and MT7622.
> Due to register offset address of pwm7 for MT2712 is not fixed 0x40,
> add mtk_pwm_reg_offset array for pwm register offset.
> Add NULL pointer checking for "dat
On Wed, Oct 25, 2017 at 11:12:09AM +0900, Namhyung Kim wrote:
> The addr_location->addr should have relative address to be passed to
> hist entry so that it can compare with others which might come from a
> different address space.
>
> The callchain_cursor_node->ip already has a relative address t
On 10/23/2017 01:57 PM, Zhi Mao wrote:
> Add support to MT2712 and MT7622.
> Due to register offset address of pwm7 for MT2712 is not fixed 0x40,
> add mtk_pwm_reg_offset array for pwm register offset.
> Add NULL pointer checking for "pc->data".
>
> Signed-off-by: Zhi Mao
> ---
Reviewed-by: Ma
On Tue, Oct 24, 2017 at 05:40:45PM +0200, Ingo Molnar wrote:
>
> * Will Deacon wrote:
>
> > Ingo, Peter,
> >
> > Would you be willing to merge this via -tip, please? I'm happy to
> > rebase/repost as required, but the code is in good shape now.
>
> Sure, will do it tomorrow!
Yeah, ACK on this
On 23/10/2017 11:58, Benjamin Gaignard wrote:
> Add this exit function to be able to undo what have been done
> in timer_of_init().
>
> Signed-off-by: Benjamin Gaignard
I will take this one for 4.15
Thanks
-- Daniel
> ---
> drivers/clocksource/timer-of.c | 12
> drivers/clocks
On 10/24/2017 10:38 AM, Stephen Boyd wrote:
> On 10/19, Matthias Brugger wrote:
>>
>>
>> On 10/19/2017 04:48 AM, Weiyi Lu wrote:
>>> This series is based on v4.14-rc1 and composed of
>>> clock control (PATCH 1-4) and scpsys control (PATCH 5-9)
>>>
>>> changes since v4:
>>> - Refine scpsys and inf
On 10/11/2017 03:18 PM, Peter Zijlstra wrote:
> On Mon, Oct 09, 2017 at 06:57:46PM +0530, Prateek Sood wrote:
>> On 09/07/2017 11:21 PM, Peter Zijlstra wrote:
>
>>> But if you invert these locks, the need for cpuset_hotplug_workfn() goes
>>> away, at least for the CPU part, and we can make in sync
On Tue, 24 Oct 2017 22:29:00 +
"Wang, Liang-min" wrote:
> > -Original Message-
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Tuesday, October 24, 2017 6:07 PM
> > To: Wang, Liang-min
> > Cc: Kirsher, Jeffrey T ; k...@vger.kernel.org;
> > linux-...@vger.kerne
> On Wed, 25 Oct 2017, rui_f...@realsil.com.cn wrote:
>
> > From: rui_feng
> >
> > Because Realtek PCIE card reader driver is a pcie driver, and it
> > bridges mmc subsystem and memstick subsystem, it's not a mfd driver.
> > Greg and Lee Jones had a discussion about where to put the driver, the
>
We discovered some problems in the latest fsnotify/fanotify codebase with
the help of a stress test (Xiong Zhou is working on upstreaming it to
fstests).
This series attempts to fix these. With the patch applied the stress test
passes.
Please review/test.
Changes in v2 (only cosmetic fixes, no
After having gone through a ref-unref for the mark, dereferencing the group
(e.g. in fsnotify_compare_groups()) is wrong since the group may be
completely gone by that time. So before continuing to traverse the mark
list, check if the mark is still attached.
This is done in the generic case, not
Use helpers to get first and next marks from connector.
Also get rid of inode_node/vfsmount_node local variables, which just refers
to the same objects as iter_info. There was an srcu_dereference() for
foo_node, but that's completely superfluous since we've already done it
when obtaining foo_node
The only negative from this patch should be an addition of 32bytes to
'struct fsnotify_group' if CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not
defined.
Signed-off-by: Miklos Szeredi
---
fs/notify/fanotify/fanotify.c | 30 +++--
fs/notify/fanotify/fanotify.h | 8 ++-
fs/notify/fanoti
If fsnotify_prepare_user_wait() fails, we leave the event on the
notification list. Which will result in a warning in
fsnotify_destroy_event() and later use-after-free.
Instead of adding a new helper to remove the event from the list in this
case, I opted to move the prepare/finish up into fanoti
Blind increment of group's user_waits is not enough, we could be far enough
in the group's destruction that it isn't taken into account (i.e. grabbing
the mark ref afterwards doesn't guarantee that it was the ref coming from
the _group_ that was grabbed).
Instead we need to check (under lock) that
This patch doesn't actually fix any bug, just paves the way for fixing mark
and group pinning.
Signed-off-by: Miklos Szeredi
Cc: # v4.12
---
fs/notify/mark.c | 89 ++--
1 file changed, 41 insertions(+), 48 deletions(-)
diff --git a/fs/notify/
We may fail to pin one of the marks in fsnotify_prepare_user_wait() when
dropping the srcu read lock, resulting in use after free at the next
iteration.
Solution is to store both marks in iter_info instead of just the one we'll
be sending the event for.
Signed-off-by: Miklos Szeredi
Fixes: 9385a
On Wed, Oct 25, 2017 at 12:21 AM, Jarkko Sakkinen
wrote:
> I noticed when making slides for KS that the naming for event log stuff
> that the naming is so broken that it is hard to understand the code.
> Here it really would make sense to have a patch set just to clean up the
> cruft.
Agreed and
On Wed, Oct 25, 2017 at 09:39:39AM +0200, SF Markus Elfring wrote:
> >> Would you like to support Unicode characters there?
> >
> > Multiple people have answered this question already and I have answered
> > it multiple times.
>
> I found the corresponding feedback not sufficient so far to reach
* Paul E. McKenney wrote:
> Hello, Ingo,
>
> This series is a first step towards making the core kernel no longer
> need to consider DEC Alpha as a special case. This is accomplished
> by two sets of patches, followed by a Coccinelle script:
>
> 1.Patches 1/19 through 15/19 in the followi
On Wed, Oct 25, 2017 at 07:39:48AM +, Matthew Wilcox wrote:
> Hang on, don't tell me you found this by inspection. Are you not running the
> bitmap testcase, enabled by CONFIG_TEST_BITMAP? Either that should be
> producing an error, or there's a missing test case, or your inspection is
> w
Hi Jiri,
On Wed, Oct 25, 2017 at 10:34:32AM +0200, Jiri Olsa wrote:
> On Wed, Oct 25, 2017 at 11:12:09AM +0900, Namhyung Kim wrote:
> > The addr_location->addr should have relative address to be passed to
> > hist entry so that it can compare with others which might come from a
> > different addre
I have a donation gift for you. Reply asap
Other people who have sent me fuzzer test reproducers are able to
reproduce syzkaller logs into a simple C program. Can you explain to
me what the heck:
> r3 = syz_open_dev$urandom(&(0x7f00a000)="2f6465762f7572616e646f6d00",
> 0x0, 0x0)
means?
- Ted
Current implementation makes multiple crypto API calls for a single
block, forcing underlying crypto tfm implementation to "stop & go",
leading to under utilization of CPU (e.g. SIMD state saves) or HW
engines. To fix it unify calls to crypto init/update/final into a digest
call with a single sg wh
> On 24 Oct 2017, at 17.30, Kees Cook wrote:
>
> In preparation for unconditionally passing the struct timer_list pointer to
> all timer callbacks, switch to using the new timer_setup() and from_timer()
> to pass the timer pointer explicitly.
>
> Cc: Matias Bjorling
> Cc: linux-bl...@vger.kerne
This patch will add two elements for perf_tool struct: per_event_dump
is used to mark the per-event-dump option, last_evsel_name is used
to save last evsel's name. Add a new struct perf_script_evsel to
save evsel's specific data. There are three elements in this new struct:
dump_evsel_fp is used to
Introduce a new option to dump 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 cs -ag -- sleep 1
$perf script --per-even
This patch will make all print functions receive the fp, add the
fp_selection_helper
function to select the fp(stdout or the dump_event fp) and open the dump file
for
all print functions. When the perf script is over, closes the dump_event file
and
calculates its size.
Changes since v4:
- the f
On Wed, Oct 25, 2017 at 10:45:48AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney wrote:
>
> > Hello, Ingo,
> >
> > This series is a first step towards making the core kernel no longer
> > need to consider DEC Alpha as a special case. This is accomplished
> > by two sets of patches, followed
Changes from v4
- Use a prefix "(completion)" instead of "(complete)" for completions
- Use a prefix "(wq_completion)" instead of "(complete)" for workqueue's map
- Use a prefix "(work_completion)" instead of "(complete)" for work's map
- Use a prefix "(gendisk_completion)" instead of "(complete)"
The workqueue added manual acquisitions to catch deadlock cases.
Now crossrelease was introduced, some of those are redundant, since
wait_for_completion() already includes the acquisition for itself.
Remove it.
Signed-off-by: Byungchul Park
---
include/linux/workqueue.h | 4 ++--
kernel/workque
CONFIG_LOCKDEP_COMPLETIONS uses "(complete)" as a prefix of lock name
for completion variable.
However, "complete" is a verb or adjective and lock symbol names
should be nouns. Use "(completion)" instead, for normal completions.
Suggested-by: Ingo Molnar
Signed-off-by: Byungchul Park
---
inclu
The boot parameter, crossrelease_fullstack, was introduced to control
whether to enable unwind in cross-release or not. Add a Kconfig doing
the same thing.
Suggested-by: Ingo Molnar
Signed-off-by: Byungchul Park
---
kernel/locking/lockdep.c | 4
lib/Kconfig.debug| 15 +
Darrick posted the following warning and Dave Chinner analyzed it:
> ==
> WARNING: possible circular locking dependency detected
> 4.14.0-rc1-fixes #1 Tainted: GW
> --
> loop0/31693 is t
Sometimes, we want to initialize completions with sparate lockdep maps
to assign lock classes as desired. For example, the workqueue code
needs to directly manage lockdep maps, since only the code is aware of
how to classify lockdep maps properly.
Provide additional macros initializing completions
From: Christoph Hellwig
Simplify the code by getting rid of the submit_bio_ret structure.
Signed-off-by: Christoph Hellwig
---
block/bio.c | 19 +--
1 file changed, 5 insertions(+), 14 deletions(-)
diff --git a/block/bio.c b/block/bio.c
index 5f5472e..99d0ca5 100644
--- a/bloc
Johan Hovold reported a heavy performance regression caused by lockdep
cross-release:
> Boot time (from "Linux version" to login prompt) had in fact doubled
> since 4.13 where it took 17 seconds (with my current config) compared to
> the 35 seconds I now see with 4.14-rc4.
>
> I quick bisect
Now that the performance regression is fixed, re-enable
CONFIG_LOCKDEP_CROSSRELEASE=y and CONFIG_LOCKDEP_COMPLETIONS=y.
Signed-off-by: Byungchul Park
---
lib/Kconfig.debug | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 3db9167.
By this patch, the lockdep_map structure takes no space if lockdep is
disabled, making a debug facility's impact on unreleated kernel less.
Thanks to this, we don't need #ifdef to sparate code due to the
lockdep_map structure.
Signed-off-by: Byungchul Park
---
include/linux/lockdep.h | 5 +
On Tue, Oct 24, 2017 at 11:36:48AM -0700, Arve Hjønnevåg wrote:
> On Tue, Oct 24, 2017 at 12:28 AM, Greg Kroah-Hartman
> wrote:
> > On Mon, Oct 23, 2017 at 11:18:52AM -0700, Arve Hjønnevåg wrote:
> >> On Sat, Oct 21, 2017 at 1:15 AM, Greg Kroah-Hartman
> >> wrote:
> >> > On Fri, Oct 20, 2017 at 0
On Tue, Oct 24, 2017 at 02:59:44PM +0200, Ingo Molnar wrote:
>
> * Jiri Olsa wrote:
>
> > I recently made some changes on threaded record, which are based
> > on Namhyungs time* API, which is needed to read/sort the data afterwards
> >
> > but I wasn't able to get any substantial and constant r
On Wed, Oct 25, 2017 at 11:35:39AM +0900, Namhyung Kim wrote:
> Hi Ingo,
>
> On Tue, Oct 24, 2017 at 03:25:23PM +0200, Ingo Molnar wrote:
> >
> > * Arnaldo Carvalho de Melo wrote:
> >
> > > Em Tue, Oct 24, 2017 at 02:59:44PM +0200, Ingo Molnar escreveu:
> > > >
> > > > * Jiri Olsa wrote:
> >
* Paul E. McKenney wrote:
> On Wed, Oct 25, 2017 at 10:45:48AM +0200, Ingo Molnar wrote:
> >
> > * Paul E. McKenney wrote:
> >
> > > Hello, Ingo,
> > >
> > > This series is a first step towards making the core kernel no longer
> > > need to consider DEC Alpha as a special case. This is acco
* Jiri Olsa wrote:
> On Tue, Oct 24, 2017 at 02:59:44PM +0200, Ingo Molnar wrote:
> >
> > * Jiri Olsa wrote:
> >
> > > I recently made some changes on threaded record, which are based
> > > on Namhyungs time* API, which is needed to read/sort the data afterwards
> > >
> > > but I wasn't able
From: Paul Mackerras [mailto:pau...@ozlabs.org]
> On Wed, Oct 25, 2017 at 07:39:48AM +, Matthew Wilcox wrote:
> > Hang on, don't tell me you found this by inspection. Are you not running
> > the
> bitmap testcase, enabled by CONFIG_TEST_BITMAP? Either that should be
> producing an error, or
(Added linux-pci to CC)
> > I run Gentoo Linux on my alphas, with latest git kernels for test.
> > 4.13.0 worked well on 3 alphas but 4.13.0-09217-g5969d1bb3082 hangs on
> > boot on all 3 of them. Tried bisecting on PC164, got into unrelated
> > stuff, so probably it does not trigger always. Re
1 - 100 of 749 matches
Mail list logo
