Re: [RFC][PATCH 0/9] VFS: Introduce mount context

On Wed, 2017-05-03 at 17:04 +0100, David Howells wrote: > Here are a set of patches to create a mount context prior to setting up a > new mount, populating it with the parsed options/binary data and then > effecting the mount. > > This allows namespaces and other information to be conveyed

Re: [RFC][PATCH 0/9] VFS: Introduce mount context

On Wed, 2017-05-03 at 17:04 +0100, David Howells wrote: > Here are a set of patches to create a mount context prior to setting up a > new mount, populating it with the parsed options/binary data and then > effecting the mount. > > This allows namespaces and other information to be conveyed

GFS2: Pull request (merge window)

Hi Linus, Please consider pulling the following changes for the GFS2 file system. Special note: This time we had an unusual dependency on a patch (f9fe1c12) which went through David Miller's net-next tree, so we had a merge commit on our GFS2 for-next branch. After you pulled that patch, I

GFS2: Pull request (merge window)

Hi Linus, Please consider pulling the following changes for the GFS2 file system. Special note: This time we had an unusual dependency on a patch (f9fe1c12) which went through David Miller's net-next tree, so we had a merge commit on our GFS2 for-next branch. After you pulled that patch, I

Re: [PATCH] MAINTAINERS: add a...@kernel.org as the list for arm64 defconfig changes

On Wed, May 03, 2017 at 11:31:25AM -0500, Timur Tabi wrote: > Any changes to arch/arm64/configs/defconfig must be sent to a...@kernel.org, > otherwise they will not get picked up. Add a MAINTAINERS entry to ensure > the get_maintainers includes it. a...@kernel.org is not a mailing list, it is an

Re: [PATCH] MAINTAINERS: add a...@kernel.org as the list for arm64 defconfig changes

On Wed, May 03, 2017 at 11:31:25AM -0500, Timur Tabi wrote: > Any changes to arch/arm64/configs/defconfig must be sent to a...@kernel.org, > otherwise they will not get picked up. Add a MAINTAINERS entry to ensure > the get_maintainers includes it. a...@kernel.org is not a mailing list, it is an

[PATCH] MAINTAINERS: add a...@kernel.org as the list for arm64 defconfig changes

Any changes to arch/arm64/configs/defconfig must be sent to a...@kernel.org, otherwise they will not get picked up. Add a MAINTAINERS entry to ensure the get_maintainers includes it. Signed-off-by: Timur Tabi --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+)

[PATCH] MAINTAINERS: add a...@kernel.org as the list for arm64 defconfig changes

Any changes to arch/arm64/configs/defconfig must be sent to a...@kernel.org, otherwise they will not get picked up. Add a MAINTAINERS entry to ensure the get_maintainers includes it. Signed-off-by: Timur Tabi --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git

Re: [RFC PATCH v2 3/3] hwmon: (adt7475) temperature smoothing

On Wed, May 03, 2017 at 12:40:09PM +1200, Chris Packham wrote: > When enabled temperature smoothing allows ramping the fan speed over a > configurable period of time instead of jumping to the new speed > instantaneously. > > Signed-off-by: Chris Packham > --- >

Re: [RFC PATCH v2 3/3] hwmon: (adt7475) temperature smoothing

On Wed, May 03, 2017 at 12:40:09PM +1200, Chris Packham wrote: > When enabled temperature smoothing allows ramping the fan speed over a > configurable period of time instead of jumping to the new speed > instantaneously. > > Signed-off-by: Chris Packham > --- > Changes in v2: > - use a single

Re: [PATCH 1/2] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

Archit Taneja writes: > Hi, > > On 04/27/2017 10:06 PM, Eric Anholt wrote: >> Many DRM drivers have common code to make a stub connector >> implementation that wraps a drm_panel. By wrapping the panel in a DRM >> bridge, all of the connector code (including calls during

Re: [PATCH 1/2] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

Archit Taneja writes: > Hi, > > On 04/27/2017 10:06 PM, Eric Anholt wrote: >> Many DRM drivers have common code to make a stub connector >> implementation that wraps a drm_panel. By wrapping the panel in a DRM >> bridge, all of the connector code (including calls during encoder >>

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On Wed, May 3, 2017 at 9:09 AM, Kani, Toshimitsu wrote: > On Wed, 2017-05-03 at 08:52 -0700, Dan Williams wrote: >> On Wed, May 3, 2017 at 8:31 AM, Toshi Kani >> wrote: >> > This is a RFC patch for seeking suggestions. It adds support of >> > badblocks

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On Wed, May 3, 2017 at 9:09 AM, Kani, Toshimitsu wrote: > On Wed, 2017-05-03 at 08:52 -0700, Dan Williams wrote: >> On Wed, May 3, 2017 at 8:31 AM, Toshi Kani >> wrote: >> > This is a RFC patch for seeking suggestions. It adds support of >> > badblocks check in Device DAX by using region-level

[PATCH] scsi: pmcraid: remove redundant check to see if request_size is less than zero

From: Colin Ian King The 2nd check to see if request_size is less than zero is redundant because the first check takes error exit path on this condition. So, since it is redundant, remove it. Detected by CoverityScan, CID#146149 ("Logically Dead Code") Signed-off-by:

[PATCH] scsi: pmcraid: remove redundant check to see if request_size is less than zero

From: Colin Ian King The 2nd check to see if request_size is less than zero is redundant because the first check takes error exit path on this condition. So, since it is redundant, remove it. Detected by CoverityScan, CID#146149 ("Logically Dead Code") Signed-off-by: Colin Ian King ---

Re: [PATCH] iommu/arm-smmu-v3: Poll for CMDQ drain completion more effectively

On Wed, May 3, 2017 at 9:29 PM, Will Deacon wrote: > On Wed, May 03, 2017 at 09:24:13PM +0530, Sunil Kovvuri wrote: >> On Wed, May 3, 2017 at 9:07 PM, Will Deacon wrote: >> > On Wed, May 03, 2017 at 06:49:09PM +0530, Sunil Kovvuri wrote: >> >> On Thu,

Re: [PATCH] iommu/arm-smmu-v3: Poll for CMDQ drain completion more effectively

On Wed, May 3, 2017 at 9:29 PM, Will Deacon wrote: > On Wed, May 03, 2017 at 09:24:13PM +0530, Sunil Kovvuri wrote: >> On Wed, May 3, 2017 at 9:07 PM, Will Deacon wrote: >> > On Wed, May 03, 2017 at 06:49:09PM +0530, Sunil Kovvuri wrote: >> >> On Thu, Apr 27, 2017 at 4:43 PM, wrote: >> >> >

Re: [PATCH] iommu/arm-smmu-v3: Poll for CMDQ drain completion more effectively

On Wed, May 3, 2017 at 9:10 PM, Will Deacon wrote: > On Wed, May 03, 2017 at 04:33:57PM +0100, Robin Murphy wrote: >> On 27/04/17 12:13, sunil.kovv...@gmail.com wrote: >> > From: Sunil Goutham >> > >> > Modified polling on CMDQ consumer similar to how

Re: [PATCH] iommu/arm-smmu-v3: Poll for CMDQ drain completion more effectively

On Wed, May 3, 2017 at 9:10 PM, Will Deacon wrote: > On Wed, May 03, 2017 at 04:33:57PM +0100, Robin Murphy wrote: >> On 27/04/17 12:13, sunil.kovv...@gmail.com wrote: >> > From: Sunil Goutham >> > >> > Modified polling on CMDQ consumer similar to how polling is done for TLB >> > SYNC >> >

[PATCH v2 3/3] tpm: move TPM 1.2 code of tpm_pcr_extend() to tpm1_pcr_extend()

In preparation of the modifications to tpm_pcr_extend(), which will allow callers to supply a digest for each PCR bank of a TPM 2.0, the TPM 1.2 specific code has been moved to tpm1_pcr_extend(). tpm1_pcr_extend() uses tpm_buf_init() to prepare the command buffer, which offers protection against

[PATCH v2 3/3] tpm: move TPM 1.2 code of tpm_pcr_extend() to tpm1_pcr_extend()

In preparation of the modifications to tpm_pcr_extend(), which will allow callers to supply a digest for each PCR bank of a TPM 2.0, the TPM 1.2 specific code has been moved to tpm1_pcr_extend(). tpm1_pcr_extend() uses tpm_buf_init() to prepare the command buffer, which offers protection against

[PATCH v2 1/3] tpm: move endianness conversion of TPM_TAG_RQU_COMMAND to tpm_input_header

In the long term, TPM 1.2 functions in the driver interface will be modified to use tpm_buf_init(). However, tag and ordinals cannot be passed directly to tpm_buf_init(), because this function performs CPU native to big-endian conversion of these arguments. Since TPM_TAG_RQU_COMMAND and TPM_ORD_

[PATCH v2 1/3] tpm: move endianness conversion of TPM_TAG_RQU_COMMAND to tpm_input_header

In the long term, TPM 1.2 functions in the driver interface will be modified to use tpm_buf_init(). However, tag and ordinals cannot be passed directly to tpm_buf_init(), because this function performs CPU native to big-endian conversion of these arguments. Since TPM_TAG_RQU_COMMAND and TPM_ORD_

[PATCH v2 2/3] tpm: move endianness conversion of ordinals to tpm_input_header

Move CPU native value to big-endian conversion of ordinals to the tpm_input_header declarations. With the previous and this patch it will now be possible to modify TPM 1.2 functions to use tpm_buf_init(), which expects CPU native value for the tag and ordinal arguments. Signed-off-by: Roberto

[PATCH v2 2/3] tpm: move endianness conversion of ordinals to tpm_input_header

Move CPU native value to big-endian conversion of ordinals to the tpm_input_header declarations. With the previous and this patch it will now be possible to modify TPM 1.2 functions to use tpm_buf_init(), which expects CPU native value for the tag and ordinal arguments. Signed-off-by: Roberto

[PATCH v2 0/3] tpm_pcr_extend() code split

This patch set moves TPM 1.2 specific code to a new function called tpm1_pcr_extend(). The purpose of splitting is to isolate TPM 2.0 code, so that it can be more easily modified to handle multiple digests. With TPM 2.0, a Platform Configuration Register (PCR) could have multiple values, stored

[PATCH v2 0/3] tpm_pcr_extend() code split

This patch set moves TPM 1.2 specific code to a new function called tpm1_pcr_extend(). The purpose of splitting is to isolate TPM 2.0 code, so that it can be more easily modified to handle multiple digests. With TPM 2.0, a Platform Configuration Register (PCR) could have multiple values, stored

Re: [PATCH] CIFS: fix oplock break deadlocks

merged into cifs-2.6.git for-next cc: stabled On Wed, May 3, 2017 at 11:04 AM, Steve French wrote: > Thoughts about whether cc: stable? > > On Wed, May 3, 2017 at 10:54 AM, Rabin Vincent wrote: >> From: Rabin Vincent >> >> When the

Re: [PATCH] CIFS: fix oplock break deadlocks

merged into cifs-2.6.git for-next cc: stabled On Wed, May 3, 2017 at 11:04 AM, Steve French wrote: > Thoughts about whether cc: stable? > > On Wed, May 3, 2017 at 10:54 AM, Rabin Vincent wrote: >> From: Rabin Vincent >> >> When the final cifsFileInfo_put() is called from cifsiod and an oplock

Re: [PATCH 1/2] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

Laurent Pinchart writes: > Hi Daniel, > > On Wednesday 03 May 2017 16:28:56 Daniel Vetter wrote: >> On Wed, May 03, 2017 at 12:36:06PM +0300, Laurent Pinchart wrote: >> > On Wednesday 03 May 2017 11:32:17 Daniel Vetter wrote: >> >> On Wed, May 03, 2017 at

Re: [PATCH 1/2] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

Laurent Pinchart writes: > Hi Daniel, > > On Wednesday 03 May 2017 16:28:56 Daniel Vetter wrote: >> On Wed, May 03, 2017 at 12:36:06PM +0300, Laurent Pinchart wrote: >> > On Wednesday 03 May 2017 11:32:17 Daniel Vetter wrote: >> >> On Wed, May 03, 2017 at 02:53:00PM +0530, Archit Taneja wrote:

[PATCH v3] KVM: remove #ifndef CONFIG_S390 around kvm_vcpu_wake_up

The #ifndef was protecting a missing halt_wakeup stat, but that is no longer necessary. The #ifndef around kvm_vcpu_kick is still necessary as s390 does not export smp_send_reschedule. Signed-off-by: Radim Krčmář --- v3: kept kvm_vcpu_kick() under the #ifndef and compile

[PATCH v3] KVM: remove #ifndef CONFIG_S390 around kvm_vcpu_wake_up

The #ifndef was protecting a missing halt_wakeup stat, but that is no longer necessary. The #ifndef around kvm_vcpu_kick is still necessary as s390 does not export smp_send_reschedule. Signed-off-by: Radim Krčmář --- v3: kept kvm_vcpu_kick() under the #ifndef and compile tested with kvm

Re: [PATCH v4] platform/x86: ideapad-laptop: Add sysfs interface for touchpad state

On Wed, May 03, 2017 at 05:42:02PM +0300, Andy Shevchenko wrote: > On Wed, May 3, 2017 at 5:36 PM, Ritesh Raj Sarraf wrote: > > Resending again, as Google servers are behaving weird lately. > > > > On Sun, 2017-04-30 at 15:54 +0300, Andy Shevchenko wrote: > >> > > the main issue

Re: [PATCH v4] platform/x86: ideapad-laptop: Add sysfs interface for touchpad state

On Wed, May 03, 2017 at 05:42:02PM +0300, Andy Shevchenko wrote: > On Wed, May 3, 2017 at 5:36 PM, Ritesh Raj Sarraf wrote: > > Resending again, as Google servers are behaving weird lately. > > > > On Sun, 2017-04-30 at 15:54 +0300, Andy Shevchenko wrote: > >> > > the main issue that driver

Re: [RFC PATCH v2 2/3] hwmon: (adt7475) fan stall prevention

On Wed, May 03, 2017 at 12:40:08PM +1200, Chris Packham wrote: > By default adt7475 will stop the fans (pwm duty cycle 0%) when the > temperature drops past Tmin - hysteresis. Some systems want to keep the > fans moving even when the temperature drops so add new sysfs attributes > that configure

Re: [RFC PATCH v2 2/3] hwmon: (adt7475) fan stall prevention

On Wed, May 03, 2017 at 12:40:08PM +1200, Chris Packham wrote: > By default adt7475 will stop the fans (pwm duty cycle 0%) when the > temperature drops past Tmin - hysteresis. Some systems want to keep the > fans moving even when the temperature drops so add new sysfs attributes > that configure

Re: [PATCH 3/9] bio-integrity: bio_integrity_advance must update integrity seed

Dmitry, > AFAIU: bip->bip_iter.bi_sector is always equals to bio->bi_iter.bi_sector > at least bip_set_seed() and bip_get_seed() relays on that. > Only bip->bip_vec must be advanced in intervals (this behavior not > changed by the patch this patch). Yep, I realized that a bit after sending but

Re: [PATCH 3/9] bio-integrity: bio_integrity_advance must update integrity seed

Dmitry, > AFAIU: bip->bip_iter.bi_sector is always equals to bio->bi_iter.bi_sector > at least bip_set_seed() and bip_get_seed() relays on that. > Only bip->bip_vec must be advanced in intervals (this behavior not > changed by the patch this patch). Yep, I realized that a bit after sending but

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On Wed, 2017-05-03 at 08:52 -0700, Dan Williams wrote: > On Wed, May 3, 2017 at 8:31 AM, Toshi Kani > wrote: > > This is a RFC patch for seeking suggestions.  It adds support of > > badblocks check in Device DAX by using region-level badblocks list. > > This patch is only

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On Wed, 2017-05-03 at 08:52 -0700, Dan Williams wrote: > On Wed, May 3, 2017 at 8:31 AM, Toshi Kani > wrote: > > This is a RFC patch for seeking suggestions.  It adds support of > > badblocks check in Device DAX by using region-level badblocks list. > > This patch is only briefly tested. > > > >

Re: [PATCHv2 0/4] Motorola Droid 4: Add WL1285C support

Hi, On Wed, May 03, 2017 at 05:02:13PM +0200, Marcel Holtmann wrote: > >> Motorola Droid 4 uses a WL1285C, as visible on iFixit [0]. This > >> fixes the DT file to use correct compatible for the wifi node > >> and adds the bluetooth node. > >> > >> [0]

Re: [PATCHv2 0/4] Motorola Droid 4: Add WL1285C support

Hi, On Wed, May 03, 2017 at 05:02:13PM +0200, Marcel Holtmann wrote: > >> Motorola Droid 4 uses a WL1285C, as visible on iFixit [0]. This > >> fixes the DT file to use correct compatible for the wifi node > >> and adds the bluetooth node. > >> > >> [0]

[PATCH 4/9] Implement fsopen() to prepare for a mount

Provide an fsopen() system call that starts the process of preparing to mount, using an fd as a context handle. fsopen() is given the name of the filesystem that will be used: int mfd = fsopen(const char *fsname, int reserved, int open_flags); where reserved

[PATCH 4/9] Implement fsopen() to prepare for a mount

Provide an fsopen() system call that starts the process of preparing to mount, using an fd as a context handle. fsopen() is given the name of the filesystem that will be used: int mfd = fsopen(const char *fsname, int reserved, int open_flags); where reserved

[PATCH 3/9] VFS: Introduce a mount context

Introduce a mount context concept. This is allocated at the beginning of the mount procedure and into it is placed: (1) Filesystem type. (2) Namespaces. (3) Device name. (4) Superblock flags (MS_*) and mount flags (MNT_*). (5) Security details. (6) Filesystem-specific data, as set by

[PATCH 3/9] VFS: Introduce a mount context

Introduce a mount context concept. This is allocated at the beginning of the mount procedure and into it is placed: (1) Filesystem type. (2) Namespaces. (3) Device name. (4) Superblock flags (MS_*) and mount flags (MNT_*). (5) Security details. (6) Filesystem-specific data, as set by

Re: [PATCH 3/9] bio-integrity: bio_integrity_advance must update integrity seed

"Martin K. Petersen" writes: > Dmitry Monakhov writes: > >> SCSI drivers do care about bip_seed so we must update it accordingly. > >> +bip->bip_iter.bi_sector += bytes_done >> 9; > > This needs to count protection intervals. Otherwise

Re: [PATCH 3/9] bio-integrity: bio_integrity_advance must update integrity seed

"Martin K. Petersen" writes: > Dmitry Monakhov writes: > >> SCSI drivers do care about bip_seed so we must update it accordingly. > >> +bip->bip_iter.bi_sector += bytes_done >> 9; > > This needs to count protection intervals. Otherwise things will break > for block sizes different from 512

[PATCH 7/9] procfs: Move proc_fill_super() to fs/proc/root.c

Move proc_fill_super() to fs/proc/root.c as that's where the other superblock stuff is. Signed-off-by: David Howells --- fs/proc/inode.c| 48 +--- fs/proc/internal.h |4 +--- fs/proc/root.c | 48

[PATCH 7/9] procfs: Move proc_fill_super() to fs/proc/root.c

Move proc_fill_super() to fs/proc/root.c as that's where the other superblock stuff is. Signed-off-by: David Howells --- fs/proc/inode.c| 48 +--- fs/proc/internal.h |4 +--- fs/proc/root.c | 48

[PATCH 8/9] proc: Support the mount context in procfs

--- fs/proc/inode.c|2 - fs/proc/internal.h |2 - fs/proc/root.c | 158 3 files changed, 100 insertions(+), 62 deletions(-) diff --git a/fs/proc/inode.c b/fs/proc/inode.c index 194fa2d13b7e..9ddaf60c6f93 100644 ---

[PATCH 8/9] proc: Support the mount context in procfs

--- fs/proc/inode.c|2 - fs/proc/internal.h |2 - fs/proc/root.c | 158 3 files changed, 100 insertions(+), 62 deletions(-) diff --git a/fs/proc/inode.c b/fs/proc/inode.c index 194fa2d13b7e..9ddaf60c6f93 100644 ---

Re: [PATCH v2 3/9] KVM: remove #ifndef CONFIG_S390 around kvm_vcpu_wake_up

2017-04-26 22:32+0200, Radim Krčmář: > The #ifndef was protecting a missing halt_wakeup stat, but that is no > longer necessary. It was also protecting smp_send_reschedule() in kvm_vcpu_kick() and I didn't include Christian's patch that exported it and also missed the warning. Going to send v3

Re: [PATCH v2 3/9] KVM: remove #ifndef CONFIG_S390 around kvm_vcpu_wake_up

2017-04-26 22:32+0200, Radim Krčmář: > The #ifndef was protecting a missing halt_wakeup stat, but that is no > longer necessary. It was also protecting smp_send_reschedule() in kvm_vcpu_kick() and I didn't include Christian's patch that exported it and also missed the warning. Going to send v3

[PATCH 9/9] NFS: Support the mount context and fsopen()

Support the fsopen() system call in NFS, parsing the options and filling in an nfs_parsed_mount_data struct attached to the mount_context struct. For example: mfd = fsopen("nfs4", -1, 0); E_write(mfd, "d warthog:/root"); E_write(mfd, "o fsc"); E_write(mfd, "o

[PATCH 9/9] NFS: Support the mount context and fsopen()

Support the fsopen() system call in NFS, parsing the options and filling in an nfs_parsed_mount_data struct attached to the mount_context struct. For example: mfd = fsopen("nfs4", -1, 0); E_write(mfd, "d warthog:/root"); E_write(mfd, "o fsc"); E_write(mfd, "o

[PATCH 6/9] Sample program for driving fsopen/fsmount

--- samples/fsmount/test-fsmount.c | 79 1 file changed, 79 insertions(+) create mode 100644 samples/fsmount/test-fsmount.c diff --git a/samples/fsmount/test-fsmount.c b/samples/fsmount/test-fsmount.c new file mode 100644 index

[PATCH 5/9] Implement fsmount() to effect a pre-configured mount

Provide a system call by which a filesystem opened with fsopen() and configured by a series of writes can be mounted: int ret = fsmount(int fsfd, int dfd, const char *path); where fsfd is the fd returned by fsopen(), dfd and path describe the mountpoint. dfd can be AT_FDCWD or an fd

[PATCH 6/9] Sample program for driving fsopen/fsmount

--- samples/fsmount/test-fsmount.c | 79 1 file changed, 79 insertions(+) create mode 100644 samples/fsmount/test-fsmount.c diff --git a/samples/fsmount/test-fsmount.c b/samples/fsmount/test-fsmount.c new file mode 100644 index

[PATCH 5/9] Implement fsmount() to effect a pre-configured mount

Provide a system call by which a filesystem opened with fsopen() and configured by a series of writes can be mounted: int ret = fsmount(int fsfd, int dfd, const char *path); where fsfd is the fd returned by fsopen(), dfd and path describe the mountpoint. dfd can be AT_FDCWD or an fd

[PATCH 1/9] Provide a function to create a NUL-terminated string from unterminated data

Provide a function, kstrcreate(), that will create a NUL-terminated string from an unterminated character array where the length is known in advance. This is better than kstrndup() in situations where we already know the string length as the strnlen() in kstrndup() is superfluous. Signed-off-by:

[PATCH 1/9] Provide a function to create a NUL-terminated string from unterminated data

Provide a function, kstrcreate(), that will create a NUL-terminated string from an unterminated character array where the length is known in advance. This is better than kstrndup() in situations where we already know the string length as the strnlen() in kstrndup() is superfluous. Signed-off-by:

Re: [PATCH] CIFS: fix oplock break deadlocks

Thoughts about whether cc: stable? On Wed, May 3, 2017 at 10:54 AM, Rabin Vincent wrote: > From: Rabin Vincent > > When the final cifsFileInfo_put() is called from cifsiod and an oplock > break work is queued, lockdep complains loudly: > >

[PATCH 2/9] Clean up whitespace in fs/namespace.c

Clean up line terminal whitespace in fs/namespace.c. Signed-off-by: David Howells --- fs/namespace.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index cc1375eff88c..db034b6afd43 100644 --- a/fs/namespace.c +++

Re: [PATCH] CIFS: fix oplock break deadlocks

Thoughts about whether cc: stable? On Wed, May 3, 2017 at 10:54 AM, Rabin Vincent wrote: > From: Rabin Vincent > > When the final cifsFileInfo_put() is called from cifsiod and an oplock > break work is queued, lockdep complains loudly: > > = > [

[PATCH 2/9] Clean up whitespace in fs/namespace.c

Clean up line terminal whitespace in fs/namespace.c. Signed-off-by: David Howells --- fs/namespace.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index cc1375eff88c..db034b6afd43 100644 --- a/fs/namespace.c +++ b/fs/namespace.c @@

[RFC][PATCH 0/9] VFS: Introduce mount context

Here are a set of patches to create a mount context prior to setting up a new mount, populating it with the parsed options/binary data and then effecting the mount. This allows namespaces and other information to be conveyed through the mount procedure. It also allows extra error information to

[RFC][PATCH 0/9] VFS: Introduce mount context

Here are a set of patches to create a mount context prior to setting up a new mount, populating it with the parsed options/binary data and then effecting the mount. This allows namespaces and other information to be conveyed through the mount procedure. It also allows extra error information to

Re: [PATCH v2 4/5] drm/etnaviv: Reuse dma_fence_release.

Lucas Stach writes: > Hi Eric, > > Am Mittwoch, den 12.04.2017, 12:12 -0700 schrieb Eric Anholt: >> If we follow the typical pattern of the base class being the first >> member, we can use the default dma_fence_free function. > > Sorry, I don't like this change. > While

Re: [PATCH v2 4/5] drm/etnaviv: Reuse dma_fence_release.

Lucas Stach writes: > Hi Eric, > > Am Mittwoch, den 12.04.2017, 12:12 -0700 schrieb Eric Anholt: >> If we follow the typical pattern of the base class being the first >> member, we can use the default dma_fence_free function. > > Sorry, I don't like this change. > While it provides a bit of code

[PATCH 3/3] f2fs: enhance scalability of trace macro

From: Chao Yu Use __print_flags in show_bio_op_flags and show_cpreason instead of __print_symbolic, it enables tracer function traverses and shows all bits in the flag. Additionally, add missing REQ_FUA into F2FS_OP_FLAGS. Signed-off-by: Chao Yu ---

[PATCH 3/3] f2fs: enhance scalability of trace macro

From: Chao Yu Use __print_flags in show_bio_op_flags and show_cpreason instead of __print_symbolic, it enables tracer function traverses and shows all bits in the flag. Additionally, add missing REQ_FUA into F2FS_OP_FLAGS. Signed-off-by: Chao Yu --- include/trace/events/f2fs.h | 29

[PATCH 2/3] f2fs: relocate inode_{,un}lock in F2FS_IOC_SETFLAGS

From: Chao Yu This patch expands cover region of inode->i_rwsem to keep setting flag atomically. Signed-off-by: Chao Yu --- fs/f2fs/file.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index

[PATCH 2/3] f2fs: relocate inode_{,un}lock in F2FS_IOC_SETFLAGS

From: Chao Yu This patch expands cover region of inode->i_rwsem to keep setting flag atomically. Signed-off-by: Chao Yu --- fs/f2fs/file.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index 1c1c9bc4f19a..e20a1c01e556 100644 ---

[PATCH 1/3] f2fs: support statx

From: Chao Yu Last kernel has already support new syscall statx() in commit a528d35e8bfc ("statx: Add a system call to make enhanced file info available"), with this interface we can show more file info including file creation and some attribute flags to user. This patch

[PATCH 1/3] f2fs: support statx

From: Chao Yu Last kernel has already support new syscall statx() in commit a528d35e8bfc ("statx: Add a system call to make enhanced file info available"), with this interface we can show more file info including file creation and some attribute flags to user. This patch tries to support this

RE: [PATCH] ARM64/PCI: Allow userspace to mmap PCI resources

> -Original Message- > From: Lorenzo Pieralisi [mailto:lorenzo.pieral...@arm.com] > Sent: Wednesday, May 03, 2017 9:29 PM > To: Bharat Bhushan > Cc: catalin.mari...@arm.com; will.dea...@arm.com; > bhelg...@google.com; linux-arm-ker...@lists.infradead.org; linux-

RE: [PATCH] ARM64/PCI: Allow userspace to mmap PCI resources

> -Original Message- > From: Lorenzo Pieralisi [mailto:lorenzo.pieral...@arm.com] > Sent: Wednesday, May 03, 2017 9:29 PM > To: Bharat Bhushan > Cc: catalin.mari...@arm.com; will.dea...@arm.com; > bhelg...@google.com; linux-arm-ker...@lists.infradead.org; linux- > ker...@vger.kernel.org

Re: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override

On 05/03/2017 04:58 PM, Leonard Crestez wrote: > On Wed, 2017-05-03 at 16:26 +0200, Marek Vasut wrote: > >> On 05/03/2017 03:57 PM, Shawn Guo wrote: >>> >>> On Tue, Apr 25, 2017 at 07:28:06PM +0200, Marek Vasut wrote: On 04/25/2017 07:23 PM, Leonard Crestez wrote: > > Anyway,

Re: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override

On 05/03/2017 04:58 PM, Leonard Crestez wrote: > On Wed, 2017-05-03 at 16:26 +0200, Marek Vasut wrote: > >> On 05/03/2017 03:57 PM, Shawn Guo wrote: >>> >>> On Tue, Apr 25, 2017 at 07:28:06PM +0200, Marek Vasut wrote: On 04/25/2017 07:23 PM, Leonard Crestez wrote: > > Anyway,

Re: [PATCH] iommu/arm-smmu-v3: Poll for CMDQ drain completion more effectively

On Wed, May 03, 2017 at 09:24:13PM +0530, Sunil Kovvuri wrote: > On Wed, May 3, 2017 at 9:07 PM, Will Deacon wrote: > > On Wed, May 03, 2017 at 06:49:09PM +0530, Sunil Kovvuri wrote: > >> On Thu, Apr 27, 2017 at 4:43 PM, wrote: > >> > From: Sunil

Re: [PATCH] iommu/arm-smmu-v3: Poll for CMDQ drain completion more effectively

On Wed, May 03, 2017 at 09:24:13PM +0530, Sunil Kovvuri wrote: > On Wed, May 3, 2017 at 9:07 PM, Will Deacon wrote: > > On Wed, May 03, 2017 at 06:49:09PM +0530, Sunil Kovvuri wrote: > >> On Thu, Apr 27, 2017 at 4:43 PM, wrote: > >> > From: Sunil Goutham > >> > > >> > Modified polling on CMDQ

Re: [PATCH] firmware: Google VPD: fix error handling on allocation failures

Am 03.05.2017 17:49, schrieb Colin King: > From: Colin Ian King > > Fix two allocation failure checks. Firstly, ensure info is checked > for a failed allocation; this fixes a potential null pointer > dereference issue on info->key. Secondly, free info is info->key >

Re: [PATCH] firmware: Google VPD: fix error handling on allocation failures

Am 03.05.2017 17:49, schrieb Colin King: > From: Colin Ian King > > Fix two allocation failure checks. Firstly, ensure info is checked > for a failed allocation; this fixes a potential null pointer > dereference issue on info->key. Secondly, free info is info->key > fails to allocate to fix a

Re: [PATCH] ARM64/PCI: Allow userspace to mmap PCI resources

On Wed, May 03, 2017 at 09:18:58PM +0530, Bharat Bhushan wrote: > This patch allows user-space to mmap PCI resources. This > patch is inline to arm32 bit implementation. > > Signed-off-by: Bharat Bhushan > --- > arch/arm64/include/asm/pci.h | 4 >

Re: [PATCH] ARM64/PCI: Allow userspace to mmap PCI resources

On Wed, May 03, 2017 at 09:18:58PM +0530, Bharat Bhushan wrote: > This patch allows user-space to mmap PCI resources. This > patch is inline to arm32 bit implementation. > > Signed-off-by: Bharat Bhushan > --- > arch/arm64/include/asm/pci.h | 4 > arch/arm64/kernel/pci.c | 19

Re: Linux 4.4.66

diff --git a/Documentation/devicetree/bindings/clock/sunxi.txt b/Documentation/devicetree/bindings/clock/sunxi.txt index 8a47b77abfca..e8c74a6e738b 100644 --- a/Documentation/devicetree/bindings/clock/sunxi.txt +++ b/Documentation/devicetree/bindings/clock/sunxi.txt @@ -18,6 +18,7 @@ Required

Re: Linux 4.4.66

diff --git a/Documentation/devicetree/bindings/clock/sunxi.txt b/Documentation/devicetree/bindings/clock/sunxi.txt index 8a47b77abfca..e8c74a6e738b 100644 --- a/Documentation/devicetree/bindings/clock/sunxi.txt +++ b/Documentation/devicetree/bindings/clock/sunxi.txt @@ -18,6 +18,7 @@ Required

Linux 4.9.26

I'm announcing the release of the 4.9.26 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Linux 4.9.26

I'm announcing the release of the 4.9.26 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: [PATCH] driver: input :touchscreen : Change Raydium firmware update parameter

On Wed, May 3, 2017 at 8:37 AM, jeffrey.lin wrote: > From: "jeffrey.lin" > > Change boot mode trigger parameter of Raydium firmware update. > That is a bit vague. What is changed to what, and why ? In other words, what prevents

Re: [PATCH] driver: input :touchscreen : Change Raydium firmware update parameter

On Wed, May 3, 2017 at 8:37 AM, jeffrey.lin wrote: > From: "jeffrey.lin" > > Change boot mode trigger parameter of Raydium firmware update. > That is a bit vague. What is changed to what, and why ? In other words, what prevents someone else from changing it back to the old value, using the

Linux 4.4.66

I'm announcing the release of the 4.4.66 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Linux 4.4.66

I'm announcing the release of the 4.4.66 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.9.26

diff --git a/Makefile b/Makefile index 8e18c63388c4..c09679c1a70d 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 25 +SUBLEVEL = 26 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arc/include/asm/atomic.h b/arch/arc/include/asm/atomic.h

Re: Linux 4.9.26

diff --git a/Makefile b/Makefile index 8e18c63388c4..c09679c1a70d 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 25 +SUBLEVEL = 26 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arc/include/asm/atomic.h b/arch/arc/include/asm/atomic.h

Re: Linux 4.10.14

diff --git a/Makefile b/Makefile index 8285f4de02d1..48756653c42c 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 10 -SUBLEVEL = 13 +SUBLEVEL = 14 EXTRAVERSION = NAME = Fearless Coyote diff --git a/arch/arc/include/asm/atomic.h b/arch/arc/include/asm/atomic.h

Re: Linux 4.10.14

diff --git a/Makefile b/Makefile index 8285f4de02d1..48756653c42c 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 10 -SUBLEVEL = 13 +SUBLEVEL = 14 EXTRAVERSION = NAME = Fearless Coyote diff --git a/arch/arc/include/asm/atomic.h b/arch/arc/include/asm/atomic.h

<    2   3   4   5   6   7   8   9   10   11   >