On Thu, Apr 30, 2020 at 09:46:13AM +0530, Gautham R Shenoy wrote:
> Hello Michael,
> > >
> > > Michael, could you please consider this for 5.8 ?
> >
> > Yes. Has it been tested on KVM at all?
>
> No. I haven't tested this on KVM. Will do that today.
The results on Shared LPAR and KVM are as
On 1/5/20 5:07 am, Eric W. Biederman wrote:
Linus Torvalds writes:
On Thu, Apr 30, 2020 at 7:10 AM Greg Ungerer wrote:
Most of that file goes back to pre-git days. And most of the commits
since are not so much about binfmt_flat, as they are about cleanups or
changes elsewhere where
On Sat, Apr 18, 2020 at 3:06 AM Masahiro Yamada wrote:
>
> Since commit a83e4ca26af8 ("kbuild: remove cc-option switch from
> -Wframe-larger-than="), 'make ARCH=um clean' emits an error message
> as follows:
>
> $ make ARCH=um clean
> gcc: error: missing argument to '-Wframe-larger-than='
>
>
On Mon, Apr 27, 2020 at 5:06 PM Will Deacon wrote:
>
> On Mon, Apr 27, 2020 at 09:30:19AM +0900, Masahiro Yamada wrote:
> > $(AS) is not used anywhere, hence commit aa824e0c962b ("kbuild: remove
> > AS variable") killed it.
> >
> > Remove the left-over code in arch/{arm,arm64}/Makefile.
> >
> >
On Sat, Apr 25, 2020 at 10:18 PM Masahiro Yamada wrote:
>
> This notice has been here for a while. Remove it entirely now.
>
> Signed-off-by: Masahiro Yamada
> ---
>
Applied to linux-kbuild.
> Makefile | 4
> 1 file changed, 4 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index
On Mon, Apr 27, 2020 at 11:13 PM Masahiro Yamada wrote:
>
> cmd_dtc takes the additional parameter $(2) to select the target
> format, dtb or yaml. This makes things complicated when it is used
> with cmd_and_fixdep and if_changed_rule. I actually stumbled on this.
> See commit 3d4b2238684a
In the case of kdump, the PCI device was not cleanly shut down
before the kdump kernel starts. This causes the initial
attempt of entering D0 state in the kdump kernel to fail with
invalid device state returned from Hyper-V host.
When this happens, explicitly call PCI bus exit and retry to
enter
On Sat, Apr 25, 2020 at 2:47 PM Masahiro Yamada wrote:
>
> 'make ARCH=parisc clean' emits a tons of error messages as follows:
>
> $ make ARCH=parisc clean
> gcc: error: unrecognized command line option '-mno-space-regs'
> gcc: error: unrecognized command line option
Some error cases in hv_pci_probe() were not handled. Fix these error
paths to release the resourses and clean up the state properly.
Signed-off-by: Wei Hu
---
drivers/pci/controller/pci-hyperv.c | 20
1 file changed, 16 insertions(+), 4 deletions(-)
diff --git
On Sat, Apr 25, 2020 at 3:07 PM Masahiro Yamada wrote:
>
> Since commit a83e4ca26af8 ("kbuild: remove cc-option switch from
> -Wframe-larger-than="), 'make ARCH=unicore32 clean' emits error
> messages as follows:
>
> $ make ARCH=unicore32 clean
> gcc: error: missing argument to
On Sat, Apr 25, 2020 at 2:18 PM Masahiro Yamada wrote:
>
> 'make ARCH=h8300 clean' emits error messages as follows:
>
> $ make ARCH=h8300 clean
> gcc: error: missing argument to '-Wframe-larger-than='
> gcc: error: unrecognized command line option '-mint32'
>
> You can suppress the second
This series better handles some PCI HyperV error cases in general and
for kdump case. Some of review comments from previous individual
patch reviews, including splitting into separate patches, have
already been incorporated.
Thanks,
Wei
Wei Hu (2):
PCI: hv: Fix the PCI HyperV probe failure
On Thu, Apr 23, 2020 at 11:24 PM Masahiro Yamada wrote:
>
> The result of '$(CC) --version | head -n 1' is already computed by the
> top Makefile, and stored in the environment variable, CC_VERSION_TEXT.
>
> 'echo' is probably less expensive than the two commands $(CC) and
> 'head' although this
On Sat, Apr 25, 2020 at 4:06 AM Brian Cain wrote:
>
> > -Original Message-
> > From: linux-hexagon-ow...@vger.kernel.org > ow...@vger.kernel.org> On Behalf Of Masahiro Yamada
> ...
> > 'make ARCH=hexagon clean' emits an error message as follows:
> >
> > $ make ARCH=hexagon clean
> >
On Thu, Apr 30, 2020 at 11:47:33PM -0500, Josh Poimboeuf wrote:
> On Thu, Apr 30, 2020 at 08:21:47PM -0400, Steven Rostedt wrote:
> > The cause is the "ftrace=function" would register the function tracer
> > and create a trampoline, and it will set it as executable and
> > read-only. Then the
On Thu, Apr 30, 2020 at 9:06 PM Masahiro Yamada wrote:
>
> Hi Alexei,
>
> On Wed, Apr 29, 2020 at 1:14 AM Alexei Starovoitov
> wrote:
> > >
> > > At least, the build was successful,
> > > but does this work at runtime?
> > >
> > > If this is a bug, I can fix it cleanly.
> > >
> > > I think the
On 2020-05-01 09:50, Bart Van Assche wrote:
On 2020-04-30 18:42, Can Guo wrote:
On 2020-05-01 04:32, Bart Van Assche wrote:
> Has it been considered to test directly whether a SCSI device has been
> runtime suspended instead of relying on blk_queue_pm_only()? How about
> using
On Thu, Apr 30, 2020 at 08:21:47PM -0400, Steven Rostedt wrote:
> The cause is the "ftrace=function" would register the function tracer
> and create a trampoline, and it will set it as executable and
> read-only. Then the "trace_options=func_stack_trace" would then update
> the same trampoline to
Ning Bo reported an abnormal 2-second gap when booting Kata container [1].
The unconditional timeout was caused by VSOCK_DEFAULT_CONNECT_TIMEOUT of
connecting from the client side. The vhost vsock client tries to connect
an initializing virtio vsock server.
The abnormal flow looks like:
Add new subcommands to kunit.py to allow stages of the existing 'run'
subcommand to be run independently:
- 'config': Verifies that .config is a subset of .kunitconfig
- 'build': Compiles a UML kernel for KUnit
- 'exec': Runs the kernel, and outputs the test results.
- 'parse': Parses test results
On Tue, 28 Apr 2020, Mickaël Salaün wrote:
> Enable to either propagate the mount options from the underlying VFS
> mount to prevent execution, or to propagate the file execute permission.
> This may allow a script interpreter to check execution permissions
> before reading commands from a file.
On 4/30/20 10:14 PM, Jens Axboe wrote:
> On 4/30/20 9:58 PM, Al Viro wrote:
>> On Thu, Apr 30, 2020 at 10:24:46AM -0600, Jens Axboe wrote:
>>> Pipe read/write only checks for the file O_NONBLOCK flag, but we should
>>> also check for IOCB_NOWAIT for whether or not we should handle this read
>>> or
On Thu, 30 Apr 2020 22:26:55 -0400 (EDT)
Mathieu Desnoyers wrote:
> The tracers just have to make sure they perform their vmalloc'd memory
> allocation before registering the tracepoint which can touch it, else they
> need to issue vmalloc_sync_mappings() on their own before making the
> newly
Stephen,
On 4/30/20 22:30, Gustavo A. R. Silva wrote:
>> This is now a conflict between the net-next and kspp-gustavo trees.
>>
>
> Thanks for reporting this. I think the best solution, for now, is to remove
> the
> changes from my tree. I'll do it right away.
>
I just updated my -next tree.
On 4/30/20 9:58 PM, Al Viro wrote:
> On Thu, Apr 30, 2020 at 10:24:46AM -0600, Jens Axboe wrote:
>> Pipe read/write only checks for the file O_NONBLOCK flag, but we should
>> also check for IOCB_NOWAIT for whether or not we should handle this read
>> or write in a non-blocking fashion. If we
Hi Bernard,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pza/reset/next]
[also build test ERROR on drm-intel/for-linux-next drm-tip/drm-tip linus/master
v5.7-rc3 next-20200430]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve
Hi Alexei,
On Wed, Apr 29, 2020 at 1:14 AM Alexei Starovoitov
wrote:
> >
> > At least, the build was successful,
> > but does this work at runtime?
> >
> > If this is a bug, I can fix it cleanly.
> >
> > I think the bit size of the user mode helper
> > should match to the kernel bit size. Is
On Tue, 28 Apr 2020, Mickaël Salaün wrote:
> When the RESOLVE_MAYEXEC flag is passed, openat2(2) may be subject to
> additional restrictions depending on a security policy managed by the
> kernel through a sysctl or implemented by an LSM thanks to the
> inode_permission hook.
Reviewed-by: James
Hi all,
After merging the sound tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
sound/pci/hda/patch_realtek.c: In function 'alc_fixup_hp_gpio_led':
sound/pci/hda/patch_realtek.c:4134:6: warning: unused variable 'err'
[-Wunused-variable]
4134 | int err;
|
On Tue, 28 Apr 2020, Mickaël Salaün wrote:
> An LSM doesn't get path information related to an access request to open
> an inode. This new (internal) MAY_EXECMOUNT flag enables an LSM to
> check if the underlying mount point of an inode is marked as executable.
> This is useful to implement a
On Wed, Apr 29, 2020 at 06:24:06PM +1000, Stephen Rothwell wrote:
> Hi Christoph,
>
> On Wed, 29 Apr 2020 08:54:04 +0200 Christoph Hellwig wrote:
> >
> > On Tue, Apr 28, 2020 at 11:49:34PM -0700, Alexei Starovoitov wrote:
> > > On Tue, Apr 28, 2020 at 11:47 PM Christoph Hellwig wrote:
> > > >
From: Zou Wei
Date: Wed, 29 Apr 2020 11:35:28 +0800
> Fixes coccicheck warnings:
>
> drivers/net/ethernet/huawei/hinic/hinic_hw_mbox.c:452:17-24: WARNING
> opportunity for kmemdup
> drivers/net/ethernet/huawei/hinic/hinic_hw_mbox.c:458:23-30: WARNING
> opportunity for kmemdup
>
>
On Thu, Apr 30, 2020 at 10:24:46AM -0600, Jens Axboe wrote:
> Pipe read/write only checks for the file O_NONBLOCK flag, but we should
> also check for IOCB_NOWAIT for whether or not we should handle this read
> or write in a non-blocking fashion. If we don't, then we will block on
> data or space
On Thu, Apr 30, 2020 at 07:40:52AM -0700, Randy Dunlap wrote:
> On 4/30/20 7:31 AM, Randy Dunlap wrote:
> > On 4/30/20 12:40 AM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Changes since 20200429:
> >>
> >
> > on x86_64:
> >
> > kernel/exit.o: warning: objtool: __x64_sys_exit_group()+0x2e:
From: Michael Walle
Date: Wed, 29 Apr 2020 01:06:58 +0200
> The lower three bits of the phy_id specifies the chip stepping. The
> workaround is specifically for the B0 stepping. Apply it only on these
> chips.
>
> Signed-off-by: Michael Walle
> Reviewed-by: Andrew Lunn
> Reviewed-by: Florian
From: Michael Walle
Date: Wed, 29 Apr 2020 01:06:59 +0200
> This PHY has two PHY IDs depending on its mode. Adjust the mask so that
> it includes both IDs.
>
> Signed-off-by: Michael Walle
Applied.
On Wed, Apr 29, 2020 at 08:28:25PM -0400, vincent.cheng...@renesas.com wrote:
> @@ -871,6 +880,69 @@ static int idtcm_set_pll_mode(struct idtcm_channel
> *channel,
>
> /* PTP Hardware Clock interface */
>
> +/**
> + * @brief Maximum absolute value for write phase offset in picoseconds
> + *
From: Michael Walle
Date: Wed, 29 Apr 2020 01:06:57 +0200
> Broadcom defines the bits for this PHY as follows:
> { oui[24:3], model[6:0], revision[2:0] }
>
> Thus we have to mask the lower three bits only.
>
> Fixes: 6937602ed3f9 ("net: phy: add Broadcom BCM54140 support")
> Signed-off-by:
From: Michael Walle
Date: Wed, 29 Apr 2020 01:06:56 +0200
> Set the .soft_reset() op to be sure there will be a reset even if there
> is no hardware reset line registered.
>
> Signed-off-by: Michael Walle
> Reviewed-by: Florian Fainelli
Applied.
From: Michael Walle
Date: Tue, 28 Apr 2020 23:15:02 +0200
> The AR8031 and AR8035 support the link speed downshift. Add driver
> support for it. One peculiarity of these PHYs is that it needs a
> software reset after changing the setting, thus add the .soft_reset()
> op and do a phy_init_hw() if
On Tue, 28 Apr 2020, Mickaël Salaün wrote:
> Furthermore, the security policy can also be delegated to an LSM, either
> a MAC system or an integrity system. For instance, the new kernel
> MAY_OPENEXEC flag closes a major IMA measurement/appraisal interpreter
> integrity gap by bringing the
On Tue, 28 Apr 2020, Stefan Hajnoczi wrote:
> On Tue, Apr 14, 2020 at 04:49:45PM +0100, Stefan Hajnoczi wrote:
> > Document the purpose of CAP_SETFCAP. For some reason this capability
> > had no description while the others did.
> >
> > Signed-off-by: Stefan Hajnoczi
> > ---
> >
On Sat, 2020-04-25 at 11:49 +1000, Balbir Singh wrote:
> On Fri, 2020-04-24 at 13:59 -0500, Tom Lendacky wrote:
> >
> > On 4/23/20 9:01 AM, Balbir Singh wrote:
> > > Split out the allocation and free routines to be used in a follow
> > > up set of patches (to reuse for L1D flushing).
> > >
> > >
On Thu, 30 Apr 2020, KP Singh wrote:
> From: KP Singh
>
Applied to:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
for-v5.7
--
James Morris
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
include/linux/dma-buf.h
between commit:
6f49c2515e22 ("dma-buf: fix documentation build warnings")
from the drm-misc-fixes tree and commit:
09606b5446c2 ("dma-buf: add peer2peer flag")
from the drm tree.
I fixed it
On Wed, Apr 29, 2020 at 08:28:24PM -0400, vincent.cheng...@renesas.com wrote:
> From: Vincent Cheng
>
> Add adjust_phase to ptp_clock_caps capability to allow
> user to query if a PHC driver supports adjust phase with
> ioctl PTP_CLOCK_GETCAPS command.
>
> Signed-off-by: Vincent Cheng
On Wed, Apr 29, 2020 at 08:28:23PM -0400, vincent.cheng...@renesas.com wrote:
> diff --git a/drivers/ptp/ptp_clock.c b/drivers/ptp/ptp_clock.c
> index acabbe7..c46ff98 100644
> --- a/drivers/ptp/ptp_clock.c
> +++ b/drivers/ptp/ptp_clock.c
> @@ -146,6 +146,8 @@ static int ptp_clock_adjtime(struct
On Fri, May 1, 2020 at 4:25 AM Mauro Carvalho Chehab
wrote:
>
> A new behavior on more recent kernels require to always call
> "make modules_prepare" after *any* Kconfig changes.
Again, this is the behavior since 2004.
This commit:
From: Aishwarya Ramakrishnan
Date: Mon, 27 Apr 2020 16:02:30 +0530
> Fixes coccicheck warning:
> ./drivers/net/ethernet/freescale/dpaa/dpaa_eth.c:2110:30-31:
> WARNING comparing pointer to 0
>
> Avoid pointer type value compared to 0.
>
> Signed-off-by: Aishwarya Ramakrishnan
Applied,
Hi Stephen,
On 4/30/20 22:12, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 29 Apr 2020 12:06:25 +1000 Stephen Rothwell
> wrote:
>>
>> Today's linux-next merge of the mlx5-next tree got a conflict in:
>>
>> include/linux/mlx5/mlx5_ifc.h
>>
>> between commit:
>>
>> 3ba225b506a2 ("treewide:
From: Christophe JAILLET
Date: Sun, 26 Apr 2020 22:59:21 +0200
> Should an irq requested with 'devm_request_irq' be released explicitly,
> it should be done by 'devm_free_irq()', not 'free_irq()'.
>
> Fixes: 6c821bd9edc9 ("net: Add MOXA ART SoCs ethernet driver")
> Signed-off-by: Christophe
Hi Prashant,
I do not think it is present. Thinking about it, I do not think it
shall be an issue on any released device as it will have either a
firmware which wouldn't even trigger the typec probe or the one after
the hierarchy fix. Likely I just got a firmware which was somewhere in
between
On Fri, May 01, 2020 at 03:37:34AM +0100, Al Viro wrote:
> On Thu, Apr 30, 2020 at 01:38:44PM -0700, ira.we...@intel.com wrote:
>
> > -static inline void *kmap_atomic(struct page *page)
> > +static inline void *kmap_atomic_prot(struct page *page, pgprot_t prot)
> > {
> > preempt_disable();
>
A Powerpc system with multiple possible nodes and with CONFIG_NUMA
enabled always used to have a node 0, even if node 0 does not any cpus
or memory attached to it. As per PAPR, node affinity of a cpu is only
available once its present / online. For all cpus that are possible but
not present,
Hi all,
On Wed, 29 Apr 2020 12:06:25 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the mlx5-next tree got a conflict in:
>
> include/linux/mlx5/mlx5_ifc.h
>
> between commit:
>
> 3ba225b506a2 ("treewide: Replace zero-length array with flexible-array
> member")
>
> from
Node id queried from the static device tree may not
be correct. For example: it may always show 0 on a shared processor.
Hence prefer the node id queried from vphn and fallback on the device tree
based node id if vphn query fails.
Cc: linuxppc-...@lists.ozlabs.org
Cc: linux...@kvack.org
Cc:
Changelog v2:->v3:
- Resolved comments from Gautham.
Link v2:
https://lore.kernel.org/linuxppc-dev/20200428093836.27190-1-sri...@linux.vnet.ibm.com/t/#u
Changelog v1:->v2:
- Rebased to v5.7-rc3
- Updated the changelog.
Link v1:
Currently Linux kernel with CONFIG_NUMA on a system with multiple
possible nodes, marks node 0 as online at boot. However in practice,
there are systems which have node 0 as memoryless and cpuless.
This can cause numa_balancing to be enabled on systems with only one node
with memory and CPUs.
We report a bug (in linux-5.6.8) found by FuzzUSB (a modified version
of syzkaller).
This happened when the size of "name" buffer is smaller than that of
"page" buffer
(after function kstrdup executed at line 263).
I guess it comes from the "page" buffer containing 0 value in the middle.
So
Hi William,
I love your patch! Yet something to improve:
[auto build test ERROR on stm32/stm32-next]
[cannot apply to linus/master linux/master v5.7-rc3 next-20200430]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use
Hi Linus,
Regular scheduled fixes pull for graphics. Nothing to extreme bunch of
amdgpu fixes, i915 and qxl fixes, along with some misc ones.
All seems to be progressing normally.
Dave.
drm-fixes-2020-05-01:
drm fixes for 5.7-rc4
core:
- EDID off by one DTD fix
- DP mst write return code fix
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.6.7, v5.4.35, v4.19.118, v4.14.177,
v4.9.220, v4.4.220.
v5.6.7: Build OK!
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlxsw/spectrum_span.c
between commit:
3ba225b506a2 ("treewide: Replace zero-length array with flexible-array
member")
from the kspp-gustavo tree and commit:
4780dbdbd957 ("mlxsw:
On Thu, Apr 30, 2020 at 06:09:35PM -0700, Josh Triplett wrote:
> On Thu, Apr 30, 2020 at 04:11:18PM -0400, Daniel Jordan wrote:
> > Sometimes the kernel doesn't take full advantage of system memory
> > bandwidth, leading to a single CPU spending excessive time in
> > initialization paths where the
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/steering/dr_send.c
between commit:
8075411d93b6 ("net/mlx5: DR, On creation set CQ's arm_db member to right
value")
from the net tree and commit:
73a75b96fc9a ("net/mlx5:
Hi Alex,
On Thu, Apr 30, 2020 at 02:43:28PM -0700, Alexander Duyck wrote:
> On 4/30/2020 1:11 PM, Daniel Jordan wrote:
> > padata will soon divide up pfn ranges between threads when parallelizing
> > deferred init, and deferred_init_maxorder() complicates that by using an
> > opaque index in
On Thu, Apr 30, 2020 at 05:40:59PM -0400, Pavel Tatashin wrote:
> On Thu, Apr 30, 2020 at 5:31 PM Andrew Morton
> wrote:
> > On Thu, 30 Apr 2020 16:11:18 -0400 Daniel Jordan
> > wrote:
> >
> > > Sometimes the kernel doesn't take full advantage of system memory
> > > bandwidth, leading to a
On Thu, 30 Apr 2020, Arnd Bergmann wrote:
> Building ehci drivers with gcc-10 results in a number of warnings like
> when an zero-length array is accessed:
>
> drivers/usb/host/ehci-hub.c: In function 'ehci_bus_suspend':
> drivers/usb/host/ehci-hub.c:320:30: error: array subscript 14 is outside
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
include/net/mptcp.h
between commit:
cfde141ea3fa ("mptcp: move option parsing into mptcp_incoming_options()")
from the net tree and commit:
071c8ed6e88d ("tcp: mptcp: use mptcp receive buffer space to select rcv
On Thu, 30 Apr 2020 22:26:55 -0400 (EDT)
Mathieu Desnoyers wrote:
> - On Apr 30, 2020, at 9:13 PM, rostedt rost...@goodmis.org wrote:
>
> > [ Joerg, sending again this time not just to you. (hit reply to sender
> > and not reply to all). Feel free to resend what you wrote before to this ]
>> On Tue, Apr 14, 2020 at 03:13:40PM +0200, Christoph Hellwig wrote:
>> > The pgprot argument to __vmalloc is always PROT_KERNEL now, so remove
>> > it.
Greetings;
I recently noticed this change via the linux-next tree.
It may not be possible to edit at this late date, but the change
On Thu, Apr 30, 2020 at 01:38:44PM -0700, ira.we...@intel.com wrote:
> -static inline void *kmap_atomic(struct page *page)
> +static inline void *kmap_atomic_prot(struct page *page, pgprot_t prot)
> {
> preempt_disable();
> pagefault_disable();
> if (!PageHighMem(page))
>
Sometimes it is useful to preserve batches of configs when making
localmodconfig. For example, I usually don't want any usb and fs
modules to be disabled. Now we can do it by:
$ make LOCALMODCONFIG_PRESERVE="drivers/usb;fs" localmodconfig
Signed-off-by: Changbin Du
---
On Fri, May 1, 2020 at 4:10 AM Mauro Carvalho Chehab
wrote:
>
> Em Fri, 1 May 2020 02:20:13 +0900
> Masahiro Yamada escreveu:
>
> > On Fri, May 1, 2020 at 1:49 AM Mauro Carvalho Chehab
> > wrote:
> > >
> > > Em Thu, 30 Apr 2020 22:51:48 +0900
> > > Masahiro Yamada escreveu:
> > >
> > > > Hi
ira.we...@intel.com writes:
> From: Ira Weiny
>
> The kmap infrastructure has been copied almost verbatim to every architecture.
> This series consolidates obvious duplicated code by defining core functions
> which call into the architectures only when needed.
>
> Some of the k[un]map_atomic()
- On Apr 30, 2020, at 9:13 PM, rostedt rost...@goodmis.org wrote:
> [ Joerg, sending again this time not just to you. (hit reply to sender
> and not reply to all). Feel free to resend what you wrote before to this ]
>
> On Thu, 30 Apr 2020 21:14:34 +0200
> Joerg Roedel wrote:
>
>> And
On 2020-04-30 12:01, Souptick Joarder wrote:
Document path Documentation/vm/pin_user_pages.rst is not a correct
reference and it should be Documentation/core-api/pin_user_pages.rst.
Signed-off-by: Souptick Joarder
---
mm/gup.c | 18 +-
1 file changed, 9 insertions(+), 9
On Thu, Apr 30, 2020 at 01:38:43PM -0700, ira.we...@intel.com wrote:
> From: Ira Weiny
>
> To support kmap_atomic_prot() on all architectures each arch must
> support protections passed in to them.
>
> Change csky, mips, nds32 and xtensa to use their global kmap_prot value
> rather than a hard
Four minor fixes: three in drivers and one in the core. The core one
allows an additional state change that fixes a regression introduced by
an update to the aacraid driver in the previous merge window.
The patch is available here:
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git
When available, use the cpu_id field from __rseq_abi on Linux to
implement sched_getcpu(). Fall-back on the vgetcpu vDSO if unavailable.
Benchmarks:
x86-64: Intel E5-2630 v3@2.40GHz, 16-core, hyperthreading
glibc sched_getcpu(): 13.7 ns (baseline)
glibc sched_getcpu() using
Register rseq TLS for each thread (including main), and unregister for
each thread (excluding main). "rseq" stands for Restartable Sequences.
See the rseq(2) man page proposed here:
https://lkml.org/lkml/2018/9/19/647
Those are based on glibc master branch commit 6f0baacf0f89.
The rseq system
On Fri, May 1, 2020 at 10:04 AM Shakeel Butt wrote:
>
> On Thu, Apr 30, 2020 at 6:39 PM Yafang Shao wrote:
> >
> > On Fri, May 1, 2020 at 2:27 AM Shakeel Butt wrote:
> > >
> > > Lowering memory.max can trigger an oom-kill if the reclaim does not
> > > succeed. However if oom-killer does not
Thank you sir for your guidance and quick response.
Let me introduce my colleagues Paul and Mikhail here (copied in CC). They would
be taking actions based on your guidance in this email and may reach you with
further queries.
Appreciate your support and help.
Thanks,
Atul
-Original
On Thu, Apr 30, 2020 at 01:38:40PM -0700, ira.we...@intel.com wrote:
> From: Ira Weiny
>
> Every arch has the same code to ensure atomic operations and a check for
> !HIGHMEM page.
>
> Remove the duplicate code by defining a core kmap_atomic() which only
> calls the arch specific
On 2020/5/1 上午9:05, Stephen Rothwell wrote:
> Hi all,
>
> On Fri, 1 May 2020 10:24:53 +1000 Stephen Rothwell
> wrote:
>>
>> Today's linux-next merge of the btrfs tree got a conflict in:
>>
>> fs/btrfs/transaction.c
>>
>> between commit:
>>
>> fcc99734d1d4 ("btrfs: transaction: Avoid
On Thu, Apr 30, 2020 at 6:39 PM Yafang Shao wrote:
>
> On Fri, May 1, 2020 at 2:27 AM Shakeel Butt wrote:
> >
> > Lowering memory.max can trigger an oom-kill if the reclaim does not
> > succeed. However if oom-killer does not find a process for killing, it
> > dumps a lot of warnings.
> >
>
> I
This patch adds an optimization that uses the asr immediate instruction
for BPF_ALU BPF_ARSH BPF_K, rather than loading the immediate to
a temporary register. This is similar to existing code for handling
BPF_ALU BPF_{LSH,RSH} BPF_K. This optimization saves two instructions
and is more consistent
This patch optimizes the code generated by emit_a32_arsh_r64, which
handles the BPF_ALU64 BPF_ARSH BPF_X instruction.
The original code uses a conditional B followed by an unconditional ORR.
The optimization saves one instruction by removing the B instruction
and using a conditional ORR (with an
As Daniel suggested to us, we ran our formal verification tool, Serval,
over the arm JIT. The bugs we found have been patched and applied to the
bpf tree [1, 2]. This patch series introduces two small optimizations
that simplify the JIT and use fewer instructions.
[1]
On Tue, 28 Apr 2020 23:36:27 +0200
Jiri Olsa wrote:
> On Fri, Apr 17, 2020 at 04:38:10PM +0900, Masami Hiramatsu wrote:
>
> SNIP
>
> > >
> > > The code within the kretprobe handler checks for probe reentrancy,
> > > so we won't trigger any _raw_spin_lock_irqsave probe in there.
> > >
> > >
Hi,
On Wed, 29 Apr 2020 17:50:44 +0800
Po-Hsu Lin wrote:
> When the required module for the test does not exist, use
> exit_unsupported instead of exit_unresolved to indicate this test is
> not supported.
Hmm, this doesn't mean "the function is not supported" but
"we can not resolve this
__swap_entry_free() always free 1 entry, let's remove the usage.
Signed-off-by: Wei Yang
---
mm/swapfile.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/mm/swapfile.c b/mm/swapfile.c
index f73e0c11fab9..1a877d1d40e3 100644
--- a/mm/swapfile.c
+++ b/mm/swapfile.c
When the condition is true, there are two possibilities:
1. count == SWAP_MAP_BAD
2. count == (SWAP_MAP_MAX & COUNT_CONTINUED) == SWAP_MAP_SHMEM
The first case would be filtered by the first if in __swap_duplicate().
And the second case means this swap entry is for shmem. Since we never
swap_info_struct->swap_map[] encodes some flag and count. And to
do some condition check, it also introduces some special values.
Currently those macros are defined with some magic order, which makes
audience hard to understand the exact meaning.
This patch split those macros into three
On 2020-04-30 18:42, Can Guo wrote:
> On 2020-05-01 04:32, Bart Van Assche wrote:
> > Has it been considered to test directly whether a SCSI device has been
> > runtime suspended instead of relying on blk_queue_pm_only()? How about
> > using pm_runtime_status_suspended() or adding a function in
>
On Fri, May 01, 2020 at 02:42:29AM +0100, Al Viro wrote:
> On Thu, Apr 30, 2020 at 03:13:38PM -0700, Matthew Wilcox wrote:
>
> > > +/**
> > > + * clear_page_private - clear page's private field and PG_private.
> > > + * @page: page to be cleared.
> > > + *
> > > + * The counterpart function of
On (20/04/30 19:14), Alper Nebi Yasak wrote:
> Currently, add_preferred_console sets a preferred console, but doesn't
> actually change /dev/console to match it. That part is handled within
> register_device, where a newly registered console driver will be set as
> /dev/console if it matches the
On Thu, Apr 30, 2020 at 03:13:38PM -0700, Matthew Wilcox wrote:
> > +/**
> > + * clear_page_private - clear page's private field and PG_private.
> > + * @page: page to be cleared.
> > + *
> > + * The counterpart function of attach_page_private.
> > + * Return: private data of page or NULL if page
On 2020-05-01 04:32, Bart Van Assche wrote:
On 2020-04-29 22:40, Can Guo wrote:
On 2020-04-30 13:08, Bart Van Assche wrote:
On 2020-04-29 21:10, Can Guo wrote:
During system resume, scsi_resume_device() decreases a request
queue's
pm_only counter if the scsi device was quiesced before. But
On 4/28/2020 4:18 AM, Greg KH wrote:
> On Mon, Apr 27, 2020 at 10:29:58AM -0700, Florian Fainelli wrote:
>>
>>
>> On 4/26/2020 11:19 PM, Jiri Slaby wrote:
>>> On 21. 04. 20, 14:31, Zou Wei wrote:
This patch fixes below error reported by coccicheck
1 - 100 of 1652 matches
Mail list logo
