On Fri, Sep 21, 2018 at 10:03:09AM -0700, Linus Walleij wrote:
> Hi Greg,
>
> here are some two fixes for pin contol for v4.19.
>
> Please pull them in for the current HEAD.
>
> Yours,
> Linus Walleij
>
> The following changes since commit 7876320f88802b22d4e2daf7eb027dd14175a0f8:
>
> Linux
On Thu, Sep 13, 2018 at 2:31 PM, Rick Edgecombe
wrote:
> Create __vmalloc_node_try_addr function that tries to allocate at a specific
> address and supports caller specified behavior for whether any lazy purging
> happens if there is a collision.
>
> This new function draws from the __vmalloc_node
Quoting Doug Anderson (2018-09-21 10:40:14)
> Hi,
>
> On Fri, Sep 21, 2018 at 10:31 AM Stephen Boyd wrote:
> >
> > Quoting Ryan Case (2018-09-20 15:40:54)
> > > diff --git a/Documentation/devicetree/bindings/spi/qcom,spi-qcom-qspi.txt
> > > b/Documentation/devicetree/bindings/spi/qcom,spi-qcom-q
On Fri, 2018-09-21 at 10:39 -0700, Mark Brown wrote:
> On Fri, Sep 21, 2018 at 10:30:57AM -0700, Stephen Boyd wrote:
> > Quoting Ryan Case (2018-09-20 15:40:54)
> > > +Required properties:
> > > +- compatible: Should contain:
> > > + "qcom,sdm845-qspi"
> > Does someone have a more ge
The SDHCI standard, MMC host controller bindings and MMC core defines
card detect pin as active low. Therefore there is no point to invert it
twice.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi | 3 +--
1 file changed, 1 insertion(+), 2 deletions(
On Wed, Sep 19, 2018 at 10:41 AM Christoph Hellwig wrote:
>
> On Wed, Sep 19, 2018 at 10:32:06AM -0400, Jim Quinlan wrote:
> > +#if defined(CONFIG_ARM64)
>
> Please use plain #ifdef where possible.
>
> > +dma_addr_t __phys_to_dma(struct device *dev, phys_addr_t paddr)
> > +{
> > + return brcm_
On Fri, Sep 21, 2018 at 6:39 AM Tycho Andersen wrote:
>
> On Thu, Sep 20, 2018 at 07:18:45PM -0700, Andy Lutomirski wrote:
> >
> > I think we just want the operation to cover all the cases. Let PUT_FD
> > take a source fd and a dest fd. If the source fd is -1, the dest is
> > closed. If the sou
rong git tree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Song-Qiang/iio-magnetometer-hmc5843-Clean-up-redundant-code/20180921-091239
> base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
>
On Fri, Sep 21, 2018 at 10:59 AM Nick Desaulniers
wrote:
>
> On Fri, Sep 21, 2018 at 2:45 AM Dmitry Vyukov wrote:
> >
> > On Fri, Sep 21, 2018 at 11:25 AM, Andrey Ryabinin
> > wrote:
> > > On 09/21/2018 04:50 AM, Andy Lutomirski wrote:
> > >> This patch seems reasonable, but you emailed the wron
On Fri, Sep 21, 2018 at 11:02:41AM -0700, Lee Jones wrote:
> On Fri, 21 Sep 2018, Mark Brown wrote:
> > This looks OK to me - Lee, the patch is almost entirely a regulator one,
> > are you OK with me applying it?
> The diff in rohm-bd718x7.h does not look significant.
> You can apply it so long
On 9/20/18, 11:22 PM, "Lei YU" wrote:
> Tested on Palmetto (OpenPOWER P8 with AST2400), and it does show the fix is
> working on AST2400 as well.
> Without the patch, usleep(100) takes tens of milliseconds randomly;
> With the patch, usleep(100) takes about 600~700 microseconds stably.
>
> Teste
On 9/20/18, 8:33 PM, "Joel Stanley" wrote:
> I gave this a spin on the ast2400. It looked okay, but I was wondering
> if you could share you test case so I can run the same test?
Thank you Joel for the testing.
Sure I can share the test (a small c program which measures delay introduced by
nano
On Fri, 21 Sep 2018, Mark Brown wrote:
> On Fri, Sep 14, 2018 at 11:27:46AM +0300, Matti Vaittinen wrote:
> > BD71847 is reduced version of BD71837. DVS bucks 3 and 4 are
> > removed as is LDO7. Voltage ranges of some regulators are
> > expanded.
> >
> > Add initial support for BD71847 with BD718
On Thu, Sep 20, 2018 at 5:06 AM Jonas Gorski wrote:
>
> On 19 September 2018 at 16:31, Jim Quinlan wrote:
> > The DT bindings description of the Brcmstb PCIe device is described.
> > This node can be used by almost all Broadcom settop box chips, using
> > ARM, ARM64, or MIPS CPU architectures.
>
On Fri, Sep 21, 2018 at 2:45 AM Dmitry Vyukov wrote:
>
> On Fri, Sep 21, 2018 at 11:25 AM, Andrey Ryabinin
> wrote:
> > On 09/21/2018 04:50 AM, Andy Lutomirski wrote:
> >> This patch seems reasonable, but you emailed the wrong people :)
> >>
> >> On Thu, Sep 20, 2018 at 5:15 PM Jason A. Donenfeld
On 21/09/18 18:39, Julien Thierry wrote:
Hi,
On 28/08/18 16:51, Julien Thierry wrote:
Instead disabling interrupts by setting the PSR.I bit, use a priority
higher than the one used for interrupts to mask them via PMR.
The value chosen for PMR to enable/disable interrupts encodes the status
On Fri, Sep 21, 2018 at 10:24 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:234b69e3e089 ocfs2: fix ocfs2 read block panic
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=131f761a40
> kernel config: https://syzk
On Thu, Sep 20, 2018 at 12:02 PM Andy Gross wrote:
>
> On Wed, Sep 12, 2018 at 03:22:45PM +0530, Amit Kucheria wrote:
> > This is another series of tsens cleanups before we add interrupt support.
> > This applies on top of 4.19-rc2.
> >
> > Patches [1-6] can directly be applied by Eduardo.
> > Pa
From: Mel Gorman
migrate_task_rq_fair resets the scan rate for NUMA balancing on every
cross-node migration. In the event of excessive load balancing due to
saturation, this may result in the scan rate being pegged at maximum and
further overloading the machine.
This patch only resets the scan i
Currently task scan rate is reset when NUMA balancer migrates the task
to a different node. If NUMA balancer initiates a swap, reset is only
applicable to the task that initiates the swap. Similarly no scan rate
reset is done if the task is migrated across nodes by traditional load
balancer.
Inste
If NUMA improvement from the task migration is going to be very
minimal, then avoid task migration.
Specjbb2005 results (8 warehouses)
Higher bops are better
2 Socket - 2 Node Haswell - X86
JVMS PrevCurrent %Change
4 198512 205910 3.72673
1 313559 318491 1.57291
2 Socket - 4
Since this spinlock will only serialize the migrate rate limiting,
convert the spinlock to a trylock. If another thread is updating, this
task can move on.
Specjbb2005 results (8 warehouses)
Higher bops are better
2 Socket - 2 Node Haswell - X86
JVMS PrevCurrent %Change
4 205332 19851
This additional parameter (new_cpu) is used later for identifying if
task migration is across nodes.
No functional change.
Specjbb2005 results (8 warehouses)
Higher bops are better
2 Socket - 2 Node Haswell - X86
JVMS PrevCurrent %Change
4 203353 200668 -1.32036
1 328205 32179
This patchset provides left out patches from the previous series.
http://lore.kernel.org/lkml/1529514181-9842-1-git-send-email-sri...@linux.vnet.ibm.com
Changes from previous posting:
Rebased the patchset to 4.19-rc4.
Handled comments from Ingo Molnar,Peter Peter Zijlstra and Mel Gorman.
Reorder t
Task migration under NUMA balancing can happen in parallel. More than
one task might choose to migrate to the same CPU at the same time. This
can result in
- During task swap, choosing a task that was not part of the evaluation.
- During task swap, task which just got moved into its preferred node,
Registers have moved around across TSENS generations. For example, the
CTRL register was at offset 0x0 in the SROT region on msm8916 but is at
offset 0x4 in newer v2 based TSENS HW blocks.
Allow passing offsets of important registers so that we can continue to
use common functions.
Signed-off-by:
Hi,
Nothing special, description in tag.
Best regards,
Krzysztof
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
Hi Brendan,
nit:
Title in imperative mood. I'd put 'fix' instead of 'fixed'.
On 9/20/2018 4:28 PM, Brendan Higgins wrote:
The function that computes clock parameters from divisors did not
respect the maximum size of the bitfields that the parameters were
written to. This fixes the bug.
This bu
On Tue, Sep 11, 2018 at 01:36:07PM +0800, Aaron Lu wrote:
> Daniel Jordan and others proposed an innovative technique to make
> multiple threads concurrently use list_del() at any position of the
> list and list_add() at head position of the list without taking a lock
> in this year's MM summit[0].
Hi,
Nothing special, description in tag.
Best regards,
Krzysztof
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
On 09/21/2018 12:14 PM, Tim Chen wrote:
> On 09/21/2018 08:44 AM, Lendacky, Thomas wrote:
>
>
>> +if (static_cpu_has(X86_FEATURE_SSBD))
>> +x86_spec_ctrl_base |= ssbd_tif_to_spec_ctrl(tifn);
>> +
>> +x86_spec_ctrl_base |= stibp_tif_to_spec_ctrl(tifn);
>>
>> wrmsrl(MSR
On Thu, Sep 20, 2018 at 5:39 PM Florian Fainelli wrote:
>
> On 09/20/2018 02:33 PM, Ard Biesheuvel wrote:
> > On 20 September 2018 at 14:31, Florian Fainelli
> > wrote:
> >> On 09/20/2018 02:04 PM, Ard Biesheuvel wrote:
> >>> On 20 September 2018 at 13:55, Florian Fainelli
> >>> wrote:
>
Hi,
On Fri, Sep 21, 2018 at 10:31 AM Stephen Boyd wrote:
>
> Quoting Ryan Case (2018-09-20 15:40:54)
> > diff --git a/Documentation/devicetree/bindings/spi/qcom,spi-qcom-qspi.txt
> > b/Documentation/devicetree/bindings/spi/qcom,spi-qcom-qspi.txt
> > new file mode 100644
> > index ..e
Hi,
On 28/08/18 16:51, Julien Thierry wrote:
Instead disabling interrupts by setting the PSR.I bit, use a priority
higher than the one used for interrupts to mask them via PMR.
The value chosen for PMR to enable/disable interrupts encodes the status
of interrupts on a single bit. This informati
On Fri, Sep 21, 2018 at 10:30:57AM -0700, Stephen Boyd wrote:
> Quoting Ryan Case (2018-09-20 15:40:54)
> > +Required properties:
> > +- compatible: Should contain:
> > + "qcom,sdm845-qspi"
> Does someone have a more generic compatible string that can be added
> here to indicate th
Clang warns when multiple pairs of parentheses are used for a single
conditional statement.
drivers/staging/rtl8188eu/core/rtw_pwrctrl.c:295:21: warning: equality
comparison with extraneous parentheses [-Wparentheses-equality]
if ((pwrpriv->rpwm == pslv)) {
~~^
Quoting Ryan Case (2018-09-20 15:40:54)
> diff --git a/Documentation/devicetree/bindings/spi/qcom,spi-qcom-qspi.txt
> b/Documentation/devicetree/bindings/spi/qcom,spi-qcom-qspi.txt
> new file mode 100644
> index ..ecfb1e2bd520
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/s
On Fri, Sep 14, 2018 at 11:27:46AM +0300, Matti Vaittinen wrote:
> BD71847 is reduced version of BD71837. DVS bucks 3 and 4 are
> removed as is LDO7. Voltage ranges of some regulators are
> expanded.
>
> Add initial support for BD71847 with BD71837 driver.
>
> Signed-off-by: Matti Vaittinen
> --
With Due Respect,
I know that this mail will come to you as a surprise as we have never met
before, but need not to worry as I am contacting you independently of my
investigation and no one is informed of this communication. I need your urgent
assistance in transferring the sum of $11.3milli
On Thu, Sep 20, 2018 at 4:31 PM Nathan Chancellor
wrote:
>
> Clang warns when one enumerated type is converted implicitly to another:
>
> drivers/mtd/nand/raw/sh_flctl.c:483:46: warning: implicit conversion
> from enumeration type 'enum dma_transfer_direction' to different
> enumeration type 'enum
The member regd of the struct rtl_priv is true in a boolean context.
drivers/staging/rtlwifi/regd.c:413:27: warning: address of 'rtlpriv->regd' will
always
evaluate to 'true' [-Wpointer-bool-conversion]
if (!wiphy || !&rtlpriv->regd)
~ ~^~~~
1 warning g
Hello,
syzbot found the following crash on:
HEAD commit:234b69e3e089 ocfs2: fix ocfs2 read block panic
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=131f761a40
kernel config: https://syzkaller.appspot.com/x/.config?x=5fa12be50bca08d8
dashboard link:
Hello,
syzbot found the following crash on:
HEAD commit:46c163a036b4 Add linux-next specific files for 20180921
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17e32b9e40
kernel config: https://syzkaller.appspot.com/x/.config?x=20ea07a946ad19d7
Hello,
syzbot found the following crash on:
HEAD commit:74ee2200b89f kmsan: bump .config.example to v4.17-rc3
git tree: https://github.com/google/kmsan.git/master
console output: https://syzkaller.appspot.com/x/log.txt?x=1164f19780
kernel config: https://syzkaller.appspot.com/x/.c
On 09/21/2018 08:44 AM, Lendacky, Thomas wrote:
> + if (static_cpu_has(X86_FEATURE_SSBD))
> + x86_spec_ctrl_base |= ssbd_tif_to_spec_ctrl(tifn);
> +
> + x86_spec_ctrl_base |= stibp_tif_to_spec_ctrl(tifn);
>
> wrmsrl(MSR_IA32_SPEC_CTRL, msr);
> }
>
Should this part
Hi Greg,
here are some two fixes for pin contol for v4.19.
Please pull them in for the current HEAD.
Yours,
Linus Walleij
The following changes since commit 7876320f88802b22d4e2daf7eb027dd14175a0f8:
Linux 4.19-rc4 (2018-09-16 11:52:37 -0700)
are available in the Git repository at:
git://
From: Yi Sun Sent: Friday, September 21, 2018 12:25
AM
> +
> +#define pr_fmt(fmt) "hv: " fmt
Other Hyper-V messages use "Hyper-V: " as the prefix, not "hv: ". Take
a quick look at 'dmesg' output for reference.
> +
> +#include
> +#include
> +#include
> +#include
> +#include
Some of these
On Wed, 2018-08-15 at 18:29 -0700, Florian Fainelli wrote:
>
> On 08/14/2018 07:16 AM, Joe Perches wrote:
> > On Tue, 2018-08-14 at 16:06 +0200, Marcel Ziswiler wrote:
> > > From: Marcel Ziswiler
> > >
> > > Dynamic debug is really helpful.
> >
> > It's useful, but perhaps not appropriate.
> >
On Fri, Sep 21, 2018 at 3:00 AM Nathan Chancellor
wrote:
>
> Clang warns that the address of a pointer will always evaluated as true
> in a boolean context.
>
> drivers/media/platform/pxa_camera.c:2400:17: warning: address of
> 'pdev->dev.of_node' will always evaluate to 'true'
> [-Wpointer-bool-c
On Thu, Sep 20, 2018 at 03:45:52PM +0300, Alexander Shishkin wrote:
> This adds a helper to paste 2 pointer arrays together, useful for merging
> various types of attribute arrays. There are a few places in the kernel
> tree where this is open coded, and I just added one more in the STM class.
>
>
Christian Brauner wrote:
> So from reading the patch I got the impression that superblock mount
> options passed via fsconfig() are passed as strings like "ro" and are
> translated into approriate objects (e.g. flags etc.) by the kernel.
I'm having second throughts about that - at least for "ro"
From: Yi Sun Sent: Friday, September 21, 2018 12:25
AM
>
> Hyper-V may expose a HV_X64_MSR_GUEST_IDLE MSR. We can read
> HYPERV_CPUID_FEATURES eax to check it. Read this MSR can
> trigger the guest's transition to the idle power state which
> can be exited by an IPI even if IF flag is disabled.
Dear Maintainers,
On 9/20/2018 7:11 AM, Peter Zijlstra wrote:
> On Wed, Sep 19, 2018 at 10:29:05AM -0700, Reinette Chatre wrote:
>> Reinette Chatre (6):
>> perf/core: Add sanity check to deal with pinned event failure
>> perf/x86: Add helper to obtain performance counter index
>> x86/intel_r
On 9/21/2018 12:45 PM, Matthias Kaehlcke wrote:
Well, there is a generic binding
(https://elixir.bootlin.com/linux/v4.18/source/Documentation/devicetree/bindings/net/bluetooth.txt),
the fact that there are drivers that aren't adhering to it doesn't
change that.
OK. If there is some soft of a "s
On Mon, Sep 10, 2018 at 05:50:21PM +0800, honghui.zh...@mediatek.com wrote:
> From: Honghui Zhang
>
> The clocks was not enabled when enable MSI. This patch fix this
> issue by calling mtk_pcie_enable_msi in mtk_pcie_startup_port_v2
> since the clock was all enabled at that time.
>
> The functio
On Fri, Sep 21, 2018 at 01:25:45AM -0400, Sinan Kaya wrote:
> On 9/20/2018 7:19 PM, Matthias Kaehlcke wrote:
> > If the existing users populate a custom property with the BD address
> > in the bootloader you could roll out a bootloader change. You'd have
> > to make sure that bootloader and kernel
Hi Miklós,
I've reposted my patches with some of your changes folded in. I will consider
the other things, but I don't have time to do that before Monday. I think I
should also have a go at porting fuse so that we can get the subtype bits
done.
Note that I have a perl script that does some of
Hi Sakari,
On Fri, Sep 21, 2018 at 10:13:12AM +0300, Sakari Ailus wrote:
> Hi Matthias,
>
> On Thu, Sep 20, 2018 at 03:34:35PM -0700, Matthias Kaehlcke wrote:
> > Provide an API for Bluetooth drivers to retrieve the Bluetooth Device
> > address (BD_ADDR) for a device. If the device node has a pro
On Wed, Sep 12, 2018 at 06:11:49PM -0600, Logan Gunthorpe wrote:
> Add a restructured text file describing how to write drivers
> with support for P2P DMA transactions. The document describes
> how to use the APIs that were added in the previous few
> commits.
>
> Also adds an index for the PCI do
On 09/17/2018 07:29 AM, Thomas Gleixner wrote:
> The whole static protection magic is silently fixing up anything which is
> handed in. That's just wrong. The offending call sites need to be fixed.
>
> Add a debug mechanism which emits a warning if a requested mapping needs to be
> fixed up. The D
Implement parameter value retrieval with fsinfo() - akin to parsing
/proc/mounts.
This allows the values of each parameter to be retrieved in an order
corresponding to the Nth index used by FSINFO_ATTR_PARAM_SPECIFICATION. If
a parameter isn't set, an empty string is returned. Parameters may hav
Add fsinfo support to the AFS filesystem.
Signed-off-by: David Howells
---
fs/afs/super.c | 129
1 file changed, 129 insertions(+)
diff --git a/fs/afs/super.c b/fs/afs/super.c
index 944985e0a3c8..1fe5026b1104 100644
--- a/fs/afs/super.c
Allow fsinfo() to be used to query the filesystem attached to an fs_context
once a superblock has been created or if it comes from fspick().
This is done with something like:
fd = fsopen("ext4", 0);
...
fsconfig(fd, fsconfig_cmd_create, ...);
fsinfo(fd, NULL, ...);
Provide fsinfo() attributes that can be used to query a filesystem
parameter description. To do this, fsinfo() can be called on an
fs_context that doesn't yet have a superblock created and attached.
It can be obtained by doing, for example:
fd = fsopen("ext4", 0);
struct fsinfo_
Add a system call to allow filesystem information to be queried. A request
value can be given to indicate the desired attribute. Support is provided
for enumerating multi-value attributes.
===
NEW SYSTEM CALL
===
The new system call looks like:
int ret = fsinfo(
Hi Al,
Here are a set of patches that adds a syscall, fsinfo(), that allows
attributes of a filesystem/superblock to be queried. Attributes are of two
basic types: fixed-length structure and variable-length string. Attributes
can also have multiple values in up to two dimensions.
Note that th
On 09/17/2018 07:29 AM, Thomas Gleixner wrote:
> Checking static protections only page by page is slow especially for huge
> pages. To allow quick checks over a complete range, add the ability to do
> that.
>
> Make the checks inclusive so the ranges can be directly used for debug output
> later.
Add a sample program to demonstrate fsopen/fsmount/move_mount to mount
something.
Signed-off-by: David Howells
---
samples/Kconfig| 10 +-
samples/Makefile |2
samples/statx/Makefile |7 -
samples/statx/test-statx.c | 258 ---
Add fs_context support to the AFS filesystem, converting the parameter
parsing to store options there.
This will form the basis for namespace propagation over mountpoints within
the AFS model, thereby allowing AFS to be used in containers more easily.
Signed-off-by: David Howells
---
fs/afs/in
Alter the AFS automounting code to create and modify an fs_context struct
when parameterising a new mount triggered by an AFS mountpoint rather than
constructing device name and option strings.
Also remove the cell=, vol= and rwpath options as they are then redundant.
The reason they existed is be
Provide a system call by which a filesystem opened with fsopen() and
configured by a series of fsconfig() calls can have a detached mount object
created for it. This mount object can then be attached to the VFS mount
hierarchy using move_mount() by passing the returned file descriptor as the
from
Provide an fspick() system call that can be used to pick an existing
mountpoint into an fs_context which can thereafter be used to reconfigure a
superblock (equivalent of the superblock side of -o remount).
This looks like:
int fd = fspick(AT_FDCWD, "/mnt",
FSPICK_
Add a syscall for configuring a filesystem creation context and triggering
actions upon it, to be used in conjunction with fsopen, fspick and fsmount.
long fsconfig(int fs_fd, unsigned int cmd, const char *key,
const void *value, int aux);
Where fs_fd indicates the context,
Add some logging to the core users of the fs_context log so that
information can be extracted from them as to the reason for failure.
Signed-off-by: David Howells
---
fs/super.c|4 +++-
kernel/cgroup/cgroup-v1.c |2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
di
Ahem...
Of course, the linux community, like ALL communities, needs more
political correctness, because we wouldn't want others to feel left
out merely because they are wrong. FALSE || TRUE = more
participation and diversity!
>Our Pledge
>In the interest of fostering an open and welcoming envir
On 09/17/2018 07:29 AM, Thomas Gleixner wrote:
> +/*
> + * The kernel text needs to be executable for obvious reasons. This does
> + * not cover __inittext since that is gone after boot. On 64bit we do not
> + * enforce !NX on the low mapping
> + */
> +static pgprotval_t protect_kernel_text(unsigne
Implement the ability for filesystems to log error, warning and
informational messages through the fs_context. These can be extracted by
userspace by reading from an fd created by fsopen().
Error messages are prefixed with "e ", warnings with "w " and informational
messages with "i ".
Inside the
Make the anon_inodes facility unconditional so that it can be used by core
VFS code.
Signed-off-by: David Howells
---
arch/arm/kvm/Kconfig |1 -
arch/arm64/kvm/Kconfig |1 -
arch/mips/kvm/Kconfig |1 -
arch/powerpc/kvm/Kconfig |1 -
arch/s390/kvm/Kconfig |
Provide an fsopen() system call that starts the process of preparing to
create a superblock that will then be mountable, 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, unsigned int flags);
where flags
Provide documentation for the new mount API.
Signed-off-by: David Howells
---
Documentation/filesystems/mount_api.txt | 741 +++
1 file changed, 741 insertions(+)
create mode 100644 Documentation/filesystems/mount_api.txt
diff --git a/Documentation/filesystems/mou
Convert the hugetlbfs to use the fs_context during mount.
Signed-off-by: David Howells
---
fs/hugetlbfs/inode.c | 391 +-
1 file changed, 230 insertions(+), 161 deletions(-)
diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
index 4fa2e644
The kern_mount_data() isn't used any more so remove it.
Signed-off-by: David Howells
---
fs/namespace.c |7 ---
include/linux/fs.h |1 -
2 files changed, 8 deletions(-)
diff --git a/fs/namespace.c b/fs/namespace.c
index d841ba5568d9..156261d03c12 100644
--- a/fs/namespace.c
+++
Make kernfs support superblock creation/mount/remount with fs_context.
This requires that sysfs, cgroup and intel_rdt, which are built on kernfs,
be made to support fs_context also.
Notes:
(1) A kernfs_fs_context struct is created to wrap fs_context and the
kernfs mount parameters are move
Convert the mqueue filesystem to use the filesystem context stuff.
Notes:
(1) The relevant ipc namespace is selected in when the context is
initialised (and it defaults to the current task's ipc namespace).
The caller can override this before calling vfs_get_tree().
(2) Rather than s
Make the cpuset filesystem use the filesystem context. This is potentially
tricky as the cpuset fs is almost an alias for the cgroup filesystem, but
with some special parameters.
This can, however, be handled by setting up an appropriate cgroup
filesystem and returning the root directory of that
Separate just the changing of mount flags (MS_REMOUNT|MS_BIND) from full
remount because the mount data will get parsed with the new fs_context
stuff prior to doing a remount - and this causes the syscall to fail under
some circumstances.
To quote Eric's explanation:
[...] mount(..., MS_REMOUNT
Implement a filesystem context concept to be used during superblock
creation for mount and superblock reconfiguration for remount.
The mounting procedure then becomes:
(1) Allocate new fs_context context.
(2) Configure the context.
(3) Create superblock.
(4) Query the superblock.
(5) Cre
Remove code that is now unused after the filesystem context changes.
Signed-off-by: David Howells
---
fs/internal.h |2 -
fs/super.c | 62 --
include/linux/lsm_hooks.h | 12 -
include/linux/security.h | 13 -
security/sec
Add fs_context support to procfs.
Signed-off-by: David Howells
---
fs/proc/inode.c|1
fs/proc/internal.h |1
fs/proc/root.c | 220
3 files changed, 151 insertions(+), 71 deletions(-)
diff --git a/fs/proc/inode.c b/fs/proc/
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| 49 +
fs/proc/internal.h |4 +---
fs/proc/root.c | 48 +++
On Thu, Sep 20, 2018 at 03:40:55PM -0700, Ryan Case wrote:
> +static int qcom_qspi_setup(struct spi_device *spi)
> +{
> + /*
> + * Ensure that the configuration goes through by reading back
> + * a register from the IO space.
> + */
> + mstr_cfg = readl(ctrl->base + MSTR_CO
Implement the security hook to check the creation of a new mountpoint for
Tomoyo.
As far as I can tell, Tomoyo doesn't make use of the mount data or parse
any mount options, so I haven't implemented any of the fs_context hooks for
it.
Signed-off-by: David Howells
cc: Tetsuo Handa
cc: tomoyo-dev
Implement hooks to check the creation of new mountpoints for AppArmor.
Unfortunately, the DFA evaluation puts the option data in last, after the
details of the mountpoint, so we have to cache the mount options in the
fs_context using those hooks till we get to the new mountpoint hook.
Signed-off-
Implement filesystem context security hooks for the smack LSM.
Question: Should the ->fs_context_parse_source() hook be implemented to
check the labels on any source devices specified?
Signed-off-by: David Howells
cc: Casey Schaufler
cc: linux-security-mod...@vger.kernel.org
---
security/smac
Because the new API passes in key,value parameters, match_token() cannot be
used with it. Instead, provide three new helpers to aid with parsing:
(1) fs_parse(). This takes a parameter and a simple static description of
all the parameters and maps the key name to an ID. It returns 1 on a
Put security flags, such as SECURITY_LSM_NATIVE_LABELS, into the filesystem
context so that the filesystem can communicate them to the LSM more easily.
Signed-off-by: David Howells
---
include/linux/fs_context.h |1 +
include/linux/security.h |2 +-
2 files changed, 2 insertions(+), 1
Add LSM hooks for use by the new mount API and filesystem context code.
This includes:
(1) Hooks to handle allocation, duplication and freeing of the security
record attached to a filesystem context.
(2) A hook to snoop source specifications. There may be multiple of these
if the fil
Introduce a set of logging functions through which informational messages,
warnings and error messages incurred by the mount procedure can be logged
and, in a future patch, passed to userspace instead by way of the
filesystem configuration context file descriptor.
There are four functions:
(1) i
Only the mount namespace code that implements mount(2) should be using the
MS_* flags. Suppress them inside the kernel unless uapi/linux/mount.h is
included.
Signed-off-by: David Howells
---
arch/arc/kernel/setup.c |1 +
arch/arm/kernel/atags_parse.c |1 +
arch/sh/kernel/setup.c
From: Al Viro
open_tree(dfd, pathname, flags)
Returns an O_PATH-opened file descriptor or an error.
dfd and pathname specify the location to open, in usual
fashion (see e.g. fstatat(2)). flags should be an OR of
some of the following:
* AT_PATH_EMPTY, AT_NO_AUTOMOUNT, AT_SYMLINK_NOFOLLO
201 - 300 of 649 matches
Mail list logo
