On Saturday, September 26, 2015 11:20:50 AM Alan Stern wrote:
> On Sat, 26 Sep 2015, Rafael J. Wysocki wrote:
>
> > > > So something like:
> > > >
> > > > echo on >/sys/.../power/control (in case the device was
> > > > already in runtime suspend with wakeups
On Saturday, September 26, 2015 12:52:08 PM James Bottomley wrote:
> On Fri, 2015-09-25 at 22:58 +0200, Rafael J. Wysocki wrote:
> > On Friday, September 25, 2015 01:25:49 PM Viresh Kumar wrote:
> > > On 25 September 2015 at 13:33, Rafael J. Wysocki
> > > wrote:
> > > >
On 25/09/15 15:46, Javier Martinez Canillas wrote:
The regulator-compatible property from the regulator DT binding was
deprecated and the correct approach is to use the node's name.
This patch has no functional changes since the values of the node's
name and the regulator-compatible match for
On 28/08/15 04:11, fan.c...@mediatek.com wrote:
From: Fan Chen
This patch adds psci comatible properties to support all mandatory
functions of PSCI-1.0, PSCI-0.2 and PSCI-0.1, and system suspend
can be supported in PSCI-1.0.
Signed-off-by: Fan Chen
Fixes the following sparse warning:
security/smack/smack_lsm.c:55:1: warning: symbol 'smk_ipv6_port_list'
was not declared. Should it be static?
Signed-off-by: Geliang Tang
---
security/smack/smack_lsm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Sun, 27 Sep 2015 15:25:41 +0200
Sedat Dilek wrote:
> Hi Ingo, Hi Steven,
>
> I am still fighting with a llvmlinux problem in the area...
>
> workqueue | hid | irq-flags (hardirqs/sofirqs disabled) | whatever?!
>
> ...(see [0]).
>
> [ 24.705463] BUG: sleeping
Hi!
> > > > That, or there may be an additional value, say "aggressive", to write
> > > > to the
> > > > control file in which case it becomes just
> > > >
> > > > echo aggressive >/sys/.../power/control
> > >
> > > That said I suppose that the "off" value for the "wakeup" file might also
> >
On 09/27/2015 06:10 PM, Jean Delvare wrote:
> Looks good, however I think you should #include to
> avoid build failures in the future or on certain architectures.
already includes
on any arch.
p4-clockmod.c builds only on x86 arch, it's Pentium 4
on demand clock modulation/speed scaling
On Sun, Sep 27, 2015 at 8:47 AM, J. R. Okajima wrote:
>
>
> Hello NFS folks,
>
> I don't know whether this is a known issue or not (since I was off from
> development for a few months), but I've got a "general protection fault:
> " message from linux-4.3-rc2.
> Here are
On Sun, Sep 27, 2015 at 11:16:49AM -0700, Guenter Roeck wrote:
> On 09/26/2015 01:54 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 4.2.2 release.
> >There are 134 patches in this series, all will be posted as a response
> >to this one. If anyone has any
Hi Ingo, Hi Steven,
I am still fighting with a llvmlinux problem in the area...
workqueue | hid | irq-flags (hardirqs/sofirqs disabled) | whatever?!
...(see [0]).
[ 24.705463] BUG: sleeping function called from invalid context at
kernel/workqueue.c:2680
[ 24.705576] in_atomic(): 0,
Fixes the following sparse warnings:
crypto/skcipher.c:94:5:
warning: symbol 'crypto_init_skcipher_ops_blkcipher'
was not declared. Should it be static?
crypto/skcipher.c:185:5:
warning: symbol 'crypto_init_skcipher_ops_ablkcipher'
was not declared. Should it be static?
Signed-off-by:
On 23/09/15 15:26, Peter Rosin wrote:
> From: Peter Rosin
>
> Signed-off-by: Peter Rosin
Applied to the togreg branch of iio.git - initially pushed out as testing
for the autobuilders to play with it.
Note will probably get rebased shortly once Greg has picked
On 23/09/15 13:44, Tirdea, Irina wrote:
>
>
>> -Original Message-
>> From: Markus Pargmann [mailto:m...@pengutronix.de]
>> Sent: 16 September, 2015 13:13
>> To: Tirdea, Irina
>> Cc: Jonathan Cameron; Srinivas Pandruvada; Lars-Peter Clausen;
>> linux-...@vger.kernel.org;
On Sun, Sep 27, 2015 at 6:02 PM, Sedat Dilek wrote:
> On Sun, Sep 27, 2015 at 5:58 PM, Sedat Dilek wrote:
>> On Sun, Sep 27, 2015 at 5:55 PM, Sedat Dilek wrote:
>>> On Sun, Sep 27, 2015 at 5:49 PM, Paul E. McKenney
>>>
Even if --symfs is used to point to the debug binaries, we send in the
non-debug filenames to libunwind, which leads to libunwind not finding
the debug frame. Fix this.
Signed-off-by: Rabin Vincent
---
tools/perf/util/unwind-libunwind.c |2 +-
1 file changed, 1
On 16/09/15 15:34, Daniel Kurtz wrote:
On Wed, Sep 16, 2015 at 9:35 AM, Yingjoe Chen wrote:
Node name in device tree should describe general class of the
device. Correct incorrect i2c node names.
Signed-off-by: Yingjoe Chen
On 25/09/15 10:51, Lars-Peter Clausen wrote:
> On 09/25/2015 11:45 AM, Martin Kepplinger wrote:
>> This shouldn't actually change anything since the core calls the events
>> sysfs folder "events" anyways.
>>
>> Signed-off-by: Martin Kepplinger
>
> Acked-by: Lars-Peter Clausen
On 16/09/15 04:21, Yingjoe Chen wrote:
On Wed, 2015-09-16 at 10:04 +0800, Yingjoe Chen wrote:
Enable MTK_TIMER for MediaTek plaform, which will be used as
schedule clock.
Sorry, sending this series too early without cover letter and removing
Change-Id. Here's the cover letter:
This is
On 26 September 2015 at 22:31, Jiri Slaby wrote:
> But this has to crash whenever the file is read as val's storage is gone at
> that moment already, right?
Yeah, its fixed now in the new version. This was a *really* bad idea :(
--
To unsubscribe from this list: send the
Fixes the following sparse warning:
fs/namespace.c:1654:22: warning: symbol 'to_mnt_ns' was not declared.
Should it be static?
Signed-off-by: Geliang Tang
---
fs/namespace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/namespace.c b/fs/namespace.c
The nr variable is meant to be returned by a function which is
declared as returning "unsigned long", so declare nr as such.
Lower down we should also declare delta and nr_pagecache_reclaimable
as being unsigned longs because they're used to store the values
returned by zone_page_state() and
Their stored values come from zone_page_state() which returns
an unsigned long. To improve code correctness we should avoid
mixing signed and unsigned integers.
Signed-off-by: Alexandru Moise <00moses.alexande...@gmail.com>
---
mm/page_alloc.c | 4 ++--
1 file changed, 2 insertions(+), 2
On Saturday, September 26, 2015 01:05:11 AM Len Brown wrote:
> Hi Rafael,
Hi Len,
> The following patches are available on my "intel_idle"
> and "turbostat" branches, as usual, plus here for review.
There's no intel_idle branch in your tree, but there is a cpuidle one
and I found the patch
On 25/09/15 10:52, Martin Kepplinger wrote:
> This shouldn't actually change anything since the core calls the events
> sysfs folder "events" anyways.
>
> Signed-off-by: Martin Kepplinger
Applied. Thanks
> ---
> drivers/iio/adc/max1363.c | 1 -
> 1 file changed, 1 deletion(-)
On 25/09/15 12:24, Lars-Peter Clausen wrote:
> On 09/25/2015 11:54 AM, Martin Kepplinger wrote:
>> This shouldn't change anything since the core calls the events folder
>> "events" anyways.
>>
>> Signed-off-by: Martin Kepplinger
>
> Acked-by: Lars-Peter Clausen
On 23/09/15 13:48, H. Nikolaus Schaller wrote:
> This driver code was found as:
>
> https://android.googlesource.com/kernel/tegra/+/aaabb2e045f31e5a970109ffdaae900dd403d17e/drivers/staging/iio/adc
>
> Fixed various compilation issues and test this driver on omap5 evm.
>
> Signed-off-by: Pradeep
On 23/09/15 15:26, Peter Rosin wrote:
> From: Peter Rosin
>
> Add support for Microchip digital potentiometers and rheostats
> MCP4531, MCP4532, MCP4551, MCP4552
> MCP4631, MCP4632, MCP4651, MCP4652
>
> DEVICE Wipers Steps Resistor Opts (kOhm) i2c address
>
On 23/09/15 14:43, Bhuvanchandra DV wrote:
> There is an observed temperature difference of ~20°C with the
> internal temperature reading and the temperature measured on
> SoC package. Existing calculations consider the typical values
> provided in datasheet. Those typical values are valid for
>
On Sun, Sep 27, 2015 at 06:25:37PM +0200, Sedat Dilek wrote:
> On Sun, Sep 27, 2015 at 6:16 PM, Sedat Dilek wrote:
> > On Sun, Sep 27, 2015 at 6:02 PM, Sedat Dilek wrote:
> >> On Sun, Sep 27, 2015 at 5:58 PM, Sedat Dilek
Attached is a patch for two modules: RapidDisk & RapidCache. RapidDisk is a
Linux RAM drive module which allows the user to dynamically create, remove,
and resize RAM-based block devices. RapidDisk is designed to work with both
volatile and non-volatile memory. In the case of volatile memory,
On Sun, Sep 27, 2015 at 6:42 PM, Paul E. McKenney
wrote:
> On Sun, Sep 27, 2015 at 05:55:43PM +0200, Sedat Dilek wrote:
>> On Sun, Sep 27, 2015 at 5:49 PM, Paul E. McKenney
>> wrote:
>> > On Sun, Sep 27, 2015 at 09:37:05AM +0200, Sedat
On Sun, Sep 27, 2015 at 09:30:48AM -0700, Andy Lutomirski wrote:
> On Sep 26, 2015 1:19 PM, "H. Peter Anvin" wrote:
> >
> > Sadly a lot of firmware is known to fail in that configuration :( That was
> > very much our guest choice.
> >
>
> Why can't we map everything completely
Linus,
please pull the latest locking-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-for-linus
A single bugfix for lockdep:
- Preserve the pinning counter when rebuilding the lock stack.
Thanks,
tglx
-->
Linus,
please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
Another pile of fixes for perf
- Plug overflows and races in the core code
- Sanitize the flow of the perf syscall so we error out
Den 24.09.2015 14:27, skrev Tomi Valkeinen:
Hi all,
fbdev is (more or less) maintained, but it's a deprecated framework. All
new Linux display drivers should be done on DRM.
So let's not add any more new fbdev drivers.
I will continue to maintain the current fbdev drivers, and I don't mind
On Sun, Sep 27, 2015 at 12:04 AM, Viresh Kumar wrote:
> global_lock is defined as an unsigned long and accessing only its lower
> 32 bits from sysfs is incorrect, as we need to consider other 32 bits
> for big endian 64-bit systems. There are no such platforms yet, but
On Sun, Sep 27, 2015 at 5:49 PM, Paul E. McKenney
wrote:
> On Sun, Sep 27, 2015 at 09:37:05AM +0200, Sedat Dilek wrote:
>> On Sun, Sep 27, 2015 at 9:32 AM, Paul E. McKenney
>> wrote:
>> > On Sun, Sep 27, 2015 at 08:28:39AM +0200, Sedat
Hi Denys,
On Sat, 26 Sep 2015 14:47:18 +0200, Denys Vlasenko wrote:
> Straigntforward conversion from
> int has_N44_O17_errata[NR_CPUS]
> to
> DECLARE_BITMAP(has_N44_O17_errata, NR_CPUS)
>
> Saves about 2 kbytes in bss for NR_CPUS=512.
>
> Signed-off-by: Denys Vlasenko
Hi all,
On 27 September 2015 at 14:09, Noralf Trønnes wrote:
>
> Den 24.09.2015 14:27, skrev Tomi Valkeinen:
>>
>> Hi all,
>>
>> fbdev is (more or less) maintained, but it's a deprecated framework. All
>> new Linux display drivers should be done on DRM.
>>
>> So let's not add
On Tue, Sep 22, 2015 at 2:33 PM, Andy Shevchenko
wrote:
> On Tue, 2015-09-22 at 13:22 +0200, Geert Uytterhoeven wrote:
>> On Tue, Sep 22, 2015 at 1:19 PM, Geert Uytterhoeven
>> wrote:
>> > JFYI, when comparing v4.3-rc2[1] to v4.3-rc1[3],
On Sun, Sep 27, 2015 at 07:24:22PM +0200, Sedat Dilek wrote:
> On Sun, Sep 27, 2015 at 6:42 PM, Paul E. McKenney
> wrote:
> > On Sun, Sep 27, 2015 at 05:55:43PM +0200, Sedat Dilek wrote:
> >> On Sun, Sep 27, 2015 at 5:49 PM, Paul E. McKenney
> >>
On 23/09/15 15:45, Sascha Hauer wrote:
On Fri, Sep 11, 2015 at 09:05:20PM +0800, Henry Chen wrote:
The watchdog may not be initialized by the bootloader, even if the rest
of the pwrap is. Move the watchdog initialization out of pwrap_init() to
make sure the watchdog is always initialized and
The message queue is replaced with standard Linux linked list. A check for
return value of receive method is added.
Signed-off-by: Chandra S Gorentla
---
drivers/staging/wilc1000/host_interface.c | 7 +++-
drivers/staging/wilc1000/wilc_msgqueue.c | 62
On Sun, Sep 27, 2015 at 12:18:41PM +0530, Sudip Mukherjee wrote:
> From: Daniel Axtens
>
> commit 4e1efb403c1c016ae831bd9988a7d2e5e0af41a0 upstream.
>
> If the driver doesn't participate in EEH, the AFUs will be removed
> by cxl_remove, which will be invoked by EEH.
>
> If the
On Sun, Sep 27, 2015 at 05:55:43PM +0200, Sedat Dilek wrote:
> On Sun, Sep 27, 2015 at 5:49 PM, Paul E. McKenney
> wrote:
> > On Sun, Sep 27, 2015 at 09:37:05AM +0200, Sedat Dilek wrote:
> >> On Sun, Sep 27, 2015 at 9:32 AM, Paul E. McKenney
> >>
On Sun, 27 Sep 2015, angelo wrote:
> On 27/09/2015 03:36, Hugh Dickins wrote:
> > Let's Cc linux-fsdevel, who will be more knowledgable.
> >
> > On Sun, 27 Sep 2015, angelo wrote:
> >
> > > Hi all,
> > >
> > > running xfstests, generic 308 on whatever 32bit arch is possible
> > > to observe cpu
On Saturday, September 26, 2015 09:33:56 PM Arnd Bergmann wrote:
> On Saturday 26 September 2015 11:40:00 Viresh Kumar wrote:
> > On 25 September 2015 at 15:19, Rafael J. Wysocki wrote:
> > > So if you allow something like debugfs to update your structure, how
> > > do you make
On Sun, Sep 27, 2015 at 09:15:24PM +0800, Fengguang Wu wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit 991de2e59090e55c65a7f59a049142e3c480f7bd
> Author:
Fixes the following sparse warning:
drivers/acpi/apei/apei-base.c:298:23: warning: symbol
'apei_resources_all' was not declared. Should it be static?
Signed-off-by: Geliang Tang
---
drivers/acpi/apei/apei-base.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Fixes the following sparse warning:
security/selinux/hooks.c:3242:5: warning: symbol 'ioctl_has_perm' was
not declared. Should it be static?
Signed-off-by: Geliang Tang
---
security/selinux/hooks.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Fixes the following sparse warning:
arch/x86/kernel/cpu/intel_cacheinfo.c:160:33: warning: symbol
'num_cache_leaves' was not declared. Should it be static?
Signed-off-by: Geliang Tang
---
arch/x86/kernel/cpu/intel_cacheinfo.c | 2 +-
1 file changed, 1 insertion(+), 1
Fixes the following sparse warnings:
arch/x86/kernel/cpu/intel_cacheinfo.c:329:5: warning: symbol
'amd_get_l3_disable_slot' was not declared. Should it be static?
arch/x86/kernel/cpu/intel_cacheinfo.c:406:5: warning: symbol
'amd_set_l3_disable_slot' was not declared. Should it be static?
On Fri, Sep 25, 2015 at 04:51:28PM +0900, Inha Song wrote:
> Hi, Charles,
>
> On Thu, 24 Sep 2015 08:41:07 +0100
> Charles Keepax wrote:
>
> > On Thu, Sep 24, 2015 at 10:38:09AM +0900, Inha Song wrote:
> > > Hi, Charles,
> > >
> > > On Wed, 23 Sep 2015
On Sep 26, 2015 1:19 PM, "H. Peter Anvin" wrote:
>
> Sadly a lot of firmware is known to fail in that configuration :( That was
> very much our guest choice.
>
Why can't we map everything completely 1:1 (VA = PA) and call the
setVA thing but pass it literally the identity.
On 09/26/2015 01:54 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.2.2 release.
There are 134 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 should be
Also properly initialize numa distance table for serial nids.
Problem: Powerpc supports sparse nid numbering which could affect
1) memory footprint 2) virtualization use cases
Current solution:
The patch maps sprase chipid got fromn device tree to serail
nids.
Result before:
node 0 1 16
There is no change in the fuctionality
Signed-off-by: Raghavendra K T
---
arch/powerpc/mm/numa.c | 42 +-
1 file changed, 21 insertions(+), 21 deletions(-)
diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c
We access numa_cpu_lookup_table array directly in all the places
to read/update numa cpu lookup information. Instead use a helper
function to update.
This is helpful in changing the way numa<-->cpu mapping in single
place when needed.
This is a cosmetic change, no change in functionality.
Create arrays that maps serial nids and sparse chipids.
Note: My original idea had only two arrays of chipid to nid map. Final
code is inspired by driver/acpi/numa.c that maps a proximity node with
a logical node by Takayoshi Kochi , and thus
uses an additional chipid_map
Problem description:
Powerpc has sparse node numbering, i.e. on a 4 node system nodes are
numbered (possibly) as 0,1,16,17. At a lower level, we map the chipid
got from device tree is naturally mapped (directly) to nid.
Potential side effect of that is:
1) There are several places in kernel that
Once we have made the distinction between nid and chipid
create a 1:1 mapping between them. This makes compacting the
nids easy later.
No functionality change.
Signed-off-by: Raghavendra K T
---
arch/powerpc/mm/numa.c | 36 +---
Pass CFLAGS and LDFLAGS to the libiberty compile line to make the
detection work when using a cross compiler.
Otherwise perf fails to link even though BFD is detected.
...libbfd: [ on ]
LINK perf
libbfd.a(bfd.o): In function `bfd_errmsg':
bfd.c:(.text+0x168):
unw_word_t is uint64_t even on 32-bit MIPS. Cast it to uintptr_t before
the cast to void *p to get rid of the following errors:
util/unwind-libunwind.c: In function 'access_mem':
util/unwind-libunwind.c:464:4: error: cast to pointer from integer of different
size [-Werror=int-to-pointer-cast]
When NO_LIBUNWIND_DEBUG_FRAME=0, use the .debug_frame if the .eh_frame
doesn't contain the approprate unwind tables.
Signed-off-by: Rabin Vincent
---
tools/perf/util/unwind-libunwind.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
On Sat, Sep 26, 2015 at 06:53:47PM -0400, Paul Gortmaker wrote:
> [[PATCH v2 0/5] drivers/tty: make more bool drivers explicitly non-modular]
> On 19/08/2015 (Wed 17:48) Paul Gortmaker wrote:
>
> > [v2: drop dead module code removal from 8250_lpc18xx.c ; instead convert it
> > from bool to
On Wed, Sep 23, 2015 at 8:47 PM, Myron Stowe wrote:
snip
>
> There is a kernel boot parameter, pci=norom, that is intended to disable the
> kernel's resource assignment actions for Expansion ROMs that do not already
> have BIOS assigned address ranges. Note however, if I
On Fri, Sep 25, 2015 at 11:11:49AM +, He Kuang wrote:
SNIP
> +char *parse_events_formats_error_string(char *additional_terms)
> +{
> + char *str;
> + static const char *static_terms = "config,config1,config2,name,"
> +
On Fri, Sep 25, 2015 at 11:11:49AM +, He Kuang wrote:
> Prompt proper error message when wrong config terms is specificed for
> hw/sw type perf events. This patch makes the original error prompt
> function formats_error_string() more generic, which only outputs the
> static config terms for
Map between "system.richacl" xattrs and the in-kernel representation.
Signed-off-by: Andreas Gruenbacher
---
fs/Makefile | 2 +-
fs/richacl_xattr.c| 220 ++
fs/xattr.c| 34 +--
The Kconfig currently controlling compilation of this code is:
init/Kconfig:config TREE_RCU_TRACE
init/Kconfig: def_bool RCU_TRACE && ( TREE_RCU || PREEMPT_RCU )
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned,
Add support for the "system.richacl" xattr in nfs. The existing
"system.nfs4_acl" xattr on nfs doesn't map user and group names to uids
and gids; the "system.richacl" xattr does, and only keeps the
on-the-wire names when there is no mapping. This allows to copy
permissions across different file
Initialize xdr_stream and xdr_buf from a pages array, for encoding into
the pages.
Signed-off-by: Andreas Gruenbacher
---
include/linux/sunrpc/xdr.h | 2 ++
net/sunrpc/xdr.c | 25 +
2 files changed, 27 insertions(+)
diff --git
In the write-through case, change the acl so that owner@ is granted the
permissions set in the owner mask (to match what the permission check
algorithm grants the owner).
Signed-off-by: Andreas Gruenbacher
Reviewed-by: J. Bruce Fields
---
On 09/26/2015 01:54 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.1.9 release.
There are 159 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 should be
Firmware was not released properly if kmemdup fails.
Addresses-Coverity-Id: 1269118
Signed-off-by: Mateusz Kulikowski
---
drivers/staging/rtl8723au/hal/rtl8723a_hal_init.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Fri, Sep 25, 2015 at 02:57:14PM +, Liang, Kan wrote:
SNIP
> > >
> > > Yes, the way to store the data from perf stat is better than pure
> > > script way. I guess your patch "perf stat record" can do that, right?
> > >
> > > If so, how should we run perf record and stat in parallel? By
On Fri, Sep 25, 2015 at 11:11:51AM +, He Kuang wrote:
SNIP
>
> +static int config_term_tracepoint(struct perf_event_attr *attr,
> + struct parse_events_term *term,
> + struct parse_events_error *err)
> +{
> + switch
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
From: "Aneesh Kumar K.V"
Support the richacl permission model in ext4. The richacls are stored
in "system.richacl" xattrs. Richacls need to be enabled by tune2fs or
at file system create time.
Signed-off-by: Aneesh Kumar K.V
Cache richacls in struct inode so that this doesn't have to be done
individually in each filesystem. This is similar to POSIX ACLs.
Signed-off-by: Andreas Gruenbacher
---
fs/inode.c | 11 ++--
fs/posix_acl.c | 2 +-
fs/richacl_base.c | 4
When a new file is created, it can inherit an acl from its parent
directory; this is similar to how default acls work in POSIX (draft)
ACLs.
As with POSIX ACLs, if a file inherits an acl from its parent directory,
the intersection between the create mode and the permissions granted by
the
ACLs are considered equivalent to file modes if they only consist of
owner@, group@, and everyone@ entries, the owner@ permissions do not
depend on whether the owner is a member in the owning group, and no
inheritance flags are set. This test is used to avoid storing richacls
if the acl can be
A richacl roughly grants a requested access if the NFSv4 acl in the
richacl grants the requested permissions according to the NFSv4
permission check algorithm and the file mask that applies to the process
includes the requested permissions.
Signed-off-by: Andreas Gruenbacher
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,
Doing a chmod() sets the file mode, which includes the file permission
bits. When a file has a richacl, the permissions that the richacl
grants need to be limited to what the new file permission bits allow.
This is done by setting the file masks in the richacl to what the file
permission bits
A richacl consists of an NFSv4 acl and an owner, group, and other mask.
These three masks correspond to the owner, group, and other file
permission bits, but they contain NFSv4 permissions instead of POSIX
permissions.
Each entry in the NFSv4 acl applies to the file owner (OWNER@), the
owning
The trailing everyone@ allow ace can grant permissions to all file
classes including the owner and group class. Before we can apply the
other mask to this entry to turn it into an "other class" entry, we need
to ensure that members of the owner or group class will not lose any
permissions from
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
On file systems with richacls enabled, get and set richacls directly
instead of converting from / to posix acls.
Signed-off-by: Andreas Gruenbacher
Acked-by: J. Bruce Fields
---
fs/nfsd/acl.h | 3 +-
fs/nfsd/nfs4acl.c | 124
We need to map from POSIX permissions to NFSv4 permissions when a
chmod() is done, from NFSv4 permissions to POSIX permissions when an acl
is set (which implicitly sets the file permission bits), and from the
MAY_READ/MAY_WRITE/MAY_EXEC/MAY_APPEND flags to NFSv4 permissions when
doing an access
On 09/25/2015 11:20 PM, Ingo Molnar wrote:
> * Dave Hansen wrote:
...
>> Since follow_pte() fails for all huge
>> pages, it just falls back to pulling the protection key out of the VMA,
>> which _does_ work for huge pages.
>
> That might be true for explicit hugetlb vmas, but what
Compute upper bound owner, group, and other file masks with as few
permissions as possible without denying any permissions that the NFSv4
acl in a richacl grants.
This algorithm is used when a file inherits an acl at create time and
when an acl is set via a mechanism that does not provide file
On Fri, Sep 25, 2015 at 11:11:50AM +, He Kuang wrote:
> Adds rules for parsing tracepoint names. Change rules of tracepoint
> which derives of PE_NAMEs into tracepoint names directly, so adding
> more rules based on tracepoint names will be easier.
>
> Signed-off-by: He Kuang
On Fri, Sep 25, 2015 at 11:11:50AM +, He Kuang wrote:
> Adds rules for parsing tracepoint names. Change rules of tracepoint
> which derives of PE_NAMEs into tracepoint names directly, so adding
> more rules based on tracepoint names will be easier.
>
> Signed-off-by: He Kuang
In case of several stacked block devices, which both were inited by
blk_init_queue call, you can catch the queue stuck, if first device
in stack makes bio submit being in a flush of a plug list.
Let's consider this regular scenario taking readahead into account
(readahead.c:read_pages):
1. Start
We are a private loan company, we offer project funding. We deal mainly on
project funding for projects such as construction loans, agricultural loans,
refinery project loans, mortgage loans, debt consolidation loans, personal
loans,real estate loans etc at a 3% interest rate per annum. Contact
Richacls support the Automatic Inheritance permission propagation
mechanism as specified in NFSv4.1. Over NFS, this requires support for
the dacl attribute: compared to the acl attribute, the dacl attribute
has an additional flags field which indicates when Automatic Inheritance
is in use.
The
When converting from NFSv4 ACLs to POSIX ACLs, nfsd so far was using
struct nfs4_acl as its internal representation. This representation is a
subset of richacls, so get rid of struct nfs4_acl. Richacls even have a
more compact in-memory representation, so a few more ACL entries can
easily be
Some remote file systems like nfs may return user or group identifiers
that cannot be mapped to local uids / gids. Allow to represent such
unmapped identifiers in richacls. (We still cannot represent unmapped
owners and owning groups, however.)
In the in-memory representation, the richacl is
1 - 100 of 496 matches
Mail list logo