On 10/23/2015 11:44 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.2.5 release.
> There are 54 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Fri, 2015-10-23 at 22:50 +0200, Bendik Rønning Opstad wrote:
>
> +/**
> + * tcp_stream_is_thin_dpifl() - Tests if the stream is thin based on dynamic
> PIF
> + * limit
> + * @tp: the tcp_sock struct
> + *
> + * Return: true if current packets in flight (PIF)
On Fri, Oct 23, 2015 at 3:05 PM, Kukjin Kim wrote:
> On 10/24/15 04:47, Kukjin Kim wrote:
>> On 10/23/15 10:39, Krzysztof Kozlowski wrote:
>>> SRAM bindings for various SoCs, using the mmio-sram genalloc
>>> API, are spread over different places - per SoC vendor. Since all of
>>> these are quite
The following changes since commit 25cb62b76430a91cc6195f902e61c2cb84ade622:
Linux 4.3-rc5 (2015-10-11 11:09:45 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.3-rc7
for you to fetch changes up to
The following changes since commit 25cb62b76430a91cc6195f902e61c2cb84ade622:
Linux 4.3-rc5 (2015-10-11 11:09:45 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-4.3-rc7
for you to fetch changes up to
The following changes since commit 25cb62b76430a91cc6195f902e61c2cb84ade622:
Linux 4.3-rc5 (2015-10-11 11:09:45 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-4.3-rc7
for you to fetch changes up to
On Fri, Oct 23, 2015 at 2:22 PM, Kees Cook wrote:
> On Fri, Oct 23, 2015 at 2:07 PM, Andy Lutomirski wrote:
>> On Oct 23, 2015 10:01 AM, "Kees Cook" wrote:
>>>
>>> On Fri, Oct 23, 2015 at 9:19 AM, Andy Lutomirski
>>> wrote:
>>> > I would argue that, if auditing is off, audit_seccomp shouldn't
On Fri, Oct 23, 2015 at 2:07 PM, Andy Lutomirski wrote:
> On Oct 23, 2015 10:01 AM, "Kees Cook" wrote:
>>
>> On Fri, Oct 23, 2015 at 9:19 AM, Andy Lutomirski wrote:
>> > I would argue that, if auditing is off, audit_seccomp shouldn't do
>> > anything. After all, unlike e.g. selinux, seccomp is
On Fri, Oct 23, 2015 at 1:58 PM, Paul Moore wrote:
> On Fri, Oct 23, 2015 at 4:51 PM, Steve Grubb wrote:
>> On Friday, October 23, 2015 03:38:05 PM Paul Moore wrote:
>>> On Fri, Oct 23, 2015 at 1:01 PM, Kees Cook wrote:
>>> > On Fri, Oct 23, 2015 at 9:19 AM, Andy Lutomirski
>> wrote:
>>> >> I
On Oct 23, 2015 10:01 AM, "Kees Cook" wrote:
>
> On Fri, Oct 23, 2015 at 9:19 AM, Andy Lutomirski wrote:
> > I would argue that, if auditing is off, audit_seccomp shouldn't do
> > anything. After all, unlike e.g. selinux, seccomp is not a systemwide
> > policy, and seccomp signals might be
On 10/23/2015 11:45 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.56 release.
> There are 25 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 10/23/2015 11:44 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.92 release.
> There are 17 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
One of the largest chunks of log messages in a OOM is from dump_stack() and in
some cases it isn't even necessary to figure out what's going on. In
systems with multiple tenants/containers with limited resources each
OOMs can be way more frequent and being able to reduce the amount of log
output
[Apologies for the subject line, should just have the [RFC PATCH 5/7]]
On 23.10.2015 [14:00:08 -0700], Nishanth Aravamudan wrote:
> In order to cleanly expose the desired IOMMU page shift via the new
> dma_get_page_shift API, we need to have the sparc constants available in
> a more typical
We received a bug report recently when DDW (64-bit direct DMA on Power)
is not enabled for NVMe devices. In that case, we fall back to 32-bit
DMA via the IOMMU, which is always done via 4K TCEs (Translation Control
Entries).
The NVMe device driver, though, assumes that the DMA alignment for the
On sparc, the kernel's page size differs from the IOMMU's page size, so
override the generic implementation, which always returns the kernel's
page size, and return IOMMU_PAGE_SHIFT instead.
Signed-off-by: Nishanth Aravamudan
---
I know very little about sparc, so please correct me if this
Don't send HTML e-mail.
On Fri, 2015-10-23 at 02:06 -0500, Zhao Qiang-B45475 wrote:
> On Fri, 2015-10-23 at 11:00 AM, Wood Scott-B07421
> wrote:
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Friday, October 23, 2015 11:00 AM
> > To: Zhao Qiang-B45475
> > Cc:
In order to cleanly expose the desired IOMMU page shift via the new
dma_get_page_shift API, we need to have the sparc constants available in
a more typical location. There should be no functional impact to this
move, but it is untested.
Signed-off-by: Nishanth Aravamudan
---
When DDW (Dynamic DMA Windows) are present for a device, we have stored
the TCE (Translation Control Entry) size in a special device tree
property. Check if we have enabled DDW for the device and return the TCE
size from that property if present. If the property isn't present,
fallback to looking
The IOMMU page size is not always stored in struct iommu on Power.
Specifically if a device is configured for DDW (Dynamic DMA Windows aka.
64-bit direct DMA), the used TCE (Translation Control Entry) size is
stored in a special device property created at run-time by the DDW
configuration code.
On Fri, Oct 23, 2015 at 4:51 PM, Steve Grubb wrote:
> On Friday, October 23, 2015 03:38:05 PM Paul Moore wrote:
>> On Fri, Oct 23, 2015 at 1:01 PM, Kees Cook wrote:
>> > On Fri, Oct 23, 2015 at 9:19 AM, Andy Lutomirski
> wrote:
>> >> I would argue that, if auditing is off, audit_seccomp
[Sorry, subject should have been 0/7!]
On 23.10.2015 [13:54:20 -0700], Nishanth Aravamudan wrote:
> We received a bug report recently when DDW (64-bit direct DMA on Power)
> is not enabled for NVMe devices. In that case, we fall back to 32-bit
> DMA via the IOMMU, which is always done via 4K TCEs
On Power, the kernel's page size can differ from the IOMMU's page size,
so we need to override the generic implementation, which always returns
the kernel's page size. Lookup the IOMMU's page size from struct
iommu_table, if available. Fallback to the kernel's page size,
otherwise.
Signed-off-by:
On Fri, 2015-10-23 at 02:45 -0500, Zhao Qiang-B45475 wrote:
> On Fri, 2015-10-23 at 11:10 AM, Wood Scott-B07421
> wrote:
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Friday, October 23, 2015 11:10 AM
> > To: Zhao Qiang-B45475
> > Cc: linux-kernel@vger.kernel.org;
Drivers like NVMe need to be able to determine the page size used for
DMA transfers. Add a new API that defaults to return PAGE_SHIFT on all
architectures.
Signed-off-by: Nishanth Aravamudan
---
v1 -> v2:
Based upon feedback from Christoph Hellwig, implement the IOMMU page
size lookup as a
On Fri, 2015-10-23 at 02:49 -0500, Zhao Qiang-B45475 wrote:
> On Fri, Oct 23, 2015 at 11:20 AM, Wood Scott-B07421 > wrote:
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Friday, October 23, 2015 11:20 AM
> > To: Zhao Qiang-B45475
> > Cc: linux-kernel@vger.kernel.org;
The existing mechanism for detecting thin streams (tcp_stream_is_thin)
is based on a static limit of less than 4 packets in flight. This treats
streams differently depending on the connections RTT, such that a stream
on a high RTT link may never be considered thin, whereas the same
application
This is a request for comments.
Redundant Data Bundling (RDB) is a mechanism for TCP aimed at reducing
the latency for applications sending time-dependent data.
Latency-sensitive applications or services, such as online games and
remote desktop, produce traffic with thin-stream characteristics,
RDB is a mechanism that enables a TCP sender to bundle redundant
(already sent) data with TCP packets containing new data. By bundling
(retransmitting) already sent data with each TCP packet containing new
data, the connection will be more resistant to sporadic packet loss
which reduces the
We received a bug report recently when DDW (64-bit direct DMA on Power)
is not enabled for NVMe devices. In that case, we fall back to 32-bit
DMA via the IOMMU, which is always done via 4K TCEs (Translation Control
Entries).
The NVMe device driver, though, assumes that the DMA alignment for the
On Friday, October 23, 2015 03:38:05 PM Paul Moore wrote:
> On Fri, Oct 23, 2015 at 1:01 PM, Kees Cook wrote:
> > On Fri, Oct 23, 2015 at 9:19 AM, Andy Lutomirski
wrote:
> >> I would argue that, if auditing is off, audit_seccomp shouldn't do
> >> anything. After all, unlike e.g. selinux,
On Fri, Oct 23, 2015 at 04:14:10AM +, Kosuke Tatsukawa wrote:
> J. Bruce Fields wrote:
> > On Fri, Oct 16, 2015 at 02:28:10AM +, Kosuke Tatsukawa wrote:
> >> Tatsukawa Kosuke wrote:
> >> > J. Bruce Fields wrote:
> >> >> On Thu, Oct 15, 2015 at 11:44:20AM +, Kosuke Tatsukawa wrote:
> >>
From: Stephen Chandler Paul
Debugging input devices, specifically laptop touchpads, can be tricky
without having the physical device handy. Here we try to remedy that
with userio. This module allows an application to connect to a character
device provided by the kernel, and emulate any serio
Hi Guenter
thanks for the review, answers bellow.
Marc.
Le 23/10/2015 18:52, Guenter Roeck a écrit :
On 10/23/2015 09:13 AM, Marc Titinger wrote:
With the current implementation, the driver will prevent a readout at a
pace faster than the default conversion time (2ms) times the averaging
On 10/23/2015 11:45 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.1.12 release.
> There are 46 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Fri 23 Oct 13:01 PDT 2015, Stephen Boyd wrote:
> Now that we have a generic library function for this, replace the
> open-coded instance.
>
> Cc: Bjorn Andersson
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Wednesday 21 October 2015 22:59:38 Alexandre Belloni wrote:
>
> The following changes since commit a9b672a636a599cc052afcb6837e3177dc53c143:
>
> ARM: at91/dt: sama5d2 Xplained: add device pin muxing (2015-09-23 16:26:47
> +0200)
>
> are available in the git repository at:
>
>
Queued for 4.4. Thanks.
-corey
On 10/23/2015 02:51 PM, Amitoj Kaur Chawla wrote:
> This patch replaces timeval with timespec64 as 32 bit 'struct timeval'
> will not give current time beyond 2038.
>
> The patch changes the code to use ktime_get_real_ts64() which returns
> a 'struct timespec64'
Hi,
Greeting for the day,
Would you be interested in reaching out “EMC Data Storage Users List” with
opt-in verified contact information?
We also have data for Dell SAN Users, EMC Data Domain Users, EMC Network
Storage Users, EMC SAN Users, EMC PowerPath, IBM SAN Users, HP SAN Users, HP
On Wednesday 21 October 2015 20:36:28 Masahiro Yamada wrote:
> The user space should not expect that a particular I2C channel is
> always visible through the same character device.
> No reason to fix the I2C indexes with aliases.
>
> Signed-off-by: Masahiro Yamada
>
As I said in my reply to
On 10/23/15 10:39, Krzysztof Kozlowski wrote:
> Exynos SoC Device Tree bindings are spread over arm/exynos/ and
> arm/samsung/ directories. There is no need for that separation and it
> actually confuses. Put power domain bindings under power/ and
> remaining samsung-boards.txt under arm/samsung/.
Den 23.10.2015 kl. 20:46, skrev Greg Kroah-Hartman:
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Konstantin Khlebnikov
commit fe32d3cd5e8eb0f82e459763374aa80797023403 upstream.
This one broke drivers/xen/ build
On Wednesday 21 October 2015 20:36:30 Masahiro Yamada wrote:
> Initial version of DTS for ProXstream2 Vodka board.
>
> Signed-off-by: Masahiro Yamada
Applied, thanks!
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wednesday 21 October 2015 20:36:29 Masahiro Yamada wrote:
> Initial version of DTS for ProXstream2 Gentil board.
>
> Signed-off-by: Masahiro Yamada
Applied, thanks!
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wednesday 21 October 2015 17:49:12 Masahiro Yamada wrote:
> > Right. In-kernel drivers can handle it nicely.
> >
> > Also, we can write a device tree that specifies device connection
> > hierarchy like follows.
> > The device names will appear under /sys/ directory and user-land
> >
I am announcing the release of the Linux 3.19.8-ckt8 kernel.
The updated 3.19.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.19.y
and can be browsed at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.19.y
The diff from v3.19.8-ckt7 is posted as
On Wednesday 21 October 2015 20:36:27 Masahiro Yamada wrote:
> Specifying both console and stdout-path is redundant. Add options
> ":115200n8" to stdout-path and drop "console=ttyS0,115200".
>
> Signed-off-by: Masahiro Yamada
>
Applied, thanks!
Arnd
--
To unsubscribe from this list:
Hi Marc,
[auto build test WARNING on hwmon/hwmon-next -- if it's inappropriate base,
please suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Marc-Titinger/hwmon-ina2xx-port-to-using-remap-improve-bandwidth/20151024-001809
config:
Andreas Gruenbacher:
>
> Here is another update of the richacl patch queue. I would like to ask
for
> feedback so that the core and local filesystem code (patches 1-25) can be
> merged in the 4.4 merge window.
>
> Changes since the last posting (http://lwn.net/Articles/661078/):
>
> * On
Hi Peter,
On Fri, 23 Oct 2015 11:50:08 +0200
Peter Zijlstra wrote:
[...]
> > >>This removes the warning, but I am not sure if it is the correct
> > >>fix (is it valid to unpin rq->lock, here?).
> > >>
> > >>If someone can confirm that this is the correct approach, I'll
> > >>test the patch a
diff --git a/Makefile b/Makefile
index 2e4c860..e5cefec 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 3
PATCHLEVEL = 13
SUBLEVEL = 11
-EXTRAVERSION = -ckt27
+EXTRAVERSION = -ckt28
NAME = King of Alienated Frog Porn
# *DOCUMENTATION*
diff --git
Hi Tejun,
On Fri, Oct 23, 2015 at 11:09 AM, Tejun Heo wrote:
> Hello,
>
> On Fri, Oct 23, 2015 at 10:01:35AM +0530, Vinayak Kale wrote:
>> > It looks like it'd work given that it's forcing qc->tag into
>> > tf->nsect. What's the use case tho?
>>
>> We need to issue NCQ commands with priority
I am announcing the release of the Linux 3.13.11-ckt28 kernel.
The updated 3.13.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.13.y
and can be browsed at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.13.y
The diff from v3.13.11-ckt27 is posted
On 10/24/15 04:47, Kukjin Kim wrote:
> On 10/23/15 10:39, Krzysztof Kozlowski wrote:
>> SRAM bindings for various SoCs, using the mmio-sram genalloc
>> API, are spread over different places - per SoC vendor. Since all of
>> these are quite similar (they depend on mmio-sram) move them to a common
> > Should it (ACPI walk) be done in PCI case as well? If so, then it needs
> > to be done up to i2c-core. There you may adjust the bus speed whenever
> > slave device is enumerated.
> >
> I think the "ACPI walk for bus speed" also works for PCI case. It'll
> be good to do this in i2c-core.
> By
This patch is to the lpfc_els.c which resolves following warning
reported by coccicheck:
WARNING: kzalloc should be used for rdp_context, instead of
kmalloc/memset
Signed-off-by: Punit Vara
---
drivers/scsi/lpfc/lpfc_els.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This is the patch to the hpsa.c file that resolves following warning
reported by coccicheck:
WARNING: casting value returned by memory allocation function to
(BIG_IOCTL_Command_struct *) is useless.
Signed-off-by: Punit Vara
---
drivers/scsi/hpsa.c | 3 +--
1 file changed, 1 insertion(+), 2
Punit Vara (2):
scsi: lpfc: Use kzalloc instead of kmalloc
scsi: remove useless casting value returned by kmalloc to structure
drivers/scsi/hpsa.c | 3 +--
drivers/scsi/lpfc/lpfc_els.c | 2 +-
2 files changed, 2 insertions(+), 3 deletions(-)
--
2.5.3
--
To unsubscribe from this
Some drivers need to read data out of iomem areas 32-bits at a
time. Add an API to do this.
Cc: Bjorn Andersson
Signed-off-by: Stephen Boyd
---
include/linux/io.h | 1 +
lib/iomap_copy.c | 21 +
2 files changed, 22 insertions(+)
diff --git a/include/linux/io.h
Now that we have a generic library function for this, replace the
open-coded instance.
Cc: Hauke Mehrtens
Cc: Rafał Miłecki
Cc: Paul Walmsley
Cc: linux-m...@linux-mips.org
Signed-off-by: Stephen Boyd
---
drivers/firmware/broadcom/bcm47xx_nvram.c | 11 +++
1 file changed, 3
Now that we have a generic library function for this, replace the
open-coded instance.
Cc: Bjorn Andersson
Signed-off-by: Stephen Boyd
---
drivers/soc/qcom/smd.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/drivers/soc/qcom/smd.c b/drivers/soc/qcom/smd.c
The SMD driver is reading and writing chunks of data to iomem,
and there's an __iowrite32_copy() function for the writing part, but
no __ioread32_copy() function for the reading part. This series
adds __ioread32_copy() and uses it in two places.
This is a respin with some small fixes found with
The frv port uses compiler builtins, __builtin_read*(), for the
I/O read routines. Unfortunately, these don't accept const void
pointers although the generic ASM implementations do, so generic
code passing const pointers to these APIs cause compilers to emit
warnings. Add wrapper functions that
On 10/23/2015 12:05 PM, Alex Williamson wrote:
On Fri, 2015-10-23 at 11:36 -0700, Alexander Duyck wrote:
On 10/21/2015 09:37 AM, Lan Tianyu wrote:
This patchset is to propose a new solution to add live migration support for
82599
SRIOV network card.
Im our solution, we prefer to put all
During the removal of the cfs wrappers the kg_sem semaphore
was handled incorrectly. We need to take a write lock when
writing data to the kkuc_groups. The libcfs_kkuc_group_foreach
needs to only take a read lock. This makes use match the
OpenSFS development branch.
Signed-off-by: James Simmons
From: Henri Doreau
Associate copytool registration to a given MDC import so that
multiple mounts of the same filesystem do not lead to having the
copytool registered multiple time.
Signed-off-by: Henri Doreau
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3882
Reviewed-on:
From: frank zago
Move the kernel portion from libcfs to obdclass. This code is
only used by lustre. This is broken out of the original patch
14270. The part covered by this change is as follows:
The original code in kernel_user_comm.c is split into two parts:
* obdclass/kernelcomm.c for the
From: frank zago
Point to the right place for GNU license. Update Intel copyright.
Update Nathan Rutmans email address. This was broken out of the
original patch 14270.
Signed-off-by: frank zago
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6245
Reviewed-on:
From: frank zago
Split the kernel comm header in libcfs into two new headers
to handle both kernel space and user space for the lustre layer.
This is broken out of the original patch 14270. The part covered
by this change is as follows:
The original libcfs_kernelcomm.h header is split into
The kernel communication code used for HSM and changelog is
entangled. Move the user space bits into the liblustreapi. This will
also help for a possible relicensing. The kernel portion is also moved
from libcfs to obdclass.
The original libcfs_kernelcomm.h header is split into three parts:
*
On Tue, Oct 06, 2015 at 05:22:56PM +0800, Eddie Huang wrote:
> From: Liguo Zhang
>
> mt65xx i2c controller initial setting will be cleared after system suspend,
> so we should init mt65xx i2c controller again when system resume.
>
> Signed-off-by: Liguo Zhang
> Signed-off-by: Eddie Huang
On Saturday 24 October 2015 01:21:04 Amitoj Kaur Chawla wrote:
> This patch replaces timeval with timespec64 as 32 bit 'struct timeval'
> will not give current time beyond 2038.
>
> The patch changes the code to use ktime_get_real_ts64() which returns
> a 'struct timespec64' instead of
This patch replaces timeval with timespec64 as 32 bit 'struct timeval'
will not give current time beyond 2038.
The patch changes the code to use ktime_get_real_ts64() which returns
a 'struct timespec64' instead of do_gettimeofday() which returns a
'struct timeval'
This patch also alters the
Hi Tang,
Your patch assumes that system supports memory less node and
fixes the issue on x86 architecture.
But if system does not supports memory less node, your patch cannot
fix the issue. It means that system must support memory less node
to support Node (CPU and memory) hotplug.
Why don't
On 10/23/15 10:39, Krzysztof Kozlowski wrote:
> SRAM bindings for various SoCs, using the mmio-sram genalloc
> API, are spread over different places - per SoC vendor. Since all of
> these are quite similar (they depend on mmio-sram) move them to a common
> place.
>
> Signed-off-by: Krzysztof
On 10/22/15 10:28, Krzysztof Kozlowski wrote:
> Extend the Samsung Exynos maintainer entry to match SoC documentation
> and SoC dt-bindings directories. Without that some files, like
> bindings/arm/samsung/pmu.txt, are not matched by existing patterns.
>
> This also may serve as a hint where new
On 10/23/15 13:19, Krzysztof Kozlowski wrote:
> Update the documentation about:
> 1. Usage of PMU_SPARE2 register.
>Bootloaders on Exynos542x-based boards often use the register
>PMU_SPARE2 (0x908) in the same way as on Exynos3250: as a indicator
>the secondary CPU was booted on. The
On Fri, Oct 23, 2015 at 1:01 PM, Kees Cook wrote:
> On Fri, Oct 23, 2015 at 9:19 AM, Andy Lutomirski wrote:
>> I would argue that, if auditing is off, audit_seccomp shouldn't do
>> anything. After all, unlike e.g. selinux, seccomp is not a systemwide
>> policy, and seccomp signals might be
Acked-by: Julia Lawall
On Fri, 23 Oct 2015, Daniel Granat wrote:
> * Extend checking on tables containing structures which are
> initialized without specifying member name. Added new tables
> for checking: i2c_device_id and platform_device_id.
>
> Signed-off-by: Daniel Granat
> ---
>
On 10/16/15 14:42, Krzysztof Kozlowski wrote:
> Dear Kukjin,
>
> Last batch of changes to DT for Exynos for v4.4.
> Includes dependency - clock driver changes.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit 9aaf43d9b59d6b5d8daeb3a4b9d894ea88fc34c5:
>
> clk: samsung:
On 2015-10-23 14:41, Andreas Gruenbacher wrote:
From: "Aneesh Kumar K.V"
This feature flag selects richacl instead of posix acl support on the
file system. In addition, the "acl" mount option is needed for enabling
either of the two kinds of acls.
Signed-off-by: Aneesh Kumar K.V
On Sat, Oct 24, 2015 at 12:00:14AM +0800, yalin wang wrote:
>
> > On Oct 23, 2015, at 18:11, Kirill A. Shutemov wrote:
> >
> > On Fri, Oct 23, 2015 at 05:38:49PM +0800, yalin wang wrote:
> >> This crash is caused by NULL pointer deference:
> >> [ 182.639154 ] Unable to handle kernel NULL
Add a stub for acpi_preset_companion(). Fixes build failures when
acpi_preset_companion() is used and CONFIG_ACPI is not set.
Acked-by: Mika Westerberg
Signed-off-by: Dustin Byford
---
include/linux/acpi.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/include/linux/acpi.h
Although I2C mux devices are easily enumerated using ACPI (_HID/_CID or
device property compatible string match), enumerating I2C client devices
connected through an I2C mux needs a little extra work.
This change implements a method for describing an I2C device hierarchy that
includes mux devices
v5:
- rebased on i2c/for-next (Jarkko, Wolfram)
- include acpi.h in designware drivers (Mika)
- remove return from void stub function (Mika)
- add acks and tested-by from Mika
v4:
- Moved the acpi_preset_companion() stub to a separate patch.
- Moved ACPI companion set from i2c-core to i801, ismt,
On Fri, 23 Oct 2015 20:14:06 +0200
Maxime Ripard wrote:
> On Wed, Oct 21, 2015 at 06:20:27PM +0200, Jens Kuske wrote:
> > + bus_gates: clk@01c20060 {
> > + #clock-cells = <1>;
> > + compatible = "allwinner,sun8i-h3-bus-gates-clk";
> > +
POSIX ACLs and richacls are both objects allocated by kmalloc() with a
reference count which are freed by kfree_rcu(). An inode can either
cache an access and a default POSIX ACL, or a richacl (richacls do not
have default acls). To allow an inode to cache either of the two kinds
of acls,
On Fri, 2015-10-23 at 16:05 +0300, Petko Manolov wrote:
> On 15-10-22 21:49:25, Dmitry Kasatkin wrote:
> > diff --git a/security/integrity/ima/Kconfig b/security/integrity/ima/Kconfig
> > index df30334..a292b88 100644
> > --- a/security/integrity/ima/Kconfig
> > +++
On 10/13/15 09:38, Krzysztof Kozlowski wrote:
> Dear Kukjin,
>
> This is another round of defconfig related changes for 4.4.
>
> Description along with a tag.
> You can find them also on the lists with my reviewed-by.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit
Add richacl xattr handler implementing the xattr operations based on the
get_richacl and set_richacl inode operations.
Signed-off-by: Andreas Gruenbacher
---
fs/richacl_xattr.c| 78 +++
include/linux/richacl_xattr.h | 2 ++
2 files changed,
On 15/10/23, Andy Lutomirski wrote:
> I would argue that, if auditing is off, audit_seccomp shouldn't do
> anything. After all, unlike e.g. selinux, seccomp is not a systemwide
> policy, and seccomp signals might be ordinary behavior that's internal
> to the seccomp-using application. IOW, for
Make xfs_set_mode non-static and move it from xfs_acl.c into xfs_inode.c.
Signed-off-by: Andreas Gruenbacher
---
fs/xfs/xfs_acl.c | 18 --
fs/xfs/xfs_inode.c | 24
fs/xfs/xfs_inode.h | 2 ++
3 files changed, 26 insertions(+), 18 deletions(-)
diff
The POSIX standard puts processes which are not the owner or a member in
the owning group or which match any ace other then everyone@ on the
other file class. We only know if a process is in the other class after
processing the entire acl.
Move all everyone@ aces in the acl down in the acl so
The file masks in richacls make chmod and creating new files more
efficient than having to apply file permission bits to the acl directly.
They also allow us to regain permissions from an acl even after a
restrictive chmod, because the permissions in the acl itself are not
being destroyed. In
The richacl feature flag (mkfs.xfs -m richacl=1) determines whether an xfs
filesystem supports posix acls or richacls. Richacls are stored in
"system.richacl" xattrs.
On the grounds that richacls add relatively little overhead compared to the
size of xfs itself, to keep the testing matrix small,
On Fri, Oct 23, 2015 at 11:53 AM, Toshi Kani wrote:
> This patch-set extends the EINJ driver to allow injecting a memory
> error to NVDIMM. It first extends iomem resource interface to support
> checking a NVDIMM region.
>
> Patch 1/3 changes region_intersects() to accept non-RAM regions, and
>
At the time that this code was originally written, call_srcu didn't
exist, so this thread was required to ensure that we waited for that
SRCU grace period to settle before finally freeing the object.
It does exist now however and we can much more efficiently use call_srcu
to handle this. That
On Fri, 2015-10-23 at 11:36 -0700, Alexander Duyck wrote:
> On 10/21/2015 09:37 AM, Lan Tianyu wrote:
> > This patchset is to propose a new solution to add live migration support
> > for 82599
> > SRIOV network card.
> >
> > Im our solution, we prefer to put all device specific operation into VF
Change the acl so that everyone@ is granted the permissions set in the
other mask.
Signed-off-by: Andreas Gruenbacher
Reviewed-by: J. Bruce Fields
---
fs/richacl_compat.c | 41 +
1 file changed, 41 insertions(+)
diff --git a/fs/richacl_compat.c
A file can have "no acl" in the sense that only the file mode permission
bits determine access. In that case, the getxattr system call fails with
errno == ENODATA (No such attribute).
Over the NFSv4 protocol, a file always has an acl, and we convert the file
mode permission bits into an
101 - 200 of 1620 matches
Mail list logo
