[PATCH 06/28] staging/lustre/osc: Fix reverted condition in osc_lock_weight

When importing clio simplification patch, the check for object got reversed by mistake when converting from if (obj == NULL) it somehow became if (obj) which is obviously wrong, and so when it does hit, a crash was happening as result. Fix the condition and all if fine now. Signed-off-by: Oleg

[PATCH 11/28] staging/lustre/ptlrpc: lost bulk leads to a hang

From: Vitaly Fertman The reverse order of request_out_callback() and reply_in_callback() puts the RPC into UNREGISTERING state, which is waiting for RPC & bulk md unlink, whereas only RPC md unlink has been called so far. If bulk is lost, even expired_set does not

[PATCH 16/28] staging/lustre: Inline Lustre intent disposition functions

They are just one-liners, so no point in having them exported and called through a different module. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/include/lustre_intent.h | 15 +++ drivers/staging/lustre/lustre/include/lustre_mdc.h| 3 ---

[PATCH 05/28] staging/lustre/osc: osc_lock_weight endless loop fix

From: Jinshan Xiong With huge number of pages to scan by osc_lock_weight() it is likely CLP_GANG_RESCHED is returned from osc_page_gang_lookup() and the scan will be repeated again from the start. To be sure that the scan is progressing across those restarts, next scan

[PATCH 06/28] staging/lustre/osc: Fix reverted condition in osc_lock_weight

When importing clio simplification patch, the check for object got reversed by mistake when converting from if (obj == NULL) it somehow became if (obj) which is obviously wrong, and so when it does hit, a crash was happening as result. Fix the condition and all if fine now. Signed-off-by: Oleg

[PATCH 11/28] staging/lustre/ptlrpc: lost bulk leads to a hang

From: Vitaly Fertman The reverse order of request_out_callback() and reply_in_callback() puts the RPC into UNREGISTERING state, which is waiting for RPC & bulk md unlink, whereas only RPC md unlink has been called so far. If bulk is lost, even expired_set does not check for UNREGISTERING state.

[PATCH 16/28] staging/lustre: Inline Lustre intent disposition functions

They are just one-liners, so no point in having them exported and called through a different module. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/include/lustre_intent.h | 15 +++ drivers/staging/lustre/lustre/include/lustre_mdc.h| 3 ---

[PATCH 05/28] staging/lustre/osc: osc_lock_weight endless loop fix

From: Jinshan Xiong With huge number of pages to scan by osc_lock_weight() it is likely CLP_GANG_RESCHED is returned from osc_page_gang_lookup() and the scan will be repeated again from the start. To be sure that the scan is progressing across those restarts, next scan should be started from the

[PATCH 12/28] staging/lustre/llite: take trunc_sem only at vvp layer

From: Patrick Farrell The lli_trunc_sem is taken in 'read' mode in both ll_page_mkwrite and vvp_io_fault_start. This can lead to a deadlock with another thread which asks for the semaphore in write mode between thse two read calls. Since all users of lli_trunc_sem are in the vvp

[PATCH 08/28] staging/lustre/ptlrpc: missing wakeup for ptlrpc_check_set

From: Liang Zhen This patch changes a few things: - There is no guarantee that request_out_callback will happen before reply_in_callback, if a request got reply and unlinked reply buffer before request_out_callback is called, then the thread waiting on

[PATCH 07/28] staging/lustre/ptlrpc: reorganize ptlrpc_request

From: Liang Zhen ptlrpc_request has some structure members are only for client side, and some others are only for server side, this patch moved these members to different structure then putting into an union. By doing this, size of ptlrpc_request is decreased about 300

[PATCH 13/28] staging/lustre: LDLM_DEBUG() shouldn't be passed \n

From: Alex Zhuravlev as it adds own \n, so any extra \n break log format. Signed-off-by: Alex Zhuravlev Reviewed-on: http://review.whamcloud.com/17494 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7521 Reviewed-by: James Simmons

[PATCH 12/28] staging/lustre/llite: take trunc_sem only at vvp layer

From: Patrick Farrell The lli_trunc_sem is taken in 'read' mode in both ll_page_mkwrite and vvp_io_fault_start. This can lead to a deadlock with another thread which asks for the semaphore in write mode between thse two read calls. Since all users of lli_trunc_sem are in the vvp layer, we can

[PATCH 08/28] staging/lustre/ptlrpc: missing wakeup for ptlrpc_check_set

From: Liang Zhen This patch changes a few things: - There is no guarantee that request_out_callback will happen before reply_in_callback, if a request got reply and unlinked reply buffer before request_out_callback is called, then the thread waiting on ptlrpc_request_set will miss wakeup

[PATCH 07/28] staging/lustre/ptlrpc: reorganize ptlrpc_request

From: Liang Zhen ptlrpc_request has some structure members are only for client side, and some others are only for server side, this patch moved these members to different structure then putting into an union. By doing this, size of ptlrpc_request is decreased about 300 bytes, besides saving

[PATCH 13/28] staging/lustre: LDLM_DEBUG() shouldn't be passed \n

From: Alex Zhuravlev as it adds own \n, so any extra \n break log format. Signed-off-by: Alex Zhuravlev Reviewed-on: http://review.whamcloud.com/17494 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7521 Reviewed-by: James Simmons Reviewed-by: John L. Hammond Reviewed-by: Andreas Dilger

[PATCH 10/28] staging/lustre/ptlrpc: Remove __ptlrpc_request_bufs_pack

From: Ben Evans Combine __ptlrpc_request_bufs_pack into ptlrpc_request_bufs_pack because it was an unnecessary wrapper otherwise. Signed-off-by: Ben Evans Reviewed-on: http://review.whamcloud.com/16765 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7269

[PATCH 10/28] staging/lustre/ptlrpc: Remove __ptlrpc_request_bufs_pack

From: Ben Evans Combine __ptlrpc_request_bufs_pack into ptlrpc_request_bufs_pack because it was an unnecessary wrapper otherwise. Signed-off-by: Ben Evans Reviewed-on: http://review.whamcloud.com/16765 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7269 Reviewed-by: Frank Zago

Re: [PATCH -next] drm/hisilicon: Fix return value check in ade_dts_parse()

Hi, On 18 June 2016 at 02:29, wrote: > From: Wei Yongjun > > In case of error, the function devm_clk_get() returns ERR_PTR() > and never returns NULL. The NULL test in the return value check > should be replaced with IS_ERR(). > > Signed-off-by:

Re: [PATCH -next] drm/hisilicon: Fix return value check in ade_dts_parse()

Hi, On 18 June 2016 at 02:29, wrote: > From: Wei Yongjun > > In case of error, the function devm_clk_get() returns ERR_PTR() > and never returns NULL. The NULL test in the return value check > should be replaced with IS_ERR(). > > Signed-off-by: Wei Yongjun Applied to drm-hisilicon-next.

linux-next: build warnings after merge of the pci tree

Hi Bjorn, After merging the pci tree, today's linux-next build (arm multi_v7_defconfig) produced these warnings: drivers/pci/host/pci-host-common.c: In function 'gen_pci_init': drivers/pci/host/pci-host-common.c:88:10: warning: return makes pointer from integer without a cast [-Wint-conversion]

linux-next: build warnings after merge of the pci tree

Hi Bjorn, After merging the pci tree, today's linux-next build (arm multi_v7_defconfig) produced these warnings: drivers/pci/host/pci-host-common.c: In function 'gen_pci_init': drivers/pci/host/pci-host-common.c:88:10: warning: return makes pointer from integer without a cast [-Wint-conversion]

Re: [PATCH v2 3/3] KVM: VMX: enable guest access to LMCE related MSRs

On 06/17/16 14:15, Eduardo Habkost wrote: > On Fri, Jun 17, 2016 at 09:11:16AM +0800, Haozhong Zhang wrote: > > On 06/16/16 11:55, Eduardo Habkost wrote: > > > On Thu, Jun 16, 2016 at 12:04:50PM +0200, Paolo Bonzini wrote: > > > > On 16/06/2016 08:05, Haozhong Zhang wrote: > > > > > From: Ashok

Re: [PATCH 2/4] thermal: rcar_gen3_thermal: Add R-Car Gen3 thermal driver support

Hi Khiem-san Thank you for your patch > +int _linear_temp_converter(struct equation_coefs coef, > + int temp_code) > +{ > + int temp, temp1, temp2; > + > + temp1 = MCELSIUS((CODETSD(temp_code) - coef.b1)) / coef.a1; > + temp2 =

Re: [PATCH v2 3/3] KVM: VMX: enable guest access to LMCE related MSRs

On 06/17/16 14:15, Eduardo Habkost wrote: > On Fri, Jun 17, 2016 at 09:11:16AM +0800, Haozhong Zhang wrote: > > On 06/16/16 11:55, Eduardo Habkost wrote: > > > On Thu, Jun 16, 2016 at 12:04:50PM +0200, Paolo Bonzini wrote: > > > > On 16/06/2016 08:05, Haozhong Zhang wrote: > > > > > From: Ashok

Re: [PATCH 2/4] thermal: rcar_gen3_thermal: Add R-Car Gen3 thermal driver support

Hi Khiem-san Thank you for your patch > +int _linear_temp_converter(struct equation_coefs coef, > + int temp_code) > +{ > + int temp, temp1, temp2; > + > + temp1 = MCELSIUS((CODETSD(temp_code) - coef.b1)) / coef.a1; > + temp2 =

Re: [PATCH] ARM: remove unused CONFIG_ARCH_HAS_BARRIERS

Hi. I have not had any comment on this patch, but it looks correct to me. I will put it into Russell's patch tracker if nobody is against it. 2016-06-13 21:25 GMT+09:00 Masahiro Yamada : > Since commit 2b749cb3a515 ("ARM: realview: remove private barrier >

Re: [PATCH] ARM: remove unused CONFIG_ARCH_HAS_BARRIERS

Hi. I have not had any comment on this patch, but it looks correct to me. I will put it into Russell's patch tracker if nobody is against it. 2016-06-13 21:25 GMT+09:00 Masahiro Yamada : > Since commit 2b749cb3a515 ("ARM: realview: remove private barrier > implementation"), this config is not

[PATCH v2 15/24] fs: ocfs2: Use time64_t to represent orphan scan times

struct timespec is not y2038 safe. Use time64_t which is y2038 safe to represent orphan scan times. time64_t is sufficient here as only the seconds delta times are relevant. Also use appropriate time functions that return time in time64_t format. Time functions now return monotonic time instead

[PATCH v2 14/24] drivers: staging: lustre: Replace CURRENT_TIME with current_time()

CURRENT_TIME macro is not appropriate for filesystems as it doesn't use the right granularity for filesystem timestamps. Use current_time() instead. This is also in preparation for the patch that transitions vfs timestamps to use 64 bit time and hence make them y2038 safe. As part of the effort

[PATCH v2 15/24] fs: ocfs2: Use time64_t to represent orphan scan times

struct timespec is not y2038 safe. Use time64_t which is y2038 safe to represent orphan scan times. time64_t is sufficient here as only the seconds delta times are relevant. Also use appropriate time functions that return time in time64_t format. Time functions now return monotonic time instead

[PATCH v2 14/24] drivers: staging: lustre: Replace CURRENT_TIME with current_time()

CURRENT_TIME macro is not appropriate for filesystems as it doesn't use the right granularity for filesystem timestamps. Use current_time() instead. This is also in preparation for the patch that transitions vfs timestamps to use 64 bit time and hence make them y2038 safe. As part of the effort

[PATCH v2 12/24] fs: cifs: Replace CURRENT_TIME by get_seconds

This is in preparation for the change that transitions filesystem timestamps to use 64 bit time and hence make them y2038 safe. CURRENT_TIME macro will be deleted before merging the aforementioned patch. Filesystems will use current_time() instead of CURRENT_TIME. Use ktime_get_real_seconds()

[PATCH v2 12/24] fs: cifs: Replace CURRENT_TIME by get_seconds

This is in preparation for the change that transitions filesystem timestamps to use 64 bit time and hence make them y2038 safe. CURRENT_TIME macro will be deleted before merging the aforementioned patch. Filesystems will use current_time() instead of CURRENT_TIME. Use ktime_get_real_seconds()

Re: [PATCH v6 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Guenter, On 2016/6/17 21:20, Guenter Roeck wrote: Hi Frank, On 06/16/2016 11:43 PM, Frank Wang wrote: Hi Guenter, On 2016/6/17 12:59, Guenter Roeck wrote: On 06/16/2016 07:09 PM, Frank Wang wrote: The newer SoCs (rk3366, rk3399) take a different usb-phy IP block than rk3288 and before,

Re: [PATCH v6 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Guenter, On 2016/6/17 21:20, Guenter Roeck wrote: Hi Frank, On 06/16/2016 11:43 PM, Frank Wang wrote: Hi Guenter, On 2016/6/17 12:59, Guenter Roeck wrote: On 06/16/2016 07:09 PM, Frank Wang wrote: The newer SoCs (rk3366, rk3399) take a different usb-phy IP block than rk3288 and before,

[PATCH v2 21/24] libceph: Replace CURRENT_TIME with ktime_get_real_ts

CURRENT_TIME is not y2038 safe. The macro will be deleted and all the references to it will be replaced by ktime_get_* apis. struct timespec is also not y2038 safe. Retain timespec for timestamp representation here as ceph uses it internally everywhere. These references will be changed to use

[PATCH v2 21/24] libceph: Replace CURRENT_TIME with ktime_get_real_ts

CURRENT_TIME is not y2038 safe. The macro will be deleted and all the references to it will be replaced by ktime_get_* apis. struct timespec is also not y2038 safe. Retain timespec for timestamp representation here as ceph uses it internally everywhere. These references will be changed to use

Re: [PATCH] checkpatch: remove obsolete CONFIG_EXPERIMENTAL checks

On Sun, 2016-06-19 at 23:29 +0300, Ruslan Bilovol wrote: > Config EXPERIMENTAL has been removed from kernel in 2013 > (see 3d374d0: "final removal of CONFIG_EXPERIMENTAL"), > there is no any reason to do these checks now. Not quite removed: $ git grep CONFIG_EXPERIMENTAL -- "*configs*" | wc -l

Re: [PATCH] checkpatch: remove obsolete CONFIG_EXPERIMENTAL checks

On Sun, 2016-06-19 at 23:29 +0300, Ruslan Bilovol wrote: > Config EXPERIMENTAL has been removed from kernel in 2013 > (see 3d374d0: "final removal of CONFIG_EXPERIMENTAL"), > there is no any reason to do these checks now. Not quite removed: $ git grep CONFIG_EXPERIMENTAL -- "*configs*" | wc -l

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: net/rds/tcp_listen.c between commit: 3bb549ae4c51 ("RDS: TCP: rds_tcp_accept_one() should transition socket from RESETTING to UP") from the net tree and commit: 0cb43965d42a ("RDS: split out connection specific

[PATCH v2 19/24] fnic: Use time64_t to represent trace timestamps

trace timestamps use struct timespec and CURRENT_TIME which are not y2038 safe. These timestamps are only part of the trace log on the machine and are not shared with the fnic. Replace then with y2038 safe struct timespec64 and ktime_get_real_ts64(), respectively. Note that change to add

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: net/rds/tcp_listen.c between commit: 3bb549ae4c51 ("RDS: TCP: rds_tcp_accept_one() should transition socket from RESETTING to UP") from the net tree and commit: 0cb43965d42a ("RDS: split out connection specific

[PATCH v2 19/24] fnic: Use time64_t to represent trace timestamps

trace timestamps use struct timespec and CURRENT_TIME which are not y2038 safe. These timestamps are only part of the trace log on the machine and are not shared with the fnic. Replace then with y2038 safe struct timespec64 and ktime_get_real_ts64(), respectively. Note that change to add

Re: [PATCH 5/7] random: replace non-blocking pool with a Chacha20-based CRNG

On Sun, Jun 19, 2016 at 07:18:28PM -0400, Theodore Ts'o wrote: > > C) Simply compiling in the Crypto layer and the ChaCha20 generic > handling (all of which is doing extra work which we would then be > undoing in the random layer --- and I haven't included the extra code > in the random driver

Re: [PATCH 5/7] random: replace non-blocking pool with a Chacha20-based CRNG

On Sun, Jun 19, 2016 at 07:18:28PM -0400, Theodore Ts'o wrote: > > C) Simply compiling in the Crypto layer and the ChaCha20 generic > handling (all of which is doing extra work which we would then be > undoing in the random layer --- and I haven't included the extra code > in the random driver

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: net/rds/tcp_connect.c between commit: 5c3da57d70f1 ("net: rds: fix coding style issues") from the net tree and commit: 0cb43965d42a ("RDS: split out connection specific state from rds_connection to

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: net/rds/tcp_connect.c between commit: 5c3da57d70f1 ("net: rds: fix coding style issues") from the net tree and commit: 0cb43965d42a ("RDS: split out connection specific state from rds_connection to

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/qlogic/qed/qed_hsi.h between commit: b639f197210d ("qed: Add missing port-mode") from the net tree and commit: 351a4dedb34c ("qed: Utilize FW 8.10.3.0") from the net-next tree. I fixed it up

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/qlogic/qed/qed_hsi.h between commit: b639f197210d ("qed: Add missing port-mode") from the net tree and commit: 351a4dedb34c ("qed: Utilize FW 8.10.3.0") from the net-next tree. I fixed it up

[PATCH v2 13/24] fs: f2fs: Use ktime_get_real_seconds for sit_info times

CURRENT_TIME_SEC is not y2038 safe. Replace use of CURRENT_TIME_SEC with ktime_get_real_seconds in segment timestamps used by GC algorithm including the segment mtime timestamps. Signed-off-by: Deepa Dinamani Cc: Jaegeuk Kim Cc: Changman Lee

[PATCH v2 13/24] fs: f2fs: Use ktime_get_real_seconds for sit_info times

CURRENT_TIME_SEC is not y2038 safe. Replace use of CURRENT_TIME_SEC with ktime_get_real_seconds in segment timestamps used by GC algorithm including the segment mtime timestamps. Signed-off-by: Deepa Dinamani Cc: Jaegeuk Kim Cc: Changman Lee Cc: linux-f2fs-de...@lists.sourceforge.net ---

Re: [PATCH 3/3] ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to it

Hi Steve, On Sun, May 22, 2016 at 04:28:49PM -0400, Steven Rostedt wrote: > From: Steven Rostedt > > Matt Fleming reported seeing crashes when enabling and disabling > function profiling which uses function graph tracer. Later Namhyung Kim > hit a similar issue and he found

Re: [PATCH 3/3] ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to it

Hi Steve, On Sun, May 22, 2016 at 04:28:49PM -0400, Steven Rostedt wrote: > From: Steven Rostedt > > Matt Fleming reported seeing crashes when enabling and disabling > function profiling which uses function graph tracer. Later Namhyung Kim > hit a similar issue and he found that the issue was

Re: [RESEND PATCH v2 2/2] power/idle: enhance the precision of sleep_length

On 17 June 2016 at 19:50, Thomas Gleixner wrote: > On Fri, 17 Jun 2016, Zhaoyang Huang wrote: >> On 17 June 2016 at 17:27, Thomas Gleixner wrote: >> > On Fri, 17 Jun 2016, Zhaoyang Huang wrote: >> >> There should be a gap between tick_nohz_idle_enter and

Re: [RESEND PATCH v2 2/2] power/idle: enhance the precision of sleep_length

On 17 June 2016 at 19:50, Thomas Gleixner wrote: > On Fri, 17 Jun 2016, Zhaoyang Huang wrote: >> On 17 June 2016 at 17:27, Thomas Gleixner wrote: >> > On Fri, 17 Jun 2016, Zhaoyang Huang wrote: >> >> There should be a gap between tick_nohz_idle_enter and >> >> tick_nohz_get_sleep_length when

[PATCH] PM / hibernate: Recycle safe pages after image restoration

From: Rafael J. Wysocki The hibernation image restoration code in snapshot.c allocates more safe pages (ie. pages that were not used by the image kernel before hibernation and therefore are suitable for storing temporary stuff that must not collide with the image

[PATCH] PM / hibernate: Recycle safe pages after image restoration

From: Rafael J. Wysocki The hibernation image restoration code in snapshot.c allocates more safe pages (ie. pages that were not used by the image kernel before hibernation and therefore are suitable for storing temporary stuff that must not collide with the image kernel's memory contents). Those

Re: [PATCH] MADVISE_FREE, THP: Fix madvise_free_huge_pmd return value after splitting

On Fri, Jun 17, 2016 at 12:45:43PM -0700, Huang, Ying wrote: > Minchan Kim writes: > > > Hi, > > > > On Thu, Jun 16, 2016 at 08:03:54PM -0700, Huang, Ying wrote: > >> From: Huang Ying > >> > >> madvise_free_huge_pmd should return 0 if the fallback PTE

Re: [PATCH] MADVISE_FREE, THP: Fix madvise_free_huge_pmd return value after splitting

On Fri, Jun 17, 2016 at 12:45:43PM -0700, Huang, Ying wrote: > Minchan Kim writes: > > > Hi, > > > > On Thu, Jun 16, 2016 at 08:03:54PM -0700, Huang, Ying wrote: > >> From: Huang Ying > >> > >> madvise_free_huge_pmd should return 0 if the fallback PTE operations are > >> required. In

Re: [PATCH v3 2/2] phy: add a driver for the Rockchip SoC internal PCIe PHY

Hi Kishon, On 2016/6/17 21:08, Kishon Vijay Abraham I wrote: Hi, On Thursday 16 June 2016 06:52 AM, Shawn Lin wrote: This patch to add a generic PHY driver for rockchip PCIe PHY. Access the PHY via registers provided by GRF (general register files) module. Signed-off-by: Shawn Lin

Re: kernel-4.7 bug in Intel sound and/or ACPI

You should CC the linux-pci too (done now) On Monday, June 20, 2016 02:35:30 AM Wim Osterholt wrote: > L.S. > up to vanilla kernel-4.6.2 sound was working fine. > Switching to kernel-4.7.0-rc3 made sound disappear. No /dev/mixer etc. > There appears to be a bug in the Intel sound driver and/or

Re: [PATCH v3 2/2] phy: add a driver for the Rockchip SoC internal PCIe PHY

Hi Kishon, On 2016/6/17 21:08, Kishon Vijay Abraham I wrote: Hi, On Thursday 16 June 2016 06:52 AM, Shawn Lin wrote: This patch to add a generic PHY driver for rockchip PCIe PHY. Access the PHY via registers provided by GRF (general register files) module. Signed-off-by: Shawn Lin ---

Re: kernel-4.7 bug in Intel sound and/or ACPI

You should CC the linux-pci too (done now) On Monday, June 20, 2016 02:35:30 AM Wim Osterholt wrote: > L.S. > up to vanilla kernel-4.6.2 sound was working fine. > Switching to kernel-4.7.0-rc3 made sound disappear. No /dev/mixer etc. > There appears to be a bug in the Intel sound driver and/or

Re: [PATCH v2 2/2] pci: host: new driver for Axis ARTPEC-6 PCIe controller

On 06/13/2016 03:33 PM, Bjorn Helgaas wrote: > On Mon, Jun 13, 2016 at 03:12:13PM +0200, Niklas Cassel wrote: >> On 06/10/2016 12:41 AM, Bjorn Helgaas wrote: >>> On Mon, May 09, 2016 at 01:49:03PM +0200, Niklas Cassel wrote: From: Niklas Cassel The Axis

Re: [PATCH v2 2/2] pci: host: new driver for Axis ARTPEC-6 PCIe controller

On 06/13/2016 03:33 PM, Bjorn Helgaas wrote: > On Mon, Jun 13, 2016 at 03:12:13PM +0200, Niklas Cassel wrote: >> On 06/10/2016 12:41 AM, Bjorn Helgaas wrote: >>> On Mon, May 09, 2016 at 01:49:03PM +0200, Niklas Cassel wrote: From: Niklas Cassel The Axis ARTPEC-6 SoC integrates a

Re: [RFC/PATCH] perf: Add sizeof operator support

On Fri, Jun 17, 2016 at 03:08:27PM -0400, Steven Rostedt wrote: > On Fri, 17 Jun 2016 13:57:44 -0500 > Jeremy Linton wrote: > > > > That is the simple case, initially I was going to just hand code some of > > the sizeofs in the kernel, but then I started noticing more

Re: [RFC/PATCH] perf: Add sizeof operator support

On Fri, Jun 17, 2016 at 03:08:27PM -0400, Steven Rostedt wrote: > On Fri, 17 Jun 2016 13:57:44 -0500 > Jeremy Linton wrote: > > > > That is the simple case, initially I was going to just hand code some of > > the sizeofs in the kernel, but then I started noticing more complex > > cases, and

[PATCH v2 18/24] fs: nfs: Make nfs boot time y2038 safe

boot_time is represented as a struct timespec. struct timespec and CURRENT_TIME are not y2038 safe. Overall, the plan is to use timespec64 and ktime_t for all internal kernel representation of timestamps. CURRENT_TIME will also be removed. boot_time is used to construct the nfs client boot

[PATCH v2 18/24] fs: nfs: Make nfs boot time y2038 safe

boot_time is represented as a struct timespec. struct timespec and CURRENT_TIME are not y2038 safe. Overall, the plan is to use timespec64 and ktime_t for all internal kernel representation of timestamps. CURRENT_TIME will also be removed. boot_time is used to construct the nfs client boot

[PATCH v2 16/24] fs: ocfs2: Replace CURRENT_TIME with ktime_get_real_seconds()

CURRENT_TIME is not y2038 safe. Use y2038 safe ktime_get_real_seconds() here for timestamps. struct heartbeat_block's hb_seq and deletetion time are already 64 bits wide and accommodate times beyond y2038. Signed-off-by: Deepa Dinamani Cc: Mark Fasheh

[PATCH v2 16/24] fs: ocfs2: Replace CURRENT_TIME with ktime_get_real_seconds()

CURRENT_TIME is not y2038 safe. Use y2038 safe ktime_get_real_seconds() here for timestamps. struct heartbeat_block's hb_seq and deletetion time are already 64 bits wide and accommodate times beyond y2038. Signed-off-by: Deepa Dinamani Cc: Mark Fasheh Cc: Joel Becker Cc:

[PATCH v2 22/24] fs: ceph: Replace current_fs_time for request stamp

The current_fs_time() api is being changed to use vfs struct inode* as an argument instead of struct super_block*. Set the new mds client request r_stamp field using ktime_get_real_ts() instead of using current_fs_time(). Also, since r_stamp is used as mtime on the server, use timespec_trunc()

[PATCH v2 22/24] fs: ceph: Replace current_fs_time for request stamp

The current_fs_time() api is being changed to use vfs struct inode* as an argument instead of struct super_block*. Set the new mds client request r_stamp field using ktime_get_real_ts() instead of using current_fs_time(). Also, since r_stamp is used as mtime on the server, use timespec_trunc()

[PATCH v2 17/24] audit: Use timespec64 to represent audit timestamps

struct timespec is not y2038 safe. Audit timestamps are recorded in string format into an audit buffer for a given context. These mark the entry timestamps for the syscalls. Use y2038 safe struct timespec64 to represent the times. The log strings can handle this transition as strings can hold upto

[PATCH v2 17/24] audit: Use timespec64 to represent audit timestamps

struct timespec is not y2038 safe. Audit timestamps are recorded in string format into an audit buffer for a given context. These mark the entry timestamps for the syscalls. Use y2038 safe struct timespec64 to represent the times. The log strings can handle this transition as strings can hold upto

kernel-4.7 bug in Intel sound and/or ACPI

L.S. up to vanilla kernel-4.6.2 sound was working fine. Switching to kernel-4.7.0-rc3 made sound disappear. No /dev/mixer etc. There appears to be a bug in the Intel sound driver and/or ACPI driver. Dmesg shows interesting lines like: [ 11.498592] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 7

kernel-4.7 bug in Intel sound and/or ACPI

L.S. up to vanilla kernel-4.6.2 sound was working fine. Switching to kernel-4.7.0-rc3 made sound disappear. No /dev/mixer etc. There appears to be a bug in the Intel sound driver and/or ACPI driver. Dmesg shows interesting lines like: [ 11.498592] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 7

Re: [v2 PATCH 2/4] phy: Add USB Type-C PHY driver for rk3399

Hi Kishon On 06/17/2016 08:54 PM, Kishon Vijay Abraham I wrote: On Monday 13 June 2016 03:09 PM, Chris Zhong wrote: Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components: USB3

Re: [v2 PATCH 2/4] phy: Add USB Type-C PHY driver for rk3399

Hi Kishon On 06/17/2016 08:54 PM, Kishon Vijay Abraham I wrote: On Monday 13 June 2016 03:09 PM, Chris Zhong wrote: Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components: USB3

[PATCH v2 24/24] time: Delete current_fs_time() function

All uses of the current_fs_time() function have been replaced by other time interfaces. And, its use cases can be fulfilled by current_time() or ktime_get_* variants. Signed-off-by: Deepa Dinamani Cc: John Stultz Cc: Thomas Gleixner

[PATCH v2 04/24] fs: Replace current_fs_time() with current_time()

current_fs_time() uses struct super_block* as an argument. As per Linus's suggestion, this is changed to take struct inode* as a parameter instead. This is because the function is primarily meant for vfs inode timestamps. Also the function was renamed as per Arnd's suggestion. Change all calls to

[PATCH v2 02/24] fs: Replace CURRENT_TIME with current_time() for inode timestamps

CURRENT_TIME macro is not appropriate for filesystems as it doesn't use the right granularity for filesystem timestamps. Use current_time() instead. CURRENT_TIME is also not y2038 safe. This is also in preparation for the patch that transitions vfs timestamps to use 64 bit time and hence make

[PATCH v2 05/24] fs: jfs: Replace CURRENT_TIME_SEC by current_time()

jfs uses nanosecond granularity for filesystem timestamps. Only this assignemt is not using nanosecond granularity. Use current_time() to get the right granularity. Signed-off-by: Deepa Dinamani Cc: Dave Kleikamp Cc:

[PATCH v2 24/24] time: Delete current_fs_time() function

All uses of the current_fs_time() function have been replaced by other time interfaces. And, its use cases can be fulfilled by current_time() or ktime_get_* variants. Signed-off-by: Deepa Dinamani Cc: John Stultz Cc: Thomas Gleixner --- include/linux/fs.h | 1 - kernel/time/time.c | 14

[PATCH v2 04/24] fs: Replace current_fs_time() with current_time()

current_fs_time() uses struct super_block* as an argument. As per Linus's suggestion, this is changed to take struct inode* as a parameter instead. This is because the function is primarily meant for vfs inode timestamps. Also the function was renamed as per Arnd's suggestion. Change all calls to

[PATCH v2 02/24] fs: Replace CURRENT_TIME with current_time() for inode timestamps

CURRENT_TIME macro is not appropriate for filesystems as it doesn't use the right granularity for filesystem timestamps. Use current_time() instead. CURRENT_TIME is also not y2038 safe. This is also in preparation for the patch that transitions vfs timestamps to use 64 bit time and hence make

[PATCH v2 05/24] fs: jfs: Replace CURRENT_TIME_SEC by current_time()

jfs uses nanosecond granularity for filesystem timestamps. Only this assignemt is not using nanosecond granularity. Use current_time() to get the right granularity. Signed-off-by: Deepa Dinamani Cc: Dave Kleikamp Cc: jfs-discuss...@lists.sourceforge.net --- fs/jfs/ioctl.c | 2 +- 1 file

[PATCH v2 23/24] time: Delete CURRENT_TIME_SEC and CURRENT_TIME macro

All uses of these macros have been replaced by other time functions. These macros are also not y2038 safe. And, all its use cases can be fulfilled by y2038 safe ktime_get_* variants. Signed-off-by: Deepa Dinamani Cc: John Stultz Cc: Thomas

[PATCH v2 23/24] time: Delete CURRENT_TIME_SEC and CURRENT_TIME macro

All uses of these macros have been replaced by other time functions. These macros are also not y2038 safe. And, all its use cases can be fulfilled by y2038 safe ktime_get_* variants. Signed-off-by: Deepa Dinamani Cc: John Stultz Cc: Thomas Gleixner Acked-by: John Stultz ---

[PATCH v2 03/24] fs: Replace CURRENT_TIME_SEC with current_time() for inode timestamps

CURRENT_TIME_SEC is not y2038 safe. current_time() will be transitioned to use 64 bit time along with vfs in a separate patch. There is no plan to transistion CURRENT_TIME_SEC to use y2038 safe time interfaces. current_time() will also be extended to use superblock range checking parameters when

[PATCH v2 11/24] fs: cifs: Replace CURRENT_TIME with ktime_get_real_ts()

This is in preparation for the patch that transitions vfs timestamps to use 64 bit time and hence make them y2038 safe. CURRENT_TIME macro will be deleted before merging the aforementioned patch. Filesystem times will use current_fs_time() instead of CURRENT_TIME. Use ktime_get_real_ts() here as

[PATCH v2 07/24] fs: ubifs: Replace CURRENT_TIME_SEC with current_time

CURRENT_TIME_SEC is not y2038 safe. current_time() will be transitioned to use 64 bit time along with vfs in a separate patch. There is no plan to transition CURRENT_TIME_SEC to use y2038 safe time interfaces. current_time() returns timestamps according to the granularities set in the inode's

[PATCH v2 08/24] fs: btrfs: Use ktime_get_real_ts for root ctime

btrfs_root_item maintains the ctime for root updates. This is not part of vfs_inode. Since current_time() uses struct inode* as an argument as Linus suggested, this cannot be used to update root times unless, we modify the signature to use inode. Since btrfs uses nanosecond time granularity, it

[PATCH v2 11/24] fs: cifs: Replace CURRENT_TIME with ktime_get_real_ts()

This is in preparation for the patch that transitions vfs timestamps to use 64 bit time and hence make them y2038 safe. CURRENT_TIME macro will be deleted before merging the aforementioned patch. Filesystem times will use current_fs_time() instead of CURRENT_TIME. Use ktime_get_real_ts() here as

[PATCH v2 07/24] fs: ubifs: Replace CURRENT_TIME_SEC with current_time

CURRENT_TIME_SEC is not y2038 safe. current_time() will be transitioned to use 64 bit time along with vfs in a separate patch. There is no plan to transition CURRENT_TIME_SEC to use y2038 safe time interfaces. current_time() returns timestamps according to the granularities set in the inode's

[PATCH v2 08/24] fs: btrfs: Use ktime_get_real_ts for root ctime

btrfs_root_item maintains the ctime for root updates. This is not part of vfs_inode. Since current_time() uses struct inode* as an argument as Linus suggested, this cannot be used to update root times unless, we modify the signature to use inode. Since btrfs uses nanosecond time granularity, it

[PATCH v2 03/24] fs: Replace CURRENT_TIME_SEC with current_time() for inode timestamps

CURRENT_TIME_SEC is not y2038 safe. current_time() will be transitioned to use 64 bit time along with vfs in a separate patch. There is no plan to transistion CURRENT_TIME_SEC to use y2038 safe time interfaces. current_time() will also be extended to use superblock range checking parameters when

[PATCH v2 00/24] Delete CURRENT_TIME and CURRENT_TIME_SEC macros

The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC macros. The macros are not y2038 safe. There is no plan to transition them into being y2038 safe. ktime_get_* api's can be used in their place. And, these are y2038 safe. Thanks to Arnd Bergmann for all the guidance and

[PATCH v2 01/24] vfs: Add current_time() api

current_fs_time() is used for inode timestamps. Change the signature of the function to take inode pointer instead of superblock as per Linus's suggestion. Also, move the api under vfs as per the discussion on the thread: https://lkml.org/lkml/2016/6/9/36 . As per Arnd's suggestion on the

<    1   2   3   4   5   6   >