On Fri, 28 Jul 2017, Prarit Bhargava wrote:
> On 07/25/2017 09:00 AM, Peter Zijlstra wrote:
> Thanks for the above change. I can see that makes the code simpler.
>
> > Although I must strongly discourage using REALTIME, DST will make
> > untangling your logs an absolute nightmare. I would simply
Commit b6a1d093f96b ("PM / Domains: Extend generic power domain
debugfs") now creates a debugfs directory for each genpd based on the
name of the genpd. Currently no name is given to the genpd created by
ti_sci_pm_domains driver so because of this we see a NULL pointer
dereferences when it is acces
Hi,
On Thu, Jul 27, 2017 at 01:01:36PM +0800, Yong Deng wrote:
> Add binding documentation for Allwinner V3s CSI.
>
> Signed-off-by: Yong Deng
> ---
> .../devicetree/bindings/media/sun6i-csi.txt| 49
> ++
> 1 file changed, 49 insertions(+)
> create mode 100644 Docu
mpll0 clock is special compared to the other mplls. It needs another
bit (ssen) to be set to activate the fractional part the mpll divider
Fixes: 007e6e5c5f01 ("clk: meson: mpll: add rw operation")
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/clk-mpll.c | 7 +++
drivers/clk/meson/clkc.
Hi,
Thanks for the second iteration!
On Thu, Jul 27, 2017 at 01:01:35PM +0800, Yong Deng wrote:
> Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface
> and CSI1 is used for parallel interface. This is not documented in
> datasheet but by testing and guess.
>
> This patch impl
From: Chao Yu
This patch introduces f2fs_statfs_project, it enables to show usage
status of directory tree which is limited with project quota.
Signed-off-by: Chao Yu
---
fs/f2fs/super.c | 48
1 file changed, 48 insertions(+)
diff --git a/fs/f2
From: Chao Yu
This patch adds FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR ioctl interface
support for f2fs. The interface is kept consistent with the one
of ext4/xfs.
Signed-off-by: Chao Yu
---
fs/f2fs/f2fs.h | 3 +
fs/f2fs/file.c | 264 +++--
2 fi
From: Chao Yu
This patch supports to enable f2fs to accept quota information through
mount option:
- {usr,grp,prj}jquota=
- jqfmt=
Then, in ->mount flow, we can recover quota file during log replaying,
by this, journelled quota can be supported.
Signed-off-by: Chao Yu
---
Documentation/filesy
Commit b6a1d093f96b ("PM / Domains: Extend generic power domain
debugfs") now creates a debugfs directory for each genpd based on the
name of the genpd. Currently no name is given to the genpd created by
ti_sci_pm_domains driver so because of this we see a NULL pointer
dereferences when it is acces
Hi,
On 07/28/2017 11:33 AM, Dave Gerlach wrote:
> Commit b6a1d093f96b ("PM / Domains: Extend generic power domain
> debugfs") now creates a debugfs directory for each genpd based on the
> name of the genpd. Currently no name is given to the genpd created by
> ti_sci_pm_domains driver so because of
On 07/28/2017 07:23 AM, Tom Bogendoerfer wrote:
> On Thu, Jul 27, 2017 at 03:39:58PM -0700, Laura Abbott wrote:
>> I don't know the intricacies of the Mustang hardware but external
>> aborts have been a symptom of missing clocks on other hardware.
>
> you are right, it's a missing clock. For SGMII
On Wed, Jul 26, 2017 at 08:07:37PM +0300, Dmitry Safonov wrote:
> vDSO VMA address is saved in mm_context for the purpose of using
> restorer from vDSO page to return to userspace after signal handling.
>
> In Checkpoint Restore in Userspace (CRIU) project we place vDSO VMA
> on restore back to th
On Fri, Jul 28, 2017 at 03:38:15PM +, Mathieu Desnoyers wrote:
> > Which only leaves PPC stranded.. but the 'good' news is that mpe says
> > they'll probably need a barrier in switch_mm() in any case.
>
> As I pointed out in my other email, I plan to do this:
>
> --- a/kernel/sched/core.c
> +
Hi Cory,
On Wed, Jul 19, 2017 at 11:44 PM, Fabio Estevam wrote:
> From: Fabio Estevam
>
> Commit 3ca9b1ac28398c ("misc: eeprom_93xx46: Add support for a GPIO
> 'select' line.") introduced the optional usage of 'select-gpios'
> by using the gpiod API in a convoluted way.
>
> Rewrite the gpiod han
On Mon, Jul 24, 2017 at 06:36:57PM -0500, Josh Poimboeuf wrote:
>Add a new ORC unwinder which is enabled by CONFIG_ORC_UNWINDER. It
>plugs into the existing x86 unwinder framework.
>
>It relies on objtool to generate the needed .orc_unwind and
>.orc_unwind_ip sections.
>
>For more details on why O
On Fri, Jul 28, 2017 at 7:05 AM, Vlastimil Babka wrote:
> On 07/28/2017 11:30 AM, Peter Zijlstra wrote:
>> On Fri, Jul 28, 2017 at 09:45:16AM +0200, Vlastimil Babka wrote:
>>> [+CC PeterZ]
>>>
>>> On 07/27/2017 06:46 PM, Dima Zavin wrote:
In codepaths that use the begin/retry interface for re
On 7/28/17 9:35 AM, Dave Gerlach wrote:
Hi,
On 07/28/2017 11:33 AM, Dave Gerlach wrote:
Commit b6a1d093f96b ("PM / Domains: Extend generic power domain
debugfs") now creates a debugfs directory for each genpd based on the
name of the genpd. Currently no name is given to the genpd created by
ti_s
The aux_head and aux_wakeup members of struct ring_buffer are defined
using the local_t type, despite the fact that they are only accessed via
the perf_aux_output_* functions, which cannot race with each other for a
given ring buffer.
This patch changes the type of the members to long, so we can a
The aux_watermark member of struct ring_buffer represents the period (in
terms of bytes) at which wakeup events should be generated when data is
written to the aux buffer in non-snapshot mode. On hardware that cannot
generate an interrupt when the aux_head reaches an arbitrary wakeup index
(such as
Kalle Valo writes:
> Kalle Valo writes:
>
>> Arvind Yadav wrote:
>>
>>> attribute_group are not supposed to change at runtime. All functions
>>> working with attribute_group provided by work
>>> with const attribute_group. So mark the non-const structs as const.
>>>
>>> Signed-off-by: Arvind
Implement MEMBARRIER_CMD_PRIVATE_EXPEDITED with IPIs using cpumask built
from all runqueues for which current thread's mm is the same as the
thread calling sys_membarrier.
Scheduler-wise, it requires a memory barrier before and after context
switching between processes (which have different mm). T
Dan Williams and Christoph Hellwig have recently expressed doubt about
whether the rw_page() interface made sense for synchronous memory drivers
[1][2]. It's unclear whether this interface has any performance benefit
for these drivers, but as we continue to fix bugs it is clear that it does
have a
Hi Egil,
Egil Hjelmeland writes:
>>> +const struct lan9303_phy_ops lan9303_indirect_phy_ops = {
>>> + .phy_read = lan9303_indirect_phy_read,
>>> + .phy_write = lan9303_indirect_phy_write,
>>> +};
>>> +EXPORT_SYMBOL(lan9303_indirect_phy_ops);
>>
>> Isn't EXPORT_SYMBOL_GPL prefered over EXPOR
The rw_page() interface doesn't provide a clear performance benefit for the
BTT and has had a nonzero maintenance burden, so remove it.
Signed-off-by: Ross Zwisler
Suggested-by: Dan Williams
Suggested-by: Christoph Hellwig
Cc: Matthew Wilcox
---
drivers/nvdimm/btt.c | 15 ---
1 fi
The rw_page() interface doesn't provide a clear performance benefit for
PMEM and has had a nonzero maintenance burden, so remove it.
Signed-off-by: Ross Zwisler
Suggested-by: Dan Williams
Suggested-by: Christoph Hellwig
Cc: Matthew Wilcox
---
drivers/nvdimm/pmem.c | 21 -
> Since this piece of the ACPI pile is doing RAS, it is perhaps prudent if
> we at least paid attention to it and the direction it takes. So add Tony
> and me as reviewers.
Acked-by: Tony Luck
The rw_page() interface doesn't provide a clear performance benefit for
BRD and has had a nonzero maintenance burden, so remove it.
Signed-off-by: Ross Zwisler
Suggested-by: Dan Williams
Suggested-by: Christoph Hellwig
Cc: Matthew Wilcox
---
drivers/block/brd.c | 10 --
1 file changed
On Fri, Jul 28, 2017 at 12:54:29PM -0400, Mathieu Desnoyers wrote:
> Scheduler-wise, it requires a memory barrier before and after context
> switching between processes (which have different mm). The memory
> barrier before context switch is already present. After context switch,
> finish_lock_swit
On 07/28/2017 08:11 AM, Egil Hjelmeland wrote:
> Handle that MDIO read with no response return 0x.
>
> Signed-off-by: Egil Hjelmeland
Reviewed-by: Florian Fainelli
--
Florian
On Wed, Jul 26, 2017 at 05:11:38PM -0500, Grygorii Strashko wrote:
> With the low speed Ethernet connection CPDMA notification about packet
> processing can be received before CPTS TX timestamp event, which is set
> when packet actually left CPSW while cpdma notification is sent when packet
> pushe
On 07/28/2017 08:11 AM, Egil Hjelmeland wrote:
> lan9303_mdio_write()/_read() must multiply register number by 4 to get
> offset.
>
> Added some commments to the register definitions.
>
> Signed-off-by: Egil Hjelmeland
Reviewed-by: Florian Fainelli
--
Florian
On 07/28/2017 08:11 AM, Egil Hjelmeland wrote:
> Preparing for the following fix of MDIO phy access:
>
> Renamed functions that access PHY 1 and 2 indirectly through PMI
> registers.
>
> lan9303_port_phy_reg_wait_for_completion() to
> lan9303_indirect_phy_wait_for_completion()
>
> lan9303_por
- On Jul 28, 2017, at 12:46 PM, Peter Zijlstra pet...@infradead.org wrote:
> On Fri, Jul 28, 2017 at 03:38:15PM +, Mathieu Desnoyers wrote:
>> > Which only leaves PPC stranded.. but the 'good' news is that mpe says
>> > they'll probably need a barrier in switch_mm() in any case.
>>
>> As
On Fri, Jul 28, 2017 at 01:25:27PM +0200, Arnd Bergmann wrote:
> Hi Josh,
>
> I ran into two more warnings with the two patches you sent me in private,
> using gcc-7.1.1:
>
> lib/ubsan.o: warning: objtool: val_to_string.constprop.7()+0x97: leave
> instruction with modified stack frame
> .config:
On 07/28/2017 09:55 AM, Vivien Didelot wrote:
> Hi Egil,
>
> Egil Hjelmeland writes:
>
+const struct lan9303_phy_ops lan9303_indirect_phy_ops = {
+ .phy_read = lan9303_indirect_phy_read,
+ .phy_write = lan9303_indirect_phy_write,
+};
+EXPORT_SYMBOL(lan9303_indirect_phy
On Fri, Jul 28, 2017 at 2:13 AM, Christian König
wrote:
> Am 28.07.2017 um 03:43 schrieb Alex Deucher:
>>
>> On Tue, Jul 25, 2017 at 5:47 PM, Kees Cook wrote:
>>>
>>> As done for vega10 in commit 3ddd396f6b57 ("drm/amd/powerplay: Use
>>> designated initializers") mark other tableFunction entries
comp_algorithm_store() passes the size of the source buffer to strlcpy()
instead of the destination buffer size, fix this.
Signed-off-by: Matthias Kaehlcke
---
drivers/block/zram/zram_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/zram/zram_drv.c b/driver
On Fri, Jul 28, 2017 at 08:18:18AM -0400, Steven Rostedt wrote:
> On Thu, 27 Jul 2017 20:22:32 -0700
> "Paul E. McKenney" wrote:
>
> > On Thu, Jul 27, 2017 at 09:38:10PM -0400, Steven Rostedt wrote:
> > > On Mon, 24 Jul 2017 14:44:36 -0700
> > > "Paul E. McKenney" wrote:
> > >
> > > > There i
On Thu, Jul 27, 2017 at 6:43 PM, Alex Deucher wrote:
> On Tue, Jul 25, 2017 at 5:47 PM, Kees Cook wrote:
>> As done for vega10 in commit 3ddd396f6b57 ("drm/amd/powerplay: Use
>> designated initializers") mark other tableFunction entries with designated
>> initializers. The randstruct plugin requi
On Thu, Jul 27, 2017 at 12:43 PM, Paul E. McKenney
wrote:
> On Thu, Jul 27, 2017 at 10:20:14PM +0300, Avi Kivity wrote:
>> IPIing only running threads of my process would be perfect. In fact
>> I might even be able to make use of "membarrier these threads
>> please" to reduce IPIs, when I change t
- On Jul 28, 2017, at 1:15 PM, Andrew Hunter a...@google.com wrote:
> On Thu, Jul 27, 2017 at 12:43 PM, Paul E. McKenney
> wrote:
>> On Thu, Jul 27, 2017 at 10:20:14PM +0300, Avi Kivity wrote:
>>> IPIing only running threads of my process would be perfect. In fact
>>> I might even be able to
Hi all,
This is v3 of the livepatch shadow variable API. v2 collected a bunch
of great feedback on terminology, use cases and concurrency notes which
I've tried to incorporate here.
Here's a high-level sketch of v2 changes:
- Overall
- Squash into a one patch, makes for finding terms and c
Add exported API for livepatch modules:
klp_shadow_get()
klp_shadow_attach()
klp_shadow_get_or_attach()
klp_shadow_update_or_attach()
klp_shadow_detach()
klp_shadow_detach_all()
that implement "shadow" variables, which allow callers to associate new
shadow fields to existing data stru
> -Original Message-
> From: keesc...@google.com [mailto:keesc...@google.com] On Behalf Of
> Kees Cook
> Sent: Friday, July 28, 2017 1:16 PM
> To: Alex Deucher
> Cc: LKML; David Airlie; amd-gfx list; Maling list - DRI developers; Deucher,
> Alexander; Zhu, Rex; Koenig, Christian; Zhang, Haw
On 07/28/2017 12:02 PM, Ivan Khoronzhuk wrote:
On Wed, Jul 26, 2017 at 05:11:38PM -0500, Grygorii Strashko wrote:
With the low speed Ethernet connection CPDMA notification about packet
processing can be received before CPTS TX timestamp event, which is set
when packet actually left CPSW while
On Fri, Jul 28, 2017 at 10:15:49AM -0700, Andrew Hunter wrote:
> On Thu, Jul 27, 2017 at 12:43 PM, Paul E. McKenney
> wrote:
> > On Thu, Jul 27, 2017 at 10:20:14PM +0300, Avi Kivity wrote:
> >> IPIing only running threads of my process would be perfect. In fact
> >> I might even be able to make us
On Fri, Jul 28, 2017 at 10:56:01AM -0600, Ross Zwisler wrote:
> Dan Williams and Christoph Hellwig have recently expressed doubt about
> whether the rw_page() interface made sense for synchronous memory drivers
> [1][2]. It's unclear whether this interface has any performance benefit
> for these d
On Thu, Jul 27, 2017 at 12:06 PM, Paul E. McKenney
wrote:
> IPIin only those CPUs running threads in the same process as the
> thread invoking membarrier() would be very nice! There is some LKML
> discussion on this topic, which is currently circling around making this
> determination reliable on
Hi,
My system has been failing with recent kernels (4.12.x and 4.13-rc2)
with a NULL pointer dereference at the stack trace given at the end of
this email. This happens when simply running 'ib_write_bw -R '
with a Chelsio T6 (cxgb4). I've bisected (log attached) to find the
offending commit to be:
On Fri, Jun 09, 2017 at 03:45:54PM +0100, Will Deacon wrote:
> On Wed, Jun 07, 2017 at 06:15:02PM +0200, Peter Zijlstra wrote:
> > Commit:
> >
> > af2c1401e6f9 ("mm: numa: guarantee that tlb_flush_pending updates are
> > visible before page table updates")
> >
> > added smp_mb__before_spinlock
- On Jul 28, 2017, at 1:31 PM, Paul E. McKenney paul...@linux.vnet.ibm.com
wrote:
> On Fri, Jul 28, 2017 at 10:15:49AM -0700, Andrew Hunter wrote:
>> On Thu, Jul 27, 2017 at 12:43 PM, Paul E. McKenney
>> wrote:
>> > On Thu, Jul 27, 2017 at 10:20:14PM +0300, Avi Kivity wrote:
>> >> IPIing onl
On Wed 26-07-17 10:33:31, Michal Hocko wrote:
[...]
> @@ -312,7 +324,7 @@ int __ref __add_pages(int nid, unsigned long
> phys_start_pfn,
> }
>
> for (i = start_sec; i <= end_sec; i++) {
> - err = __add_section(nid, section_nr_to_pfn(i), want_memblock);
> + err
On Fri, Jul 28 2017 at 12:17pm -0400,
Bart Van Assche wrote:
> On Mon, 2017-04-17 at 12:09 -0700, Dan Williams wrote:
> > diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig
> > index b7767da50c26..1de8372d9459 100644
> > --- a/drivers/md/Kconfig
> > +++ b/drivers/md/Kconfig
> > @@ -200,6 +200,7
On Fri, Jul 28, 2017 at 04:48:47PM +, Levin, Alexander (Sasha Levin) wrote:
> Hey Josh,
>
> Syzkaller seems to trigger the following:
>
> ==
> BUG: KASAN: stack-out-of-bounds in __read_once_size
> include/linux/compiler.h:253 [i
On 07/28/2017 07:44 AM, Corentin Labbe wrote:
> On Fri, Jul 28, 2017 at 04:36:00PM +0200, Andrew Lunn wrote:
I've probably asked this before: Does the internal PHY use a different
PHY ID in registers 2 and 3?
>>>
>>> yes
>>>
>>> reg2: 0x0044
>>> reg3: 0X1500
>
> Copy/paste error, it
Commit bd8b2441742b ("NFS: Store the raw NFS access mask in the inode's
access cache") changed the way access mask is stored in struct
nfs_access_entry. However, there a are couple of places NFSv4 code where
it still uses the generic access bits instead of the raw NFS ones (e.g.
MAY_READ instead of
On 07/28, Abhishek Sahu wrote:
> On 2017-07-28 00:14, Stephen Boyd wrote:
> >
> >It looks like the two UBI clks that messed this up don't have an MN
> >counter, so instead of doing this maddness, just add a flag like
>
> I have given example for one of the RCG. IPQ8074 have more clocks for
> whi
On Tue, 2017-06-27 at 14:39 +0300, Tariq Toukan wrote:
>
> On 27/06/2017 10:40 AM, Colin King wrote:
> > From: Colin Ian King
> >
> > Trivial fix to spelling mistake in mlx5_ib_dbg message
> >
> > Signed-off-by: Colin Ian King
> > ---
> > drivers/infiniband/hw/mlx5/main.c | 2 +-
> > 1 file
Subject: [PATCH 0/6] Make ipc y2038 safe
The series aims to transition internal workings of ipc subsystem
to use y2038-safe types and apis.
The series is based on Al Viro's #work.ipc branch.
Deepa Dinamani (6):
ipc: Make sys_semtimedop() y2038 safe
ipc: mqueue: Replace timespec with timespec
time_t is not y2038 safe. Replace all uses of
time_t by y2038 safe time64_t.
Similarly, replace the calls to get_seconds() with
y2038 safe ktime_get_real_seconds().
Note that this preserves fast access on 64 bit systems,
but 32 bit systems need sequence counters.
The syscall interfaces themselves
struct timespec is not y2038 safe on 32 bit machines.
Replace timespec with y2038 safe struct timespec64.
Note that the patch only changes the internals without
modifying the syscall interfaces. This will be part
of a separate series.
Signed-off-by: Deepa Dinamani
---
fs/utimes.c | 23
struct timespec is not y2038 safe. Replace
all uses of timespec by y2038 safe struct timespec64.
Even though timespec is used here to represent timeouts,
replace these with timespec64 so that it facilitates
in verification by creating a y2038 safe kernel image
that is free of timespec.
The syscal
time_t is not y2038 safe. Replace all uses of
time_t by y2038 safe time64_t.
Similarly, replace the calls to get_seconds() with
y2038 safe ktime_get_real_seconds().
Note that this preserves fast access on 64 bit systems,
but 32 bit systems need sequence counters.
The syscall interface themselves
time_t is not y2038 safe. Replace all uses of
time_t by y2038 safe time64_t.
Similarly, replace the calls to get_seconds() with
y2038 safe ktime_get_real_seconds().
Note that this preserves fast access on 64 bit systems,
but 32 bit systems need sequence counters.
The syscall interfaces themselves
On 07/27/2017 05:36 PM, Josh Poimboeuf wrote:
> On Thu, Jul 27, 2017 at 04:43:58PM -0400, Joe Lawrence wrote:
>> On 07/20/2017 12:17 AM, Josh Poimboeuf wrote:
>>> - The post-patch and post-unpatch hooks will need to be run from either
>>> klp_complete_transition() or klp_module_coming/going(), de
struct timespec is not y2038 safe on 32 bit machines.
Replace timespec with y2038 safe struct timespec64.
Note that the patch only changes the internals without
modifying the syscall interface. This will be part
of a separate series.
Signed-off-by: Deepa Dinamani
---
ipc/sem.c | 12 ++--
On 7/28/2017 7:34 AM, Dietmar Eggemann wrote:
On 28/07/17 13:59, Peter Zijlstra wrote:
On Fri, Jul 28, 2017 at 01:16:24PM +0100, Dietmar Eggemann wrote:
IIRC the topology you had in mind was MC + DIE level with n (n > 2) DIE
level sched groups.
[...]
If I then start a 3rd loop, I see 100% 5
On Fri, Jul 28, 2017 at 10:37:25AM -0700, Andrew Hunter wrote:
> On Thu, Jul 27, 2017 at 12:06 PM, Paul E. McKenney
> wrote:
> > IPIin only those CPUs running threads in the same process as the
> > thread invoking membarrier() would be very nice! There is some LKML
> > discussion on this topic, w
El Thu, Jul 27, 2017 at 02:10:04PM -0700 Matthias Kaehlcke ha dit:
> Several functions use an enum type as parameter for an event/state,
> but are called in some locations with an argument of a different enum
> type. Adjust the interface of these functions to reality by changing the
> parameter to
Hi Shuah,
Thank you for your patches.
On Mon, 2017-07-24 at 15:07 -0600, Shuah Khan wrote:
> This patch series includes patches to convert sync test to use TAP13
> ksft framework. In addition, fix to sync test to differentiate
> between
> unsupported feature and access error when a non-root user
From: Mikael Pettersson
Date: Fri, 28 Jul 2017 10:45:15 +0200
> David Miller writes:
> > From: Mikael Pettersson
> > Date: Thu, 27 Jul 2017 21:45:25 +0200
> >
> > > Attempting to build strace-4.18 as sparcv9 code and run its test suite
> > > on a sparc64 machine (Sun Blade 2500 w/ 2 x USII
On Fri, Jul 28, 2017 at 12:54:29PM -0400, Mathieu Desnoyers wrote:
> Implement MEMBARRIER_CMD_PRIVATE_EXPEDITED with IPIs using cpumask built
> from all runqueues for which current thread's mm is the same as the
> thread calling sys_membarrier.
>
> Scheduler-wise, it requires a memory barrier befo
On Fri, Jul 28, 2017 at 02:08:33PM -0400, Joe Lawrence wrote:
> On 07/27/2017 05:36 PM, Josh Poimboeuf wrote:
> > On Thu, Jul 27, 2017 at 04:43:58PM -0400, Joe Lawrence wrote:
> >> On 07/20/2017 12:17 AM, Josh Poimboeuf wrote:
> >>> - The post-patch and post-unpatch hooks will need to be run from e
On Fri, Jul 28, 2017 at 12:52:34PM -0500, Josh Poimboeuf wrote:
>On Fri, Jul 28, 2017 at 04:48:47PM +, Levin, Alexander (Sasha Levin) wrote:
>> Hey Josh,
>>
>> Syzkaller seems to trigger the following:
>>
>> ==
>> BUG: KASAN: stack
On 07/27, Abhishek Sahu wrote:
> diff --git a/drivers/clk/qcom/clk-alpha-pll.c
> b/drivers/clk/qcom/clk-alpha-pll.c
> index 47a1da3..e6cde2d 100644
> --- a/drivers/clk/qcom/clk-alpha-pll.c
> +++ b/drivers/clk/qcom/clk-alpha-pll.c
> @@ -118,7 +118,10 @@ void clk_alpha_pll_configure(struct clk_alpha
On Thu, 27 Jul 2017, Zdenek Kabelac wrote:
> > Zdenek, you check this explanation by commenting out these last two
> > lines at the end of hub_port_connect() in drivers/usb/core/hub.c:
> >
> > if (hcd->driver->relinquish_port && !hub->hdev->parent)
> > hcd->driver->relinquish_port
Hi Kurt,
On 07/28/2017 03:02 PM, Kurt Van Dijck wrote:
The word 'max-arbitration-bitrate' makes the difference very clear.
I think you are mixing up ISO layer 1 and ISO layer 2.
In order to provide higher data throughput without putting extra limits
on transceiver & wire, the requirement fo
On 07/27, Abhishek Sahu wrote:
> Some of the Alpha PLL’s support dynamic update in which the
> frequency can be changed dynamically without turning off the PLL.
>
> This dynamic update requires the following sequence
>
> 1. Write the desired values to pll_l_val and pll_alpha_val.
> 2. Toggle pll_
v2->v3:
- Add a faster pruning rate when the free pool is closed to depletion.
- As suggested by James Bottomley, add an artificial delay waiting
loop before killing a negative dentry and properly clear the
DCACHE_KILL_NEGATIVE flag if killing doesn't happen.
- Add a new patch to tra
Having a limit for the number of negative dentries may have an
undesirable side effect that no new negative dentries will be allowed
when the limit is reached. This may have a performance impact on some
workloads.
To prevent this from happening, we need a way to prune the negative
dentries so that
There is performance concern about killing recently created negative
dentries. This should rarely happen under normal working condition. To
understand the extent of how often this negative dentry killing is
happening, the /proc/sys/fs/denty-state file is extended to track this
number. This allows u
The number of negative dentries currently in the system is now reported
in the /proc/sys/fs/dentry-state file.
Signed-off-by: Waiman Long
---
fs/dcache.c| 16 +++-
include/linux/dcache.h | 7 ---
2 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/fs/dcac
The negative dentry pruning is done on a specific super_block set
in the ndblk.prune_sb variable. If the super_block is also being
un-mounted concurrently, the content of the super_block may no longer
be valid.
To protect against such racing condition, a new lock is added to
the ndblk structure to
The number of positive dentries is limited by the number of files
in the filesystems. The number of negative dentries, however,
has no limit other than the total amount of memory available in
the system. So a rogue application that generates a lot of negative
dentries can potentially exhaust most o
From: David Miller
Date: Fri, 28 Jul 2017 11:27:41 -0700 (PDT)
> From: Mikael Pettersson
> Date: Fri, 28 Jul 2017 10:45:15 +0200
>
>> David Miller writes:
>> > From: Mikael Pettersson
>> > Date: Thu, 27 Jul 2017 21:45:25 +0200
>> >
>> > > Attempting to build strace-4.18 as sparcv9 code an
On Fri, Jul 28, 2017 at 7:23 AM, Tom Bogendoerfer
wrote:
> On Thu, Jul 27, 2017 at 03:39:58PM -0700, Laura Abbott wrote:
>> I don't know the intricacies of the Mustang hardware but external
>> aborts have been a symptom of missing clocks on other hardware.
>
> you are right, it's a missing clock.
On Fri, 21 Jul 2017 11:32:23 +0200
Michal Simek wrote:
> Hi Alan,
>
> this is the initial version before next step which is move
> uart_register_driver to probe function.
> I was able to get rid of static array with uart_port structures.
> It was wired with console which is also fixed.
> And the
Commit b6a1d093f96b ("PM / Domains: Extend generic power domain
debugfs") extends the existing generic power domain debugfs to provide
more information about each genpd, however it creates a debugfs
directory for each based on the name of the genpd. While it is a good
idea to populate the name fiel
The APM X-Gene PCIe root port does not support ACS at this point.
However, the hw provides isolation and source validation through
the SMMU. The stream ID generated by the PCIe ports contain both
the BDF as well as the port ID in its 3 most significant bits.
Turn on ACS but disable all the peer to
On Wed, 2017-07-26 at 10:48 +0200, Borislav Petkov wrote:
> From: Borislav Petkov
>
> Register with the GHES notifier chain so that there's no need to call
> into the module with ghes_edac_report_mem_error().
>
> Signed-off-by: Borislav Petkov
:
> +static int report_mem_error(struct notifier_b
On 07/28/2017 03:57 AM, Marc Gonzalez wrote:
> On 26/07/2017 21:24, Florian Fainelli wrote:
>
>> Marc reported that he was not getting the PHY library adjust_link()
>> callback function to run when calling phy_stop() + phy_disconnect()
>> which does not indeed happen because we don't make sure we
time_t is not y2038 safe. Replace all uses of
time_t by y2038 safe time64_t.
Similarly, replace the calls to get_seconds() with
y2038 safe ktime_get_real_seconds().
Note that this preserves fast access on 64 bit systems,
but 32 bit systems need sequence counters.
The syscall interfaces themselves
struct timespec is not y2038 safe on 32 bit machines.
Replace timespec with y2038 safe struct timespec64.
Note that the patch only changes the internals without
modifying the syscall interface. This will be part
of a separate series.
Signed-off-by: Deepa Dinamani
---
ipc/sem.c | 12 ++--
struct timespec is not y2038 safe on 32 bit machines.
Replace timespec with y2038 safe struct timespec64.
Note that the patch only changes the internals without
modifying the syscall interfaces. This will be part
of a separate series.
Signed-off-by: Deepa Dinamani
---
fs/utimes.c | 23
Resending to fix mail subject header.
The series aims to transition internal workings of ipc subsystem
to use y2038-safe types and apis.
The series is based on Al Viro's #work.ipc branch.
Deepa Dinamani (6):
ipc: Make sys_semtimedop() y2038 safe
ipc: mqueue: Replace timespec with timespec64
time_t is not y2038 safe. Replace all uses of
time_t by y2038 safe time64_t.
Similarly, replace the calls to get_seconds() with
y2038 safe ktime_get_real_seconds().
Note that this preserves fast access on 64 bit systems,
but 32 bit systems need sequence counters.
The syscall interfaces themselves
Quoting Eric Anholt (2017-07-25 19:27:25)
> Chris Wilson writes:
>
> > Quoting Eric Anholt (2017-06-22 21:50:54)
> >> This has proven immensely useful for debugging memory leaks and
> >> overallocation (which is a rather serious concern on the platform,
> >> given that we typically run at about 2
On 07/28/2017 01:33 PM, Oliver Hartkopp wrote:
> Hi Kurt,
>
> On 07/28/2017 03:02 PM, Kurt Van Dijck wrote:
>
The word 'max-arbitration-bitrate' makes the difference very clear.
>>>
>>> I think you are mixing up ISO layer 1 and ISO layer 2.
>>
>> In order to provide higher data throughput
struct timespec is not y2038 safe. Replace
all uses of timespec by y2038 safe struct timespec64.
Even though timespec is used here to represent timeouts,
replace these with timespec64 so that it facilitates
in verification by creating a y2038 safe kernel image
that is free of timespec.
The syscal
There are several error handling paths in aspeed_vuart_probe(),
where sysfs group is left unremoved. The patch fixes them.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/tty/serial/8250/8250_aspeed_vuart.c | 7 +--
1 file changed
301 - 400 of 742 matches
Mail list logo
