If there is no reservation corresponding to a vma, map_chg is always != 0,
i.e. we can not meet the condition where a vma does not have reservation
while map_chg = 0.
Signed-off-by: Miaohe Lin
---
mm/hugetlb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/hugetlb.c
Since CMA is getting used more widely, it's more important to
keep monitoring CMA statistics for system health since it's
directly related to user experience.
This patch introduces sysfs statistics for CMA, in order to provide
some basic monitoring of the CMA allocator.
* the number of CMA page
The sparse tool complains as follows:
drivers/soc/ti/knav_qmss_queue.c:70:12: warning:
symbol 'knav_acc_firmwares' was not declared. Should it be static?
This symbol is not used outside of knav_qmss_queue.c, so this
commit marks it 'static const char * const'.
Reported-by: Hulk Robot
On Tue, Feb 09, 2021 at 04:19:03PM -0800, Kees Cook wrote:
> On Wed, Feb 10, 2021 at 02:23:48AM +0300, Andrey Ryabinin wrote:
> > Since GCC 8.0 -fsanitize=signed-integer-overflow doesn't work with -fwrapv.
> > -fwrapv makes signed overflows defines and GCC essentially disables
> > ubsan checks. On
Hi, Max,
> From: Max Gurtovoy
> Sent: Tuesday, February 2, 2021 12:28 AM
>
> Hi Alex and Cornelia,
>
> This series split the vfio_pci driver into 2 parts: pci driver and a
> subsystem driver that will also be library of code. The pci driver,
> vfio_pci.ko will be used as before and it will
On 2/9/21 11:26 PM, Greg KH wrote:
...
I just am not especially happy about the inability to do natural, efficient
things here, such as use a statically allocated set of things with sysfs. And
I remain convinced that the above is not "improper"; it's a reasonable
step, given the limitations of
On Wed, Feb 10, 2021 at 11:46:25AM +0800, Jiapeng Chong wrote:
> Fix the following coccicheck warning:
Please fix your robot or find yourself in the 'special' mailbox.
2b076054e524 ("remove boolinit.cocci")
This series first converts the debugfs files in the pinctrl subsystem to
octal permissions and then adds a new debug file "pinmux-select".
Function name and group name can be written to "pinmux-select" which
will cause the function and group to be activated on the pin controller.
Notes for PATCH
Switch over pinctrl debugfs files to use octal permissions as they are
preferred over symbolic permissions. Refer to commit f90774e1fd27
("checkpatch: look for symbolic permissions and suggest octal instead").
Signed-off-by: Drew Fustini
---
drivers/pinctrl/core.c| 6 +++---
Add "pinmux-select" to debugfs which will activate a function and group
when 2 integers " " are written to
the file. The write operation pinmux_select() handles this by checking
if fsel and gsel are valid selectors and then calling ops->set_mux().
The existing "pinmux-functions" debugfs file
Hi Kishon,
On 2/9/21 2:45 PM, Kishon Vijay Abraham I wrote:
> Hi Peter,
>
> On 09/02/21 5:53 pm, Péter Ujfalusi wrote:
>> Hi Kishon,
>>
>> On 2/9/21 11:00 AM, Kishon Vijay Abraham I wrote:
>>> bcdma_get_*() and udma_get_*() checks if bchan/rchan/tchan/rflow is
>>> already allocated by checking
The sparse tool complains as follows:
drivers/soc/mediatek/mtk-mutex.c:464:24: warning:
symbol 'mtk_mutex_driver' was not declared. Should it be static?
This symbol is not used outside of mtk-mutex.c, so this
commit marks it static.
Reported-by: Hulk Robot
Signed-off-by: Wei Yongjun
---
The sparse tool complains as follows:
drivers/mfd/arizona-spi.c:28:31: warning:
symbol 'reset_gpios' was not declared. Should it be static?
drivers/mfd/arizona-spi.c:29:31: warning:
symbol 'ldoena_gpios' was not declared. Should it be static?
Those symbols are not used outside of
The function cdn_dp_resume() may have no callers depending
on configuration, so it must be marked __maybe_unused to
avoid harmless warning:
drivers/gpu/drm/rockchip/cdn-dp-core.c:1124:12: warning:
'cdn_dp_resume' defined but not used [-Wunused-function]
1124 | static int cdn_dp_resume(struct
On Wed, Feb 10, 2021 at 06:30:45AM +0530, Mukul Mehar wrote:
> This patch fixes a warning, of the line ending with a '(',
> generated by checkpatch.pl.
>
> Signed-off-by: Mukul Mehar
> ---
> Changes since v1:
> - Fixed indentation.
> ---
> drivers/staging/most/sound/sound.c | 6 +++---
> 1
Use a customized signature service supported by openssl engine
to sign the kernel module.
Add command line parameters that support engine for sign-file
to use the customized openssl engine service to sign kernel modules.
Signed-off-by: Yang Song
---
scripts/sign-file.c | 65
Reviewed-by: Christian König for the series.
Am 10.02.21 um 00:48 schrieb Rikard Falkeborn:
Constify a few static vm_operations_struct that are never modified. Their
only usage is to assign their address to the vm_ops field in the
vm_area_struct, which is a pointer to const
It's not necessary to free memory allocated with devm_kzalloc
and using kfree leads to a double free.
Fixes: 363baf7d6051 ("NTB: Add support for EPF PCI-Express Non-Transparent
Bridge")
Reported-by: Hulk Robot
Signed-off-by: Wei Yongjun
---
drivers/ntb/hw/epf/ntb_hw_epf.c | 1 -
1 file
On Tue, 2021-02-09 at 23:28 -0800, Kees Cook wrote:
> On Sun, Jan 10, 2021 at 12:41:44PM -0800, Joe Perches wrote:
> > Replace the lkml.org links with lore to better use a single source
> > that's more likely to stay available long-term.
>
> What's the best way to teach checkpatch about this? I
Jiapeng Chong wrote:
> Fix the following coccicheck warning:
>
> ./drivers/net/wireless/realtek/rtlwifi/rtl8821ae/phy.c:3853:7-17:
> WARNING: Comparison of 0/1 to bool variable.
>
> Reported-by: Abaci Robot
> Signed-off-by: Jiapeng Chong
Patch applied to wireless-drivers-next.git, thanks.
Jiapeng Chong wrote:
> Fix the follow coccicheck warnings:
>
> ./drivers/net/wireless/realtek/rtlwifi/rtl8192se/hw.c:2305:6-27:
> WARNING: Comparison of 0/1 to bool variable.
>
> ./drivers/net/wireless/realtek/rtlwifi/rtl8192se/hw.c:1376:5-26:
> WARNING: Comparison of 0/1 to bool variable.
>
On Wed, Feb 10, 2021 at 01:39:42AM +0100, Filippo Sironi wrote:
> Amazon NVMe controllers do not support 64-bit DMA addresses; they are
> limited to 48-bit DMA addresses. Let's add a quirk to ensure that we
> make use of 48-bit DMA addresses to avoid misbehavior.
This should probably say some,
Hi Peter,
On 2021-02-02 11:41, Sai Prakash Ranjan wrote:
Hi Peter,
On 2021-02-01 19:11, Peter Zijlstra wrote:
On Mon, Feb 01, 2021 at 01:11:04PM +0530, Sai Prakash Ranjan wrote:
Ok I suppose you mean CONFIG_SECURITY_LOCKDOWN_LSM? But I don't see
how this new config has to depend on that?
On Wed, Feb 10, 2021 at 10:27:17AM +0300, Dan Carpenter wrote:
> On Wed, Feb 10, 2021 at 12:23:17AM +0530, karthik alapati wrote:
> > fix checkpatch.pl warning for "block comments should align the * on each
> > line"
> >
> > Signed-off-by: karthik alapati
> > ---
> >
On Sun, Jan 10, 2021 at 12:41:44PM -0800, Joe Perches wrote:
> Replace the lkml.org links with lore to better use a single source
> that's more likely to stay available long-term.
What's the best way to teach checkpatch about this? I couldn't find the
right place to do it. (And more generally,
Looks good,
Reviewed-by: Christoph Hellwig
On Tue, Feb 09, 2021 at 11:16:07PM -0800, John Hubbard wrote:
> On 2/9/21 11:12 PM, Minchan Kim wrote:
> ...
> > > > Agreed. How about this for the warning part?
> > > >
> > > > +
> > > > +/*
> > > > + * note: kobj_type should provide a release function to free
> > > > dynamically
> > > > + *
On Thu, Feb 04, 2021 at 04:59:32PM +0800, Hui Tang wrote:
> 1.Update clusters number for both Kunpeng920 and Kunpeng930.
> 2.Some bugfixs only on Kunpeng920, so added hardware version wrap.
> 3.Fix use of 'dma_map_single'.
> 4.Fix PASID on Kunpeng930.
>
> Hui Tang (2):
> crypto: hisilicon/hpre
On Wed, Feb 10, 2021 at 5:51 AM Namjae Jeon wrote:
> > Hope Sven will do a new release for Debian.
> > ( Note that Debian/bullseye release plans "Milestone 2" this Friday,
> > February 12th (see [1] > "Key
> > release dates" > "[2021-Feb-12] Soft Freeze"). Dunno which impact this
> > might
On Thu, Feb 04, 2021 at 05:00:24PM +0800, Hui Tang wrote:
> Enable x25519/x448/ecdh/ecdsa/sm2 algorithm on Kunpeng 930.
>
> Signed-off-by: Hui Tang
> ---
> drivers/crypto/hisilicon/hpre/hpre_main.c | 9 -
> 1 file changed, 8 insertions(+), 1 deletion(-)
Patch applied. Thanks.
--
On Fri, Feb 05, 2021 at 06:12:52PM +0800, Weili Qian wrote:
> This patchset fixes some bugs:
> 1. Removing the waiting reset's completion logic of driver.
> 2. In order to prevent request missing,
>call user's callback before device resetting.
> 3. Fix the value of 'QM_SQC_VFT_BASE_MASK_V2'.
>
On Thu, Feb 04, 2021 at 04:42:15PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> When CONFIG_CPUMASK_OFFSTACK is disabled, clang reports a warning
> about a bogus condition:
>
> drivers/crypto/marvell/octeontx2/otx2_cptlf.c:334:21: error: address of array
>
There is no need to use a new local variable ret2 to get the return value
of handle_userfault(). Use ret directly to make code more succinct.
Signed-off-by: Miaohe Lin
---
mm/huge_memory.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/mm/huge_memory.c
On Thu, Feb 04, 2021 at 07:11:33AM +, Xu Wang wrote:
> Remove casting the values returned by dma_alloc_coherent.
>
> Signed-off-by: Xu Wang
> ---
> drivers/crypto/cavium/cpt/cptvf_main.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
Patch applied. Thanks.
--
Email:
On Wed, Feb 03, 2021 at 03:42:10PM +, Daniele Alessandrelli wrote:
> From: Daniele Alessandrelli
>
> In ocs_aes_ccm_write_b0(), 'q' (the octet length of the binary
> representation of the octet length of the payload) is set to 'iv[0]',
> while it should be set to 'iv[0] & 0x7' (i.e., only
-20210209 #142 Tainted: GW
[ 57.207497] --
[ 57.207508] Xorg/459 is trying to acquire lock:
[ 57.207521] 888016edc518 (>mutex){+.+.}-{3:3}, at:
nouveau_bo_move+0x4bf/0x2ec0 [nouv
On Wed, Feb 03, 2021 at 09:09:33PM +0530, Bhaskar Chowdhury wrote:
>
> s/optimzation/optimization/
>
> Signed-off-by: Bhaskar Chowdhury
> ---
> crypto/xor.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Patch applied. Thanks.
--
Email: Herbert Xu
Home Page:
On Tue, Feb 02, 2021 at 11:17:30AM +0800, Yang Li wrote:
> Eliminate the following coccicheck warning:
> ./arch/powerpc/crypto/sha256-spe-glue.c:132:2-3: Unneeded
> semicolon
>
> Reported-by: Abaci Robot
> Signed-off-by: Yang Li
> ---
> arch/powerpc/crypto/sha256-spe-glue.c | 2 +-
> 1 file
On Wed, Feb 03, 2021 at 11:28:37AM +, Daniele Alessandrelli wrote:
> From: Daniele Alessandrelli
>
> The length ('len' parameter) passed to crypto_ecdh_decode_key() is never
> checked against the length encoded in the passed buffer ('buf'
> parameter). This could lead to an out-of-bounds
On Mon, Feb 01, 2021 at 02:44:31PM +0100, Geert Uytterhoeven wrote:
> The Marvell OcteonTX2 CPT physical function PCI device is present only
> on OcteonTx2 SoC, and not available as an independent PCIe endpoint.
> Hence add a dependency on ARCH_THUNDER2, to prevent asking the user
> about this
On Tue, Feb 02, 2021 at 10:06:15AM +0800, Jiapeng Chong wrote:
> Fix the following coccicheck warning:
>
> ./drivers/crypto/caam/debugfs.c:23:0-23: WARNING: caam_fops_u64_ro
> should be defined with DEFINE_DEBUGFS_ATTRIBUTE.
>
> ./drivers/crypto/caam/debugfs.c:22:0-23: WARNING: caam_fops_u32_ro
On Mon, Feb 01, 2021 at 04:14:59PM +0100, Jan Henrik Weinstock wrote:
> Ensure cooldown period tolerance of 1% is actually accounted for.
>
> Signed-off-by: Jan Henrik Weinstock
> ---
>
> Before patch, if period_us was less than 100us, no extra sleep time was
> added. If it was more than 100us,
On Sun, Feb 07, 2021 at 09:39:39AM -0500, Thara Gopinath wrote:
>
> + /*
> + * The crypto engine does not support any two keys
> + * being the same for triple des algorithms. The
> + * verify_skcipher_des3_key does not check for all the
> + * below conditions. Return
On 2/9/21 11:12 PM, Minchan Kim wrote:
...
Agreed. How about this for the warning part?
+
+/*
+ * note: kobj_type should provide a release function to free dynamically
+ * allocated object since kobject is responsible for controlling lifespan
+ * of the object. However, cma_area is static
We should not transfer the per-node surplus state when we do not cross the
node in order to save some cpu cycles
Signed-off-by: Miaohe Lin
---
mm/hugetlb.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index da347047ea10..4f2c92ddbca4 100644
---
On Tue, Feb 09, 2021 at 01:32:58PM -0800, Jesse Barnes wrote:
> > ==
> > Augmented Page Reclaim
> > ==
> > We would like to share a work with you and see if there is enough
> > interest to warrant a run for the mainline. This work is a part of
> > result
On Wed, Feb 10, 2021 at 07:43:37AM +0100, Greg KH wrote:
> On Tue, Feb 09, 2021 at 01:13:17PM -0800, Minchan Kim wrote:
> > On Tue, Feb 09, 2021 at 12:11:20PM -0800, John Hubbard wrote:
> > > On 2/9/21 9:49 AM, Greg KH wrote:
> > > > > > That's fine if you want to add it to the parent. If so,
Fix the following coccicheck warning:
./include/linux/mfd/db8500-prcmu.h:723:8-9: WARNING: return of 0/1 in
function 'db8500_prcmu_is_ac_wake_requested' with return type bool.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Chong
---
include/linux/mfd/db8500-prcmu.h | 2 +-
1 file changed, 1
On Wed, Feb 10, 2021 at 12:40:53AM +0100, Thomas Gleixner wrote:
> To avoid include recursion hell move the do_softirq_own_stack() related
> content into a generic asm header and include it from all places in arch/
> which need the prototype.
>
> This allows architectures to provide an inline
On Wed, Feb 10, 2021 at 12:40:52AM +0100, Thomas Gleixner wrote:
> To prepare for inlining do_softirq_own_stack() replace
> __ARCH_HAS_DO_SOFTIRQ with a Kconfig switch and select it in the affected
> architectures.
>
> This allows in the next step to move the function prototype and the inline
>
On 09.02.2021 17:40, Michael Walle wrote:
> Registers >= 16 are paged. Be sure to set the page. It seems this was
> working for now, because the default is correct for the registers used
> in the driver at the moment. But this will also assume, nobody will
> change the page select register before
Hello Lee,
I appreciate your thorough reviews :) Thanks.
On Tue, 2021-02-09 at 15:25 +, Lee Jones wrote:
> On Fri, 22 Jan 2021, Matti Vaittinen wrote:
>
> > BD9573 and BD9576 support set of "protection" interrupts for
> > "fatal"
> > issues. Those lead to SOC reset as PMIC shuts the power
> From: James Morse
> Sent: Tuesday, February 9, 2021 10:15 AM
> To: Dexuan Cui
> Cc: Rafael J. Wysocki ; linux-a...@vger.kernel.org;
> linux-kernel@vger.kernel.org; linux-hyp...@vger.kernel.org; Michael Kelley
> ; Leandro Pereira
> Subject: Re: How can a userspace program tell if the system
From: huangxuesen
bpf_skb_adjust_room sets the inner_protocol as skb->protocol for packets
encapsulation. But that is not appropriate when pushing Ethernet header.
Add an option to further specify encap L2 type and set the inner_protocol
as ETH_P_TEB.
Suggested-by: Willem de Bruijn
On 2/9/21 22:25, ira.we...@intel.com wrote:
> From: Ira Weiny
>
> Add VM_BUG_ON bounds checks to ensure the newly lifted and created page
> memory operations do not result in corrupted data in neighbor pages and
> to make them consistent with zero_user().[1][2]
>
I did not understand this, in my
We could use pages_per_huge_page to get the number of pages per hugepage,
use get_hstate_idx to calculate hstate index, and use hstate_is_gigantic
to check if a hstate is gigantic to make code more succinct.
Signed-off-by: Miaohe Lin
---
fs/hugetlbfs/inode.c | 2 +-
mm/hugetlb.c | 6
On Thu, Feb 04, 2021 at 11:09:40AM +, Lee Jones wrote:
> This set is part of a larger effort attempting to clean-up W=1
> kernel builds, which are currently overwhelmingly riddled with
> niggly little warnings.
>
> This is set 1 of 2 sets required to fully clean Crypto.
>
> Lee Jones (20):
>
On 10/02/2021 04:30, Michal Rostecki wrote:
From: Michal Rostecki
This patch series adds a new raid1 read policy - roundrobin. For each
request, it selects the mirror which has lower load than queue depth.
Load is defined as the number of inflight requests + a penalty value
(if the scheduled
Hi,
On Mon, 8 Feb 2021 16:56:00 +0300 Serge Semin wrote:
>
> Since commit bb3222f71b57 ("net: stmmac: platform: use optional clk/reset
> get APIs") a manual implementation of the optional device reset control
> functionality has been replaced with using the
> devm_reset_control_get_optional()
On 2/9/21 22:25, ira.we...@intel.com wrote:
> From: Ira Weiny
>
> 3 more common kmap patterns are kmap/memcpy/kunmap, kmap/memmove/kunmap.
> and kmap/memset/kunmap.
>
> Add helper functions for those patterns which use kmap_local_page().
>
> Cc: Andrew Morton
> Cc: Christoph Hellwig
>
On Tue, Feb 09, 2021 at 12:01:06PM -0800, Dan Williams wrote:
> On Tue, Feb 9, 2021 at 11:16 AM Greg KH wrote:
> [..]
> > > diff --git a/drivers/base/auxiliary.c b/drivers/base/auxiliary.c
> > > index 8336535f1e11..53f93a506626 100644
> > > --- a/drivers/base/auxiliary.c
> > > +++
Add tracepoints to retrieve information about the invoke_fn. This would
help to measure how many invoke_fn are triggered and how long it takes
to complete one invoke_fn call.
Signed-off-by: Jisheng Zhang
---
Since v1:
- add BUILD_BUG_ON() macro usage to make sure that the size of what is being
On Tue, Feb 09, 2021 at 03:17:00PM -0700, Dave Jiang wrote:
> When the auxiliary device code is built into the kernel, it can be executed
> before the auxiliary bus is registered. This causes bus->p to be not
> allocated and triggers a NULL pointer dereference when the auxiliary bus
> device gets
An endpoint is not a device and it is recommended to use clocks property
in the device node. Hence reverting the original change.
Fixes: 531e5b7abbde ("ASoC: audio-graph-card: Add clocks property to endpoint
node")
Suggested-by: Rob Herring
Cc: Kuninori Morimoto
Signed-off-by: Sameer Pujar
An endpoint is not a device and it is recommended to use clocks property
in device node. RT5658 Codec binding already specifies the usage of
clocks property. Thus move the clocks from endpoint to device node.
Fixes: 5b4f6323096a ("arm64: tegra: Audio graph sound card for Jetson AGX
Xavier")
It is recommended to not specifiy clocks property in an endpoint subnode.
This series moves clocks to device node.
However after moving the clocks to device node, the audio playback or
capture fails. The specified clock is not actually getting enabled and
hence the failure is seen. There seems to
If "clocks = <>" is specified from the CPU or Codec component
device node, the clock is not getting enabled. Thus audio playback
or capture fails.
Fix this by populating "simple_dai->clk" field when clocks property
is specified from device node as well. Also tidy up by re-organising
conditional
On Sun, Feb 07, 2021 at 06:04:40PM +0800, Longfang Liu wrote:
> If the header file "crypto/internal/hash.h" not
> added, the allocation of crypto_tfm will fail when
> the shash algorithm calculates the hash
> through the software.
>
> Signed-off-by: Longfang Liu
> ---
>
On Tue, Feb 09, 2021 at 01:13:17PM -0800, Minchan Kim wrote:
> On Tue, Feb 09, 2021 at 12:11:20PM -0800, John Hubbard wrote:
> > On 2/9/21 9:49 AM, Greg KH wrote:
> > > > > That's fine if you want to add it to the parent. If so, then the
> > > > > kobject controls the lifetime of the structure,
' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Srinivas-Kandagatla/ASoC-codecs-add-support-for-LPASS-Codec-TX-and-RX-macros/20210209-084643
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
for-next
config: ia64-randconfig
On 2/9/21 22:25, ira.we...@intel.com wrote:
> From: Ira Weiny
>
> kmap_local_page() is more efficient and is well suited for these calls.
> Convert the kmap() to kmap_local_page()
>
> Cc: Andrew Morton
> Cc: Christoph Hellwig
> Signed-off-by: Ira Weiny
Looks good.
Reviewed-by: Chaitanya
On Wed, Feb 10, 2021 at 6:30 AM Mark Brown wrote:
>
> On Tue, Feb 09, 2021 at 05:16:16PM +0800, Shengjiu Wang wrote:
> > On Mon, Feb 8, 2021 at 7:53 PM Mark Brown wrote:
>
> > > hw_params() can be called multiple times and there's no need for it to
> > > be balanced with hw_free(), I'd move this
/0day-ci/linux/commits/Vincenzo-Frascino/arm64-ARMv8-5-A-MTE-Add-async-mode-support/20210209-080907
base:59fa6a163ffabc1bf25c5e0e33899e268a96d3cc
config: powerpc64-randconfig-r033-20210209 (attached as .config)
compiler: powerpc-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget
On 2/9/21 22:25, ira.we...@intel.com wrote:
> From: Ira Weiny
>
> Working through a conversion to a call kmap_local_page() instead of
> kmap() revealed many places where the pattern kmap/memcpy/kunmap
> occurred.
>
> Eric Biggers, Matthew Wilcox, Christoph Hellwig, Dan Williams, and Al
> Viro all
On (21/02/10 11:48), Muchun Song wrote:
> printk_safe_flush_on_panic() caused the following deadlock on our
> server:
>
> CPU0: CPU1:
> panic rcu_dump_cpu_stacks
> kdump_nmi_shootdown_cpus
On Tue, Feb 09, 2021 at 05:17:30PM -0800, Linus Torvalds wrote:
> On Tue, Feb 9, 2021 at 1:43 AM Mike Rapoport wrote:
> >
> > This a small cleanup in memblock for 5.12 merge window.
>
> If it's going to make Andrew's patches easier to apply during the 5.12
> timeframe, I'm happy to pull this
On 10-02-21, 00:25, Jassi Brar wrote:
> Yup any bug fix should be sent in rc. But this, imo, lies on the
> boundary of code and cosmetic issues, so I practiced discretion to
> keep it for the next pull request lest I won't have much to send ;)
Fair enough, would have been better though if you
Perf failed to add kretprobe event with debuginfo of vmlinux which is
compiled by gcc with -fpatchable-function-entry option enabled.
The same issue with kernel module.
Issue:
# perf probe -v 'kernel_clone%return $retval'
..
Writing event: r:probe/kernel_clone__return _text+599624
On Thu, Feb 04, 2021 at 03:24:13PM +0800, Jiapeng Chong wrote:
> Fix the following coccicheck warning:
>
> ./drivers/crypto/picoxcell_crypto.c:1201:8-16: WARNING: use scnprintf
> or sprintf.
>
> Reported-by: Abaci Robot
> Signed-off-by: Jiapeng Chong
> ---
> drivers/crypto/picoxcell_crypto.c
On Tue, Feb 09, 2021 at 08:17:44AM -0800, Jakub Kicinski wrote:
> On Tue, 9 Feb 2021 10:20:30 +0100 Aleksander Morgado wrote:
> > This may be a stupid suggestion, but would the integration look less a
> > backdoor if it would have been named "mhi_wwan" and it exposed already
> > all the
On Tue, Feb 9, 2021 at 5:18 AM Viresh Kumar wrote:
>
> This patch fixes a bunch of sparse warnings in the newly added arm_mhuv2
> driver.
>
> drivers/mailbox/arm_mhuv2.c:506:24: warning: incorrect type in argument 1
> (different address spaces)
> drivers/mailbox/arm_mhuv2.c:506:24:expected
From: Ira Weiny
There are many places where the pattern kmap/memcpy/kunmap occurs.
This pattern was lifted to the core common functions
memcpy_[to|from]_page().
Use these new functions to reduce the code, eliminate direct uses of
kmap, and leverage the new core functions use of
From: Ira Weiny
There are many places where kmap/memove/kunmap patterns occur.
This pattern exists in the core common function copy_highpage().
Use copy_highpage to avoid open coding the use of kmap and leverages the
core functions use of kmap_local_page().
Development of this patch was aided
From: Ira Weiny
There are many places where kmap/memset/kunmap patterns occur.
This pattern exists in the core as zero_user()
Use zero_user() to eliminate direct uses of kmap and leverage the new
core functions use of kmap_local_page().
The development of this patch was aided by the following
From: Ira Weiny
3 more common kmap patterns are kmap/memcpy/kunmap, kmap/memmove/kunmap.
and kmap/memset/kunmap.
Add helper functions for those patterns which use kmap_local_page().
Cc: Andrew Morton
Cc: Christoph Hellwig
Signed-off-by: Ira Weiny
---
New for V2
---
include/linux/highmem.h
From: Ira Weiny
zero_user() is already defined with the same interface and contains the
same code pattern as memzero_page(). Remove memzero_page() and use the
already defined common function zero_user()
To: Alexander Viro
Cc: Andrew Morton
Cc: Christoph Hellwig
Signed-off-by: Ira Weiny
From: Ira Weiny
Add VM_BUG_ON bounds checks to ensure the newly lifted and created page
memory operations do not result in corrupted data in neighbor pages and
to make them consistent with zero_user().[1][2]
[1]
https://lore.kernel.org/lkml/20201210053502.gs1563...@iweiny-desk2.sc.intel.com/
From: Ira Weiny
Changes from V1:
Rework commit messages because they were very weak
Change 'fs/btrfs: X' to 'btrfs: x'
https://lore.kernel.org/lkml/20210209151442.gu1...@suse.cz/
Per Andrew
Split out changes to highmem.h
From: Ira Weiny
Working through a conversion to a call kmap_local_page() instead of
kmap() revealed many places where the pattern kmap/memcpy/kunmap
occurred.
Eric Biggers, Matthew Wilcox, Christoph Hellwig, Dan Williams, and Al
Viro all suggested putting this code into helper functions. Al
From: Ira Weiny
kmap_local_page() is more efficient and is well suited for these calls.
Convert the kmap() to kmap_local_page()
Cc: Andrew Morton
Cc: Christoph Hellwig
Signed-off-by: Ira Weiny
---
New for V2
---
include/linux/highmem.h | 8
1 file changed, 4 insertions(+), 4
Hello Lee,
On Tue, 2021-02-09 at 14:55 +, Lee Jones wrote:
> On Fri, 22 Jan 2021, Matti Vaittinen wrote:
>
> > Add core support for ROHM BD9576MUF and BD9573MUF PMICs which are
> > mainly used to power the R-Car series processors.
> >
> > Signed-off-by: Matti Vaittinen
> > ---
> > +
> >
On Tue, Feb 9, 2021 at 6:33 PM Andy Lutomirski wrote:
>
> Erratum #93 applies to the first generation of AMD K8 CPUs. Skip the
> workaround on newer CPUs.
Whoops, this breaks the !CPU_SUP_AMD build. It needs a fixup like this:
On 2/9/21 4:27 PM, Waiman Long wrote:
[ ... ]
>
> It is because in arch/mips/include/asm/spinlock.h, asm/qrwlock.h is included
> before asm/qspinlock.h. The compilation error should be gone if the
> asm/qrwlock.h is removed or moved after asm/qspinlock.h.
>
> I did a x86 build and there was
On Tue, Feb 09, 2021 at 12:27:01PM +0100, Marco Elver wrote:
> For double-checked locking in bpf_common_lru_push_free(), node->type is
> read outside the critical section and then re-checked under the lock.
> However, concurrent writes to node->type result in data races.
>
> For example, the
ixes the problem. Bisect log
is attached.
It may also break a variety of other boot tests, but with 115 of 430
boot tests failing in -next it is difficult to identify all culprits.
Guenter
---
Bisect log:
# bad: [a4bfd8d46ac357c12529e4eebb6c89502b03ecc9] Add linux-next specific files
for 202102
Replace placeholder text about decoding stack traces with a section that
properly describes what a typical user should do these days. To make
it works for them, add a paragraph in an earlier section to ensure
people build their kernels with everything that's needed to decode stack
traces later.
On Tue, Feb 9, 2021 at 6:33 PM Theodore Ts'o wrote:
>
> On Tue, Feb 09, 2021 at 05:32:06PM -0800, Daniel Latypov wrote:
> >
> > After [2]:
> > $ ./tools/testing/kunit.py run --kunitconfig=fs/ext4/.kunitconfig
>
> Any chance that in the future this might become:
>
> $ ./tools/testing/kunit.py
On Fri, 2021-02-05 at 10:55 +0100, Lukas Bulwahn wrote:
> Commit 142d93d12dc1 ("net/mlx5: Add devlink subfunction port
> documentation") refers to a section 'mlx5 port function' in the table
> of
> contents, but includes a section 'mlx5 function attributes' instead.
>
> Hence, make htmldocs
Hi all,
> -Original Message-
> From: Arnd Bergmann [mailto:a...@kernel.org]
> Sent: Tuesday, February 9, 2021 8:36 PM
> To: Geert Uytterhoeven
> Cc: Stephen Rothwell ; Bartosz Golaszewski
> ; Olof Johansson ;
> Arnd Bergmann ; ARM ;
> Bartosz Golaszewski
> ; Linux Kernel Mailing List
On Wed, 2021-02-10 at 10:50 +0530, Naresh Kamboju wrote:
> While building Linux next tag 20210209 s390 (defconfig) with gcc-9
> make modules failed.
>
...
> Reported-by: Naresh Kamboju
>
Thanks for the report a patch was already posted earlier today
https://patchwork.ker
1 - 100 of 1488 matches
Mail list logo
