Create a function, vfs_get_block_super(), that is fs_context-aware and a
replacement for mount_bdev(). It caches the block device pointer and file
open mode in the fs_context struct so that this information can be passed
into sget_fc()'s test and set functions.
Signed-off-by: David Howells
cc:
Convert the smackfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
On Wed, Mar 06, 2019 at 04:03:17PM -0800, Bjorn Andersson wrote:
> The SDM845 Audio DSP peripheral image loader binding describes the
> properties needed to load and boot firmware on a Hexagon v56. Rename the
> file and add the Compute DSP (CDSP) found in QCS404 to the binding.
>
> Signed-off-by:
Convert the squashfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Kill mount_mtd() as it has now been replaced by vfs_get_mtd_super() in the
new mount API and nothing now uses it.
Signed-off-by: David Howells
cc: David Woodhouse
cc: Brian Norris
cc: Boris Brezillon
cc: Marek Vasut
cc: Richard Weinberger
cc: linux-...@lists.infradead.org
---
Convert the jffs2 filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
On Thu, 7 Mar 2019 03:40:57 +, Anson Huang wrote:
> Add IMX8MQ_CLK_HDMI_PHY_27M clock for i.MX8MQ clock tree.
>
> Signed-off-by: Anson Huang
> ---
> include/dt-bindings/clock/imx8mq-clock.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring
Provide a function, vfs_get_mtd_super(), to replace mount_mtd(), using an
fs_context struct to hold the parameters. The mtd device pointer is cached
in the struct, along with a destructor pointer as the mtd core may be in a
module and, as such, unreachable by the core code that would release the
Convert the openpromfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the apparmorfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the gadgetfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the ibmasmfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the xenfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the qib_fs/ipathfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the oprofilefs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the configfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Kill sget_userns(), folding it into sget() as that's the only remaining
user.
Signed-off-by: David Howells
cc: linux-fsde...@vger.kernel.org
---
fs/super.c | 61 +---
include/linux/fs.h |5
2 files changed, 20 insertions(+), 46
Convert the binfmt_misc filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the fusectl filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the rpc_pipefs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Kill mount_ns() as it has been replaced by vfs_get_super() in the new mount
API.
Signed-off-by: David Howells
cc: linux-fsde...@vger.kernel.org
---
fs/super.c | 44
include/linux/fs.h |3 ---
2 files changed, 47 deletions(-)
diff
On Wed, 6 Mar 2019 15:22:20 -0800, Bjorn Andersson wrote:
> The qcom,adsp binding document has evolved to cover the mechanism to
> load and boot firmware on a range of different Hexagon based remote
> subsystems. Rename the binding and update the description to better
> capture this.
>
>
Convert the binderfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the nfsctl filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Kill off mount_pseudo() and mount_pseudo_xattr() as they're replaced with
vfs_init_pseudo_fs_context().
Signed-off-by: David Howells
cc: linux-fsde...@vger.kernel.org
---
fs/libfs.c | 53
include/linux/fs.h | 13 -
2
Signed-off-by: David Howells
cc: linux-fsde...@vger.kernel.org
---
fs/libfs.c | 25 +++--
1 file changed, 11 insertions(+), 14 deletions(-)
diff --git a/fs/libfs.c b/fs/libfs.c
index 9a15590b65da..f6710316de00 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -242,18 +242,12 @@
Convert the virtio_balloon filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the btrfs_test filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the ia64 perfmon filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the ocxlflash filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the cxl filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the drm filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the pipe filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the nsfs filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the zsmalloc filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the anon_inodes filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the bdev filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Convert the aio filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Provide a field in the fs_context struct through which bits in the
sb->s_iflags superblock field can be set.
Signed-off-by: David Howells
cc: linux-fsde...@vger.kernel.org
---
fs/super.c |1 +
include/linux/fs_context.h |1 +
2 files changed, 2 insertions(+)
diff --git
Update the mount API docs to reflect recent changes to the code.
Signed-off-by: David Howells
---
Documentation/filesystems/mount_api.txt | 367 ---
1 file changed, 195 insertions(+), 172 deletions(-)
diff --git a/Documentation/filesystems/mount_api.txt
Provide a function, vfs_init_pseudo_fs_context(), that provides a common
infrastructure for converting pseudo-filesystems that can never be
mountable.
Signed-off-by: David Howells
cc: linux-fsde...@vger.kernel.org
---
fs/libfs.c | 93
From: Masahiro Yamada
Commit 2b50f7ab6368 ("kbuild: add workaround for Debian make-kpkg")
annoyed people who want to wrap the top Makefile with GNUmakefile
or something in order to customize it for their use.
On second thought, we do not need to run the sub-make for in-tree
build with Make 4.x
Fix an overput in which filename_lookup() unconditionally drops a ref to
the filename it was given, but this isn't taken account of in the caller,
fs_lookup_param().
Addresses-Coverity-ID: 1443811 ("Use after free")
Signed-off-by: David Howells
---
fs/fs_parser.c |1 +
1 file changed, 1
On Wed, 6 Mar 2019 09:47:56 -0800, Bjorn Andersson wrote:
> Add devicetree binding for the turing clock controller found in QCS404.
>
> Signed-off-by: Bjorn Andersson
> ---
> .../bindings/clock/qcom,turingcc.txt | 19 +++
> .../dt-bindings/clock/qcom,turingcc-qcs404.h
On Tue, Mar 05, 2019 at 09:51:48PM -0800, Bjorn Andersson wrote:
> Add the clocks and resets need in order to control the Turing
> remoteproc.
>
> Signed-off-by: Bjorn Andersson
> ---
> drivers/clk/qcom/gcc-qcs404.c | 90 +
>
On Tue, Mar 05, 2019 at 03:24:03PM +0100, Fabien Dessenne wrote:
> Add the device tree bindings document for the stm32 remoteproc devices.
>
> Signed-off-by: Fabien Dessenne
> ---
> .../devicetree/bindings/remoteproc/stm32-rproc.txt | 67
> ++
> 1 file changed, 67
On 3/27/2019 3:55 PM, Randy Dunlap wrote:
On 3/27/19 3:23 PM, Casey Schaufler wrote:
On 3/27/2019 3:05 PM, Tetsuo Handa wrote:
On 2019/03/28 6:43, Kees Cook wrote:
I don't see problems for an exclusive LSM user (AA, SELinux, Smack)
also initializing TOMOYO, though. It should be a no-op. Is
Hi,
On Wed, Mar 27, 2019 at 4:08 PM Chong Qiao wrote:
>
> KGDB_call_nmi_hook is called by other cpu through smp call.
> MIPS smp call is processed in ipi irq handler and regs is saved in
> handle_int.
> So kgdb_call_nmi_hook get regs by get_irq_regs and regs will be passed
> to kgdb_cpu_enter.
On Thu, 28 Mar 2019 02:12:15 +0300
"Dmitry V. Levin" wrote:
> > Seriously. If we keep it can we at least remove all the unused arguments
> > which we have on both functions to simplify the whole mess?
>
> In case of syscall_set_arguments() I think we can safely remove
> "i" and "n" arguments
Hi Doug,
I have changed name and signoff info format and resent patch just now.
Thanks a lot.
在 2019-03-28 06:27:26，"Doug Anderson" 写道：
>Hi,
>
>On Wed, Mar 27, 2019 at 3:25 PM qiaochong wrote:
>>
>>
>> My name is QiaoChong， which is same to my username.
>> Qiao is my family name.
>> Thanks
On Wed, Mar 27, 2019 at 11:52:19PM +0100, Thomas Gleixner wrote:
> On Thu, 28 Mar 2019, Dmitry V. Levin wrote:
> > On Wed, Mar 27, 2019 at 03:29:16PM +0100, Thomas Gleixner wrote:
> > > On Wed, 27 Mar 2019, Dmitry V. Levin wrote:
> > > > On Tue, Mar 26, 2019 at 04:12:45PM +0100, Oleg Nesterov
KGDB_call_nmi_hook is called by other cpu through smp call.
MIPS smp call is processed in ipi irq handler and regs is saved in
handle_int.
So kgdb_call_nmi_hook get regs by get_irq_regs and regs will be passed
to kgdb_cpu_enter.
Signed-off-by: Chong Qiao
---
arch/mips/kernel/kgdb.c | 3 ++-
1
On Tue, Mar 05, 2019 at 03:24:02PM +0100, Fabien Dessenne wrote:
> Document the ML-AHB interconnect for stm32 SoCs.
>
> Signed-off-by: Fabien Dessenne
> ---
> .../devicetree/bindings/arm/stm32/mlahb.txt| 30
> ++
> 1 file changed, 30 insertions(+)
> create mode
On Wed, 27 Mar 2019 23:52:19 +0100 (CET)
Thomas Gleixner wrote:
> > Could we delay the removal of syscall_set_arguments() until
> > PTRACE_GET_SYSCALL_INFO is merged into the kernel?
> > I hope it won't take another 11 years.
>
> Hope dies last :)
>
> Seriously. If we keep it can we at
On Wed, Mar 20, 2019 at 06:49:35PM +, Suzuki K Poulose wrote:
> So far we have hard coded the DT platform parsing code in
> every driver. Introduce generic helper to parse the information
> provided by the firmware in a platform agnostic manner, in preparation
> for the ACPI support.
>
> Cc:
On 3/27/19 3:23 PM, Casey Schaufler wrote:
> On 3/27/2019 3:05 PM, Tetsuo Handa wrote:
>> On 2019/03/28 6:43, Kees Cook wrote:
> I don't see problems for an exclusive LSM user (AA, SELinux, Smack)
> also initializing TOMOYO, though. It should be a no-op. Is there some
> situation where
Update the mount API docs to reflect recent changes to the code.
Signed-off-by: David Howells
---
Documentation/filesystems/mount_api.txt | 367 ---
1 file changed, 195 insertions(+), 172 deletions(-)
diff --git a/Documentation/filesystems/mount_api.txt
Hi Linus,
Could you apply the associated patch? It updates the document describing
the mount API to make it better reflect the API now in the kernel.
Thanks,
David
---
David Howells (1):
vfs: Update mount API docs
Documentation/filesystems/mount_api.txt | 367
On Thu, 28 Mar 2019, Dmitry V. Levin wrote:
> On Wed, Mar 27, 2019 at 03:29:16PM +0100, Thomas Gleixner wrote:
> > On Wed, 27 Mar 2019, Dmitry V. Levin wrote:
> > > On Tue, Mar 26, 2019 at 04:12:45PM +0100, Oleg Nesterov wrote:
> > > > On 03/23, Thomas Gleixner wrote:
> > > [...]
> > > > > 2)
Hi Randy,
On Wed, 27 Mar 2019 13:32:26 -0700 Randy Dunlap wrote:
>
> on i386 or x86_64:
>
> WARNING: unmet direct dependencies detected for MFD_SUN6I_PRCM
> Depends on [n]: HAS_IOMEM [=y] && ARCH_SUNXI
> Selected by [y]:
> - CLK_SUNXI_PRCM_SUN8I [=y] && COMMON_CLK [=y] && CLK_SUNXI [=y]
On Wed, Mar 27, 2019 at 01:27:12PM -0700, Matthew Wilcox wrote:
> On Wed, Mar 27, 2019 at 01:10:01PM -0700, syzbot wrote:
> > syzbot has bisected this bug to:
> >
> > commit b9b8a41adeff5666b402996020b698504c927353
> > Author: Dan Carpenter
> > Date: Mon Aug 20 08:25:33 2018 +
> >
> >
On Wed, 27 Mar 2019, Andi Kleen wrote:
> > > I checked the code general and with the .globl in NATIVE_LABEL the
> >
> > With or without? I removed that as well.
>
> With.
>
> LTO would still need the .globls because the variable and the asm
> statement can end up in different assembler files,
The marshalling of AFS.StoreData, AFS.StoreData64 and YFS.StoreData64 calls
generated by ->setattr() ops for the purpose of expanding a file is
incorrect due to older documentation incorrectly describing the way the RPC
'FileLength' parameter is meant to work.
The older documentation says that
> > + /* flush TX/RX FIFOs */
> > + val = (BIT(S_FIFO_RX_FLUSH_SHIFT) | BIT(S_FIFO_TX_FLUSH_SHIFT));
> > + writel(val, iproc_i2c->base + S_FIFO_CTRL_OFFSET);
>
> Will flushing FIFOs work when a slave is register while a master
> transfer is on-going at the same time?
Sorry, my bad, this
Fix checkpatch error "ERROR: space required before the open brace
'{'" in ieee80211_wx.c.
Signed-off-by: Julius Hemanth Pitti
---
Changes in v2:
- Corrected commit message typo
drivers/staging/rtl8192u/ieee80211/ieee80211_wx.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
On Wed, Mar 27, 2019 at 02:53:35PM -0700, Julius Hemanth Pitti wrote:
> Fix checkpatch error "ERROR: that open brace { should be on
> the previous line" in ieee80211_wx.c.
>
> Signed-off-by: Julius Hemanth Pitti
> ---
> drivers/staging/rtl8192u/ieee80211/ieee80211_wx.c | 12 +---
> 1
Free the priv structure only after we are done using it.
Fixes: 1690d8bb91e370ab ("cpufreq: scpi/scmi: Fix freeing of dynamic OPPs")
Signed-off-by: Vincent Stehlé
Cc: Sudeep Holla
Cc: "Rafael J. Wysocki"
Cc: Viresh Kumar
---
drivers/cpufreq/scpi-cpufreq.c | 2 +-
1 file changed, 1
On Fri, Mar 22, 2019 at 11:15 AM Roman Gushchin wrote:
>
> On Thu, Mar 07, 2019 at 08:56:32AM -0800, Greg Thelen wrote:
> > Since commit a983b5ebee57 ("mm: memcontrol: fix excessive complexity in
> > memory.stat reporting") memcg dirty and writeback counters are managed
> > as:
> > 1) per-memcg
> > I checked the code general and with the .globl in NATIVE_LABEL the
>
> With or without? I removed that as well.
With.
LTO would still need the .globls because the variable and the asm
statement can end up in different assembler files, and resolution
would rely on the linker.
-Andi
Hi,
On Wed, Mar 27, 2019 at 3:25 PM qiaochong wrote:
>
>
> My name is QiaoChong， which is same to my username.
> Qiao is my family name.
> Thanks a lot.
I guess it will be up to whichever maintainer lands this (maybe
Daniel?) on whether they want you to spin it. I think folks expect to
see a
On Thu, Feb 14, 2019 at 09:57:17AM -0800, Ray Jui wrote:
> This patch series adds the following support to the iProc I2C driver:
> - Increase maximum read transfer size to 255 bytes
> - I2C slave mode
> - Polling mode
> - NIC I2C mode
>
> This patch series is based on kernel v5.0-rc3 and
> procfd_open(int procrootfd, int pidfd, unsigned int flags);
> pidfd_open(pid_t pid, int nsfd, unsigned int flags);
That honestly just feels like splitting openat into:
openat_dir()
and
opentat_file()
My name is QiaoChong， which is same to my username.
Qiao is my family name.
Thanks a lot.
在 2019-03-28 00:25:06，"Doug Anderson" 写道：
>Hi,
>
>On Wed, Mar 27, 2019 at 8:06 AM qiaochong wrote:
>>
>> KGDB_call_nmi_hook is called by other cpu through smp call.
>> MIPS smp call is processed in ipi
> Update iProc I2C binding document to add new compatible string
> "brcm,iproc-nic-i2c". Optional property "brcm,ape-hsls-addr-mask" is
> also added that allows configuration of the host view into the APE's
> address for "brcm,iproc-nic-i2c"
I don't know the platform, but wouldn't it be more
On 3/27/2019 3:05 PM, Tetsuo Handa wrote:
On 2019/03/28 6:43, Kees Cook wrote:
I don't see problems for an exclusive LSM user (AA, SELinux, Smack)
also initializing TOMOYO, though. It should be a no-op. Is there some
situation where this is not true?
There should be no problem except some
On Wed, Mar 27, 2019 at 03:29:16PM +0100, Thomas Gleixner wrote:
> On Wed, 27 Mar 2019, Dmitry V. Levin wrote:
> > On Tue, Mar 26, 2019 at 04:12:45PM +0100, Oleg Nesterov wrote:
> > > On 03/23, Thomas Gleixner wrote:
> > [...]
> > > > 2) syscall_set_arguments() has been introduced in 2008 and we
This adds a simple test case for pidfd_open().
Signed-off-by: Christian Brauner
Cc: Arnd Bergmann
Cc: "Eric W. Biederman"
Cc: Kees Cook
Cc: Alexey Dobriyan
Cc: Thomas Gleixner
Cc: Jann Horn
Cc: "Michael Kerrisk (man-pages)"
Cc: Konstantin Khlebnikov
Cc: Jonathan Kowalski
Cc: "Dmitry V.
From: David Howells
Make the anon_inodes facility unconditional so that it can be used by core
VFS code and the pidfd_open() syscall.
Signed-off-by: David Howells
Signed-off-by: Al Viro
[christ...@brauner.io: adapt commit message to mention pidfd_open()]
Signed-off-by: Christian Brauner
---
Let pidfd_send_signal() use pidfds retrieved via pidfd_open(). With this
patch pidfd_send_signal() becomes independent of procfs. This fullfils the
request made when we merged the pidfd_send_signal() patchset. The
pidfd_send_signal() syscall is now always available allowing for it to be
used by
pidfd_open() allows to retrieve pidfds for processes and removes the
dependency of pidfd on procfs. Multiple people have expressed a desire to
do this even when pidfd_send_signal() was merged. It is even recorded in
the commit message for pidfd_send_signal() itself
(cf. commit
Hey,
This is v1 of this patchset. No major changes. Just fixing nits that
Jann detected.
After the discussion over the last days, this is a fresh approach to
getting pidfds independent of the translate_pid() patchset.
pidfd_open() allows to retrieve pidfds for processes and removes the
> + if (!((readl(iproc_i2c->base +
> + M_FIFO_CTRL_OFFSET) >>
> + M_FIFO_RX_CNT_SHIFT) &
> + M_FIFO_RX_CNT_MASK))
Don't be too strict with the 80 char limit. I think the above is hardly
readable...
> + break;
> +
> +
> +static void bcm_iproc_i2c_slave_init(
> + struct bcm_iproc_i2c_dev *iproc_i2c, bool need_reset)
> +{
> + u32 val;
> +
> + if (need_reset) {
> + /* put controller in reset */
> + val = readl(iproc_i2c->base + CFG_OFFSET);
> + val |=
On Wed, Mar 27, 2019 at 9:34 PM Christian Brauner wrote:
>
> On Wed, Mar 27, 2019 at 07:38:13PM +, Jonathan Kowalski wrote:
> > Christian,
> >
> > Giving this some thought, it looks fine to me, but I am not convinced
> > this should take a pid argument. I much prefer if obtaining a pidfd
>
>
On 2019/03/28 6:43, Kees Cook wrote:
>>> I don't see problems for an exclusive LSM user (AA, SELinux, Smack)
>>> also initializing TOMOYO, though. It should be a no-op. Is there some
>>> situation where this is not true?
>>
>> There should be no problem except some TOMOYO messages are printed.
>
On Sun, Mar 24, 2019 at 03:29:04PM +0100, Thomas Gleixner wrote:
>Wei,
>
>On Tue, 12 Feb 2019, Wei Yang wrote:
>>
>> This patch changes the implementation from the first perception to the
>> second to reduce one different handling on end_pfn. After doing so, the
>> code is easier to read.
>
>It's
On Wed, Mar 20, 2019 at 06:49:32PM +, Suzuki K Poulose wrote:
> As we are about to about refactor the platform specific handling,
s/about//
> move the DT property handling to generic helpers.
>
> Cc: Mathieu Poirier
> Signed-off-by: Suzuki K Poulose
> ---
>
On Wed, 27 Mar 2019, Andi Kleen wrote:
> >
> > It's static so it's scope is within the file and whatever GCC does with
> > that C function it has to respect that it accesses static data. If that's
> > not true then this really needs to be fixed at the compiler side and not in
> > the kernel.
>
>
Fix checkpatch error "ERROR: that open brace { should be on
the previous line" in ieee80211_wx.c.
Signed-off-by: Julius Hemanth Pitti
---
drivers/staging/rtl8192u/ieee80211/ieee80211_wx.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git
On 3/27/19 10:31 PM, Rasmus Villemoes wrote:
On 27/03/2019 22.20, Jacek Anaszewski wrote:
Thanks for the heads-up. I must admit I'm hitting into that for the
first time. After "git am" it was all OK, but it got screwed up after
"git rebase -i". And having "commit.cleanup = scissors" set
On Wed, Mar 27, 2019 at 2:05 PM Tetsuo Handa
wrote:
>
> On 2019/03/28 5:45, Kees Cook wrote:
> > On Wed, Mar 27, 2019 at 1:30 PM Tetsuo Handa
> > wrote:
> >>
> >> On 2019/03/28 4:16, Kees Cook wrote:
> >>> The part I don't understand is what you've said about TOMOYO being
> >>> primary and not
On Wed, Mar 20, 2019 at 06:49:30PM +, Suzuki K Poulose wrote:
> Track the coresight device instead of the real device.
>
> Cc: Mathieu Poirier
> Signed-off-by: Suzuki K Poulose
> ---
> drivers/hwtracing/coresight/coresight-etb10.c | 6 +++---
> 1 file changed, 3 insertions(+), 3
On Wed, Mar 27, 2019 at 11:44:37AM -0700, Paul E. McKenney wrote:
> On Wed, Mar 27, 2019 at 01:45:45PM -0400, Joel Fernandes wrote:
> > On Wed, Mar 27, 2019 at 08:53:51AM -0700, Paul E. McKenney wrote:
> > > On Wed, Mar 27, 2019 at 11:34:01AM -0400, Joel Fernandes wrote:
> > > > On Tue, Mar 26,
Use the 2nd software bit in the PTE as the devmap bit and add the
appropriate accessors.
This also allows us to set ARCH_HAS_ZONE_DEVICE.
Signed-off-by: Logan Gunthorpe
Cc: Palmer Dabbelt
Cc: Albert Ou
Cc: Laurent Dufour
Cc: Mike Rapoport
Cc: Anup Patel
Cc: Zong Li
Cc: Guo Ren
Cc:
Hi,
This patchset enables P2P on the RISC-V architecture. To do this on the
current kernel, we only need to be able to back IO memory with struct
pages using devm_memremap_pages(). This requires ARCH_HAS_ZONE_DEVICE,
ARCH_ENABLE_MEMORY_HOTPLUG, and ARCH_ENABLE_MEMORY_HOTREMOVE; which in
turn
In order to define ARCH_ENABLE_MEMORY_HOTPLUG we need to implement
arch_add_memory() and vmemmap_free().
arch_add_memory() is very similar to the x86 versions except we
don't need to fuss with the mapping as we've already mapped the
entire linear region in riscv.
For now, vmemmap_free() is empty
The motivation for this is to support P2P transactions. P2P requires
having struct pages for IO memory which means the linear mapping must
be able to cover all of the IO regions. Unfortunately with Sv39 we are
not able to cover all the IO regions available on existing hardware,
but we can do
With the new virtual address changes in an earlier patch, we want the
page tables to cover more of the linear mapping region. Instead of
only mapping from PAGE_OFFSET and up, we instead map starting
from an aligned version of va_pa_offset such that all of the physical
address space will be mapped.
This file is similar to the x86_64 equivalent (in
Documentation/x86/x86_64/mm.txt) and describes the virtuas address space
usage for RISC-V.
Signed-off-by: Logan Gunthorpe
Cc: Jonathan Corbet
Cc: Palmer Dabbelt
Cc: Albert Ou
---
Documentation/riscv/mm.txt | 24
1
This patch implements sparsemem support for risc-v which helps pave the
way for memory hotplug and eventually P2P support.
We introduce Kconfig options for virtual and physical address bits which
are used to calculate the size of the vmemmap and set the
MAX_PHYSMEM_BITS.
The vmemmap is located
101 - 200 of 1290 matches
Mail list logo
