On Mon, Jan 18, 2021 at 11:39:09PM -0500, Pavel Tatashin wrote:
> When migration failure occurs, we still pin pages, which means
> that we may pin CMA movable pages which should never be the case.
>
> Instead return an error without pinning pages when migration failure
> happens.
>
> No need to r
> This should have a fixme too, this is a bug.
OK
>
> The patch looks OK, but I keep feeling this logic is all really
> overcomplicated...
I agree, I have a simplification patch for this logic, check out patch 12/14.
>
> Reviewed-by: Jason Gunthorpe
Thank you for your review.
Pasha
On Fri, Jan 15, 2021, Babu Moger wrote:
> ---
> arch/x86/include/asm/svm.h |4 +++-
> arch/x86/kvm/svm/sev.c |4
> arch/x86/kvm/svm/svm.c | 19 +++
> 3 files changed, 22 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/include/asm/svm.h b/arch/x86/inc
On Mon, Jan 04, 2021 at 08:59:09PM +0530, Kishon Vijay Abraham I wrote:
> Add documentation to help users use pci-epf-ntb function driver and
> existing host side NTB infrastructure for NTB functionality.
>
> Signed-off-by: Kishon Vijay Abraham I
> Reviewed-by: Randy Dunlap
> ---
> Documentatio
On Mon, Jan 04, 2021 at 08:58:53PM +0530, Kishon Vijay Abraham I wrote:
> Add specification for the *PCI NTB* function device. The endpoint function
> driver and the host PCI driver should be created based on this
> specification.
>
> Signed-off-by: Kishon Vijay Abraham I
A few typos below if th
On Tue, Jan 19, 2021 at 1:30 PM Jason Gunthorpe wrote:
>
> On Mon, Jan 18, 2021 at 11:39:14PM -0500, Pavel Tatashin wrote:
> > Zero page should not be used for long term pinned pages. Once pages
> > are pinned their physical addresses cannot changed until they are unpinned.
> >
> > Guarantee to al
This series adds bindings and device-tree for the Beelink (AZW) GS-King-X,
which like GT-King and GT-King Pro is based on the W400 reference design.
Changes since v2:
- shorten audio card name to GSKING-X
- add Neil's tested-by
- add Martin's reviews
Changes since v1:
- move audio from TDM_B to T
On 15-01-21, 09:47, Jack Pham wrote:
> Add compatible strings for the USB DWC3 controller on QCOM SM8150,
> SM8250 and SM8350 SoCs.
>
> Note the SM8150 & SM8250 compatibles are already being used in the
> dts but was missing from the documentation.
Reviewed-by: Vinod Koul
--
~Vinod
* Rob Herring [210119 14:51]:
> On Mon, Jan 18, 2021 at 2:41 AM Tony Lindgren wrote:
> > - PRM power managment interrupts that also pinctrl driver uses
>
> I haven't looked at it, but can't one driver go find the other node
> and the interrupts it needs? There's nothing wrong with a driver
> loo
Hello,
syzbot found the following issue on:
HEAD commit:1d94330a Merge tag 'for-5.11/dm-fixes-1' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=124f589f50
kernel config: https://syzkaller.appspot.com/x/.config?x=ee2266946ed36986
das
Hello,
syzbot found the following issue on:
HEAD commit:66c55602 skbuff: back tiny skbs with kmalloc() in __netdev..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=121bf89f50
kernel config: https://syzkaller.appspot.com/x/.config?x=c60c9ff9cc916cbc
dashboar
**
** NOTE: To "view the full picture", please look at the following
** patch series:
** https://patchwork.kernel.org/project/linux-arm-msm/list/?series=413355
** This is a subset of that series.
**
Changes in v4:
- Huge patch series has been split for better reviewability
Hi Saravana,
On Tue, Jan 19, 2021 at 6:54 PM Saravana Kannan wrote:
> On Tue, Jan 19, 2021 at 2:20 AM Linus Walleij
> wrote:
> > On Tue, Jan 19, 2021 at 9:50 AM Geert Uytterhoeven
> > wrote:
> > > > Can we pull this into driver-core-next please? It fixes issues on some
> > > > boards with fw_
On 1/19/2021 3:06 AM, Borislav Petkov wrote:
On Tue, Dec 29, 2020 at 01:30:29PM -0800, Yu-cheng Yu wrote:
Shadow Stack provides protection against function return address
corruption. It is active when the processor supports it, the kernel has
CONFIG_X86_CET_USER enabled, and the application is
On Tue, Jan 19, 2021 at 12:34:07PM -0600, Bjorn Helgaas wrote:
> [cc->to Greg]
>
> On Mon, Jan 04, 2021 at 08:59:02PM +0530, Kishon Vijay Abraham I wrote:
> > Documentation/PCI/endpoint/pci-endpoint-cfs.rst explains how a user
> > has to create a directory in-order to create a 'EPF Device' that
>
Paul Lawrence writes:
> Below patch will cause NULL ptr dereferences if the optional filenames
> are not present.
>
> Fixes: ef3ba87cb7c9 (um: ubd: Set device serial attribute from cmdline)
> Signed-off-by: Paul Lawrence
Looks good.
Reviewed-by: Gabriel Krisman Bertazi
Totally unrelated, but
On Tue, Jan 19, 2021 at 12:34:05PM -0600, Bjorn Helgaas wrote:
> [cc->to Greg]
>
> On Mon, Jan 04, 2021 at 08:59:02PM +0530, Kishon Vijay Abraham I wrote:
> > Documentation/PCI/endpoint/pci-endpoint-cfs.rst explains how a user
> > has to create a directory in-order to create a 'EPF Device' that
>
On Tue, 15 Dec 2020 12:54:36 +0100 SeongJae Park wrote:
> From: SeongJae Park
>
> Even somehow the initial monitoring target regions are well constructed
> to fulfill the assumption (pages in same region have similar access
> frequencies), the data access pattern can be dynamically changed. Th
Hi Saravana,
On Tue, Jan 19, 2021 at 7:19 PM Saravana Kannan wrote:
> On Tue, Jan 19, 2021 at 10:10 AM Geert Uytterhoeven
> wrote:
> > On Tue, Jan 19, 2021 at 6:54 PM Saravana Kannan
> > wrote:
> > > On Tue, Jan 19, 2021 at 2:20 AM Linus Walleij
> > > wrote:
> > > > On Tue, Jan 19, 2021 at 9
On 19.01.21 19:17, Jason Gunthorpe wrote:
On Tue, Jan 19, 2021 at 07:08:32PM +0100, Bodo Stroesser wrote:
On 19.01.21 19:03, Jason Gunthorpe wrote:
On Tue, Jan 19, 2021 at 06:24:49PM +0100, Bodo Stroesser wrote:
I had a second look into math.h, but I don't find any reason why round_up
could o
On Tue, Jan 19, 2021 at 01:08:17PM +0900, Namhyung Kim wrote:
SNIP
> > + if (!session)
> > + return -ENOMEM;
> > +
> > + pr_debug("reconfig: found new session %s\n", name);
> > + /* This is new session, trigger reconfig to start it.
On 18-01-21, 09:21, mda...@codeaurora.org wrote:
> On 2021-01-15 11:28, Vinod Koul wrote:
> > On 14-01-21, 01:20, mda...@codeaurora.org wrote:
> > > On 2021-01-12 15:40, Vinod Koul wrote:
> > > > On 12-01-21, 15:01, mda...@codeaurora.org wrote:
> > > > > On 2020-12-21 23:03, mda...@codeaurora.org w
The remaining callers of kernel_fpu_begin() in 64-bit kernels don't use 387
instructions, so there's no need to sanitize the FPU state. Skip it to get
most of the performance we lost back.
Reported-by: Krzysztof Olędzki
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/fpu/api.h | 12 +++
Currently, requesting kernel FPU access doesn't distinguish which parts of
the extended ("FPU") state are needed. This is nice for simplicity, but
there are a few cases in which it's suboptimal:
- The vast majority of in-kernel FPU users want XMM/YMM/ZMM state but do
not use legacy 387 state.
On Tue, Jan 19, 2021 at 05:10:45PM +0100, Mauro Carvalho Chehab wrote:
> +static int hi6421_spmi_regulator_get_voltage_sel(struct regulator_dev *rdev)
> +{
> +static int hi6421_spmi_regulator_set_voltage_sel(struct regulator_dev *rdev,
> + unsigned int
This series fixes two regressions: a boot failure on AMD K7 and a
performance regression on everything.
I did a double-take here -- the regressions were reported by different
people, both named Krzysztof :)
Changes from v1:
- Fix MMX better -- MMX really does need FNINIT.
- Improve the EFI code
EFI uses kernel_fpu_begin() to conform to the UEFI calling convention.
This specifically requires initializing FCW, whereas no sane 64-bit kernel
code should use legacy 387 operations that reference FCW.
This should enable us to safely change the default semantics of
kernel_fpu_begin() to stop ini
The default kernel_fpu_begin() doesn't work on systems that support XMM but
haven't yet enabled CR4.OSFXSR. This causes crashes when _mmx_memcpy() is
called too early because LDMXCSR generates #UD when the aforementioned bit
is clear.
Fix it by using kernel_fpu_begin_mask(KFPU_387) explicitly.
F
The implementation was rather buggy. It unconditionally marked PTEs
read-only, even for VM_SHARED mappings. I'm not sure whether this is
actually a problem, but it certainly seems unwise. More importantly, it
released the mmap lock before flushing the TLB, which could allow a racing
CoW operatio
On Mon, Jan 18, 2021 at 7:30 PM Vincenzo Frascino
wrote:
>
> MTE provides an asynchronous mode for detecting tag exceptions. In
> particular instead of triggering a fault the arm64 core updates a
> register which is checked by the kernel after the asynchronous tag
> check fault has occurred.
>
> A
On 19.01.21 19:03, Jason Gunthorpe wrote:
On Tue, Jan 19, 2021 at 06:24:49PM +0100, Bodo Stroesser wrote:
I had a second look into math.h, but I don't find any reason why round_up
could overflow. Can you give a hint please?
#define round_up(x, y) x)-1) | __round_mask(x, y))+1)
On Tue, Jan 19, 2021 at 1:05 AM Geert Uytterhoeven wrote:
>
> Hi Saravana,
>
> On Mon, Jan 18, 2021 at 10:19 PM Saravana Kannan wrote:
> > On Mon, Jan 18, 2021 at 11:16 AM Geert Uytterhoeven
> > wrote:
> > > On Mon, Jan 18, 2021 at 6:59 PM Marc Zyngier wrote:
> > > > On 2021-01-18 17:39, Geert
On Mon, Jan 18, 2021 at 11:39:08PM -0500, Pavel Tatashin wrote:
> When pages are isolated in check_and_migrate_movable_pages() we skip
> compound number of pages at a time. However, as Jason noted, it is
> not necessary correct that pages[i] corresponds to the pages that
> we skipped. This is becau
On Mon, Jan 18, 2021 at 7:30 PM Vincenzo Frascino
wrote:
>
> This patchset implements the asynchronous mode support for ARMv8.5-A
> Memory Tagging Extension (MTE), which is a debugging feature that allows
> to detect with the help of the architecture the C and C++ programmatic
> memory errors like
If bit 22 of Group B Features is set, the guest has access to the
Isolation Configuration CPUID leaf. On x86, the first four bits
of EAX in this leaf provide the isolation type of the partition;
we entail three isolation types: 'SNP' (hardware-based isolation),
'VBS' (software-based isolation), an
On Tue, Jan 19, 2021 at 09:53:36AM -0800, Marc Orr wrote:
> This patch ensures that when `nvme_map_data()` fails to map the
> addresses in a scatter/gather list:
>
> * The addresses are not incorrectly unmapped. The underlying
> scatter/gather code unmaps the addresses after detecting a failure.
>
Restrict the NVSP protocol version(s) that will be negotiated with the
host to be NVSP_PROTOCOL_VERSION_61 or greater if the guest is running
isolated. Moreover, do not advertise the SR-IOV capability and ignore
NVSP_MSG_4_TYPE_SEND_VF_ASSOCIATION messages in isolated guests, which
are not suppose
The current fixed metadata version format (version 0), means that adding
metadata parameter items renders files from a previous version of perf
unreadable. Per CPU parameters appear in a fixed order, but there is no
field to indicate the number of ETM parameters per CPU.
This patch updates the per
Only the VSCs or ICs that have been hardened and that are critical for
the successful adoption of Confidential VMs should be allowed if the
guest is running isolated. This change reduces the footprint of the
code that will be exercised by Confidential VMs and hence the exposure
to bugs and vulnera
Hi all,
To reduce the footprint of the code that will be exercised, and hence
the exposure to bugs and vulnerabilities, restrict configurations and
devices on 'isolated' VMs.
Specs of the Isolation Configuration leaf (cf. patch #1) were derived
from internal discussions with the Hyper-V team and,
**
** NOTE: To "view the full picture", please look at the following
** patch series:
** https://patchwork.kernel.org/project/linux-arm-msm/list/?series=413355
** This is a subset of that series.
**
In preparation for adding a driver for CPR3, CPR4 and CPR4-Hardened,
commo
On Mon, Jan 18, 2021 at 9:55 AM Randy Dunlap wrote:
>
> On 1/15/21 6:32 PM, Vipin Sharma wrote:
> > Documentation of Encryption IDs controller. This new controller is used
> > to track and limit usage of hardware memory encryption capabilities on
> > the CPUs.
> >
> > Signed-off-by: Vipin Sharma
On Tue, Jan 19, 2021 at 11:20:24AM +0100, Linus Walleij wrote:
> On Tue, Jan 19, 2021 at 9:50 AM Geert Uytterhoeven
> wrote:
>
> > > Can we pull this into driver-core-next please? It fixes issues on some
> > > boards with fw_devlink=on.
> >
> > On r8a77951-salvator-xs.dts, it introduces one more
In commit 208921bae696 ("arm64: dts: qcom: pmi8998: Add nodes for
LAB and IBB regulators") bindings for the lab/ibb regulators were
added to the pmi8998 dt, but the original committer has never
specified what the interrupts were for.
LAB and IBB regulators provide two interrupts, SC-ERR (short
circ
In commit a871be6b8eee ("cpuidle: Convert Qualcomm SPM driver to a generic
CPUidle driver") the SPM driver has been converted to a
generic CPUidle driver: that was mainly made to simplify the
driver and that was a great accomplishment;
Though, it was ignored that the SPM driver is not used only
on
**
** NOTE: To "view the full picture", please look at the following
** patch series:
** https://patchwork.kernel.org/project/linux-arm-msm/list/?series=413355
** This is a subset of that series.
**
Changes in v4:
- Huge patch series has been split for better reviewability
On Tue, Jan 19, 2021 at 2:20 AM Linus Walleij wrote:
>
> On Tue, Jan 19, 2021 at 9:50 AM Geert Uytterhoeven
> wrote:
>
> > > Can we pull this into driver-core-next please? It fixes issues on some
> > > boards with fw_devlink=on.
> >
> > On r8a77951-salvator-xs.dts, it introduces one more failure
This patch ensures that when `nvme_map_data()` fails to map the
addresses in a scatter/gather list:
* The addresses are not incorrectly unmapped. The underlying
scatter/gather code unmaps the addresses after detecting a failure.
Thus, unmapping them again in the driver is a bug.
* The DMA pool all
On Tuesday 19 Jan 2021 at 17:42:44 (+), Qais Yousef wrote:
> Hmm IIUC you want to still tag it as misfit so it'll be balanced within the
> little cores in case there's another core with more spare capacity, right?
Well yes but that's just a special case. But even you have big CPUs in
the affin
On Tue, Jan 19, 2021 at 11:35 AM Christophe Leroy
wrote:
>
> Hi Rasmus,
>
> Le 28/11/2019 à 15:55, Rasmus Villemoes a écrit :
> > The QUICC engine drivers use the powerpc-specific out_be32() etc. In
> > order to allow those drivers to build for other architectures, those
> > must be replaced by io
From: Manivannan Sadhasivam
Convert Qualcomm cpufreq devicetree binding to YAML.
Signed-off-by: Manivannan Sadhasivam
Signed-off-by: AngeloGioacchino Del Regno
---
.../bindings/cpufreq/cpufreq-qcom-hw.txt | 172 ---
.../bindings/cpufreq/cpufreq-qcom-hw.yaml | 204 +++
On Fri, Dec 18, 2020 at 08:33:37PM +, Jon Hunter wrote:
>
> On 18/12/2020 17:54, Linus Torvalds wrote:
> > On Fri, Dec 18, 2020 at 7:33 AM Jon Hunter wrote:
> >>
> >> However, if you are saying that this is a problem/bug with our builders,
> >> then of course we will have to get this fixed.
>
The CPR driver's common functions were split and put in another
file in order to support newer CPR revisions: to simplify the
commonization, the expected names of the fuses had to be changed
in order for both new and old support to use the same fuse name
retrieval function and keeping the naming co
Add the SDM630, SDM636 and SDM660 to the blacklist since the CPU
scaling is handled out of this.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/cpufreq/cpufreq-dt-platdev.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c
b/drivers/cpufreq/cpuf
This commit introduces a new driver, based on the one for cpr v1,
to enable support for the newer Qualcomm Core Power Reduction
hardware, known downstream as CPR3, CPR4 and CPRh, and support
for MSM8998 and SDM630 CPU power reduction.
In these new versions of the hardware, support for various new
On 1/16/21 1:18 AM, Miaohe Lin wrote:
> Since commit e5ff215941d5 ("hugetlb: multiple hstates for multiple page
> sizes"), we can use macro default_hstate to get the struct hstate which
> we use by default. But init_hugetlbfs_fs() forgot to use it.
>
> Signed-off-by: Miaohe Lin
Thanks,
Reviewed
On new SoCs (SDM845 onwards) the Operating State Manager (OSM) is
being programmed in the bootloader and write-protected by the
hypervisor, leaving to the OS read-only access to some of its
registers (in order to read the Lookup Tables and also some
status registers) and write access to the p-state
Add the bindings for the CPR3 driver to the documentation.
Signed-off-by: AngeloGioacchino Del Regno
---
.../bindings/soc/qcom/qcom,cpr3.yaml | 241 ++
1 file changed, 241 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,cpr3.yaml
diff
In order to fine-tune the frequency scaling from various governors,
allow to set a maximum transition latency from OPPs, which may be
different depending on the SoC.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/cpufreq/qcom-cpufreq-hw.c | 7 +++
1 file changed, 7 insertions(+)
dif
Please CC Andrew on hugetlb patches as they need to go through his tree.
On 1/16/21 1:26 AM, Miaohe Lin wrote:
> The variable avoid_reserve is meaningless because we never changed its
> value and just passed it to alloc_huge_page(). So remove it to make code
> more clear that in hugetlbfs_fallocat
On Mon, 18 Jan 2021 14:16:26 -0400
Jason Gunthorpe wrote:
> On Mon, Jan 18, 2021 at 05:00:09PM +0100, Cornelia Huck wrote:
>
> > > You can say that all the HW specific things are in the mlx5_vfio_pci
> > > driver. It is an unusual driver because it must bind to both the PCI
> > > VF with a pci_d
Hi Andrey,
On 1/19/21 6:27 PM, Andrey Konovalov wrote:
> On Tue, Jan 19, 2021 at 6:26 PM Vincenzo Frascino
> wrote:
>>
>> With the introduction of KASAN_HW_TAGS, kasan_report() dereferences
>> the address passed as a parameter.
>>
>> Add a comment to make sure that the preconditions to the functi
On Tue, Jan 19, 2021 at 07:12:40PM +0100, Andrey Konovalov wrote:
> On Tue, Jan 19, 2021 at 4:45 PM Vincenzo Frascino
> wrote:
> > On 1/19/21 2:45 PM, Catalin Marinas wrote:
> > > On Mon, Jan 18, 2021 at 06:30:33PM +, Vincenzo Frascino wrote:
> > >> mte_assign_mem_tag_range() is called on prod
On Wed, Jan 20, 2021 at 2:48 AM Thierry Reding wrote:
>
> On Fri, Dec 18, 2020 at 08:33:37PM +, Jon Hunter wrote:
> >
> > On 18/12/2020 17:54, Linus Torvalds wrote:
> > > On Fri, Dec 18, 2020 at 7:33 AM Jon Hunter wrote:
> > >>
> > >> However, if you are saying that this is a problem/bug with
On Tue, Jan 19, 2021 at 07:00:57PM +, Vincenzo Frascino wrote:
> On 1/19/21 6:52 PM, Catalin Marinas wrote:
> > On Tue, Jan 19, 2021 at 07:27:43PM +0100, Andrey Konovalov wrote:
> >> On Tue, Jan 19, 2021 at 6:26 PM Vincenzo Frascino
> >> wrote:
> >>>
> >>> With the introduction of KASAN_HW_TAG
On 1/19/21 7:02 PM, Catalin Marinas wrote:
> On Tue, Jan 19, 2021 at 07:00:57PM +, Vincenzo Frascino wrote:
>> On 1/19/21 6:52 PM, Catalin Marinas wrote:
>>> On Tue, Jan 19, 2021 at 07:27:43PM +0100, Andrey Konovalov wrote:
On Tue, Jan 19, 2021 at 6:26 PM Vincenzo Frascino
wrote:
On Mon, Jan 18, 2021 at 11:03 PM Daniel Vetter wrote:
>
> On Tue, Jan 19, 2021 at 12:41 AM Yiwei Zhang wrote:
> >
> > On the success of virtio_gpu_object_create, add size of newly allocated
> > bo to the tracled total_mem. In drm_gem_object_funcs.free, after the gem
> > bo lost its last refcount,
Hi,
On Friday 15 Jan 2021 at 13:18:47 (+0530), Viresh Kumar wrote:
> On 13-01-21, 16:18, Ionela Voinescu wrote:
> > On Tuesday 15 Dec 2020 at 16:46:35 (+0530), Viresh Kumar wrote:
> > > +void topology_scale_freq_tick(void)
> > > +{
> > > + struct scale_freq_tick_data *sftd = *this_cpu_ptr(&sft_dat
19.01.2021 20:40, Andy Lutomirski пишет:
The implementation was rather buggy. It unconditionally marked PTEs
read-only, even for VM_SHARED mappings. I'm not sure whether this is
actually a problem, but it certainly seems unwise. More importantly, it
released the mmap lock before flushing the T
On 1/19/21 6:52 PM, Catalin Marinas wrote:
> On Tue, Jan 19, 2021 at 07:27:43PM +0100, Andrey Konovalov wrote:
>> On Tue, Jan 19, 2021 at 6:26 PM Vincenzo Frascino
>> wrote:
>>>
>>> With the introduction of KASAN_HW_TAGS, kasan_report() dereferences
>>> the address passed as a parameter.
>>>
>>
On Mon, Jan 04, 2021 at 08:59:05PM +0530, Kishon Vijay Abraham I wrote:
> Add a new endpoint function driver to provide NTB functionality
> using multiple PCIe endpoint instances.
>
> Signed-off-by: Kishon Vijay Abraham I
Several typos below if there's any opportunity for revision.
> ---
> dri
On Tue, Jan 19, 2021 at 02:06:09PM +, Chen Jun wrote:
> since commit 5e89c55e4ed81d7abb1ce8828db35fa389dc0e90
> ("arm64: kernel: implement ACPI parking protocol")
>
> On arm64, IPI 6 will be wasted without setting
> CONFIG_ARM64_ACPI_PARKING_PROTOCOL.
>
> Signed-off-by: Chen Jun
> ---
> arc
Hi,
Do you know of a current platform that would benefit from this, that we
could run some tests on?
I've Cc-ed Jeremy as well, as he might be interested in this.
Also, please find some initial comments below:
On Tuesday 15 Dec 2020 at 16:46:36 (+0530), Viresh Kumar wrote:
> The Frequency Invar
Hi,
On Fri, Jan 15, 2021 at 1:39 AM Jiapeng Zhong
wrote:
>
> Fix the follow coccicheck warnings:
>
> ./drivers/net/wireless/marvell/mwifiex/fw.h: WARNING use flexible-array
> member instead(https://www.kernel.org/doc/html/latest/process/
> deprecated.html#zero-length-and-one-element-arrays)
>
> R
link_id can be zero and if we have multiple controller instances
in a system like Qualcomm debugfs will end-up with duplicate namespace
resulting in incorrect debugfs entries.
Using id should give a unique debugfs directory entry and should fix
below
warning too.
"debugfs: Directory 'master-
Is there v4 2/2?
On 01/19, Daeho Jeong wrote:
> From: Daeho Jeong
>
> We've added a new mount option "checkpoint=merge", which creates a
> kernel daemon and makes it to merge concurrent checkpoint requests as
> much as possible to eliminate redundant checkpoint issues. Plus, we
> can eliminate t
On Mon, 18 Jan 2021, Charan Teja Reddy wrote:
> should_proactive_compact_node() returns true when sum of the
> weighted fragmentation score of all the zones in the node is greater
> than the wmark_high of compaction, which then triggers the proactive
> compaction that operates on the individual zo
On Tue, Jan 19, 2021 at 7:57 PM Vincenzo Frascino
wrote:
>
>
>
> On 1/19/21 6:52 PM, Catalin Marinas wrote:
> > On Tue, Jan 19, 2021 at 07:27:43PM +0100, Andrey Konovalov wrote:
> >> On Tue, Jan 19, 2021 at 6:26 PM Vincenzo Frascino
> >> wrote:
> >>>
> >>> With the introduction of KASAN_HW_TAGS,
On Tue, Jan 19, 2021 at 8:00 PM Catalin Marinas wrote:
>
> On Tue, Jan 19, 2021 at 07:12:40PM +0100, Andrey Konovalov wrote:
> > On Tue, Jan 19, 2021 at 4:45 PM Vincenzo Frascino
> > wrote:
> > > On 1/19/21 2:45 PM, Catalin Marinas wrote:
> > > > On Mon, Jan 18, 2021 at 06:30:33PM +, Vincenzo
On Tue, Jan 19, 2021, Andy Lutomirski wrote:
> diff --git a/arch/x86/kernel/fpu/core.c b/arch/x86/kernel/fpu/core.c
> index eb86a2b831b1..d4a71596c41e 100644
> --- a/arch/x86/kernel/fpu/core.c
> +++ b/arch/x86/kernel/fpu/core.c
> @@ -121,7 +121,7 @@ int copy_fpregs_to_fpstate(struct fpu *fpu)
> }
Hi,
Here are a few doc comments for you:
On 1/8/21 1:25 PM, mgr...@linux.intel.com wrote:
> From: Srikanth Thokala
>
> Provide overview of XLink PCIe driver implementation
>
> Cc: Jonathan Corbet
> Cc: linux-...@vger.kernel.org
> Reviewed-by: Mark Gross
> Signed-off-by: Srikanth Thokala
> --
On 1/19/2021 4:04 AM, Borislav Petkov wrote:
On Tue, Dec 29, 2020 at 01:30:33PM -0800, Yu-cheng Yu wrote:
[...]
+DEFINE_IDTENTRY_ERRORCODE(exc_control_protection)
+{
+ struct task_struct *tsk;
+
+ if (!user_mode(regs)) {
+ if (notify_die(DIE_TRAP, "control protection f
> On Jan 19, 2021, at 03:29, Lee Jones wrote:
>
> On Mon, 18 Jan 2021, Daniel Vetter wrote:
>
>> On Mon, Jan 18, 2021 at 03:09:45PM +, Lee Jones wrote:
>>> On Mon, 18 Jan 2021, Daniel Vetter wrote:
>>>
On Fri, Jan 15, 2021 at 06:27:15PM +, Zack Rusin wrote:
>
>> On Jan
One more thing, for context:
On Tue, Jan 19, 2021 at 11:11 AM Brian Norris wrote:
> On Fri, Jan 15, 2021 at 1:39 AM Jiapeng Zhong
> wrote:
> >
> > Fix the follow coccicheck warnings:
> >
> > ./drivers/net/wireless/marvell/mwifiex/fw.h: WARNING use flexible-array
> > member instead(https://www.ke
On Tue, Jan 19, 2021 at 04:11:31AM +, Bhaskara Budiredla wrote:
> Do you see any issues to ACK this if the mmc pstore
> registration is through register_pstore_blk()?
> As Uffe said, eMMC would need to go through
> psblk_generic_blk_read()/write() instead of
> mmcpstore_read()/write().
I would
On 01/15, Chao Yu wrote:
> On 2021/1/15 5:53, Jaegeuk Kim wrote:
> > On 12/30, Chao Yu wrote:
> > > ThreadA ThreadB
> > > - f2fs_ioc_start_atomic_write
> > > - write
> > > - f2fs_ioc_commit_atomic_write
> > > - f2fs_commit_inmem_pages
> > > - f2fs_drop_inmem_pa
Em Tue, Jan 19, 2021 at 06:39:37PM +0100, Jiri Olsa escreveu:
> On Tue, Jan 19, 2021 at 11:59:22AM -0300, Arnaldo Carvalho de Melo wrote:
>
> SNIP
>
> > > +}
> >
> > 7812.70 ubuntu:18.04-x-sparc64: FAIL sparc64-linux-gnu-gcc
> > (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
> >
> > util/de
I'm announcing the release of the 5.10.9 kernel.
All users of the 5.10 kernel series must upgrade.
The updated 5.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.10.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 5c9d680b7ce5..a5edbd4f3414 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 4
-SUBLEVEL = 90
+SUBLEVEL = 91
EXTRAVERSION =
NAME = Kleptomaniac Octopus
@@ -480,7 +480,7 @@ KBUILD_AFLAGS :=
diff --git a/Makefile b/Makefile
index 3e44a813604e..a994b12d2011 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 19
-SUBLEVEL = 168
+SUBLEVEL = 169
EXTRAVERSION =
NAME = "People's Front"
@@ -438,7 +438,7 @@ KBUILD_AFLAGS :=
I'm announcing the release of the 5.4.91 kernel.
All users of the 5.4 kernel series must upgrade.
The updated 5.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.4.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.19.169 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web browser
On Tue, Jan 19, 2021 at 07:56:10PM +0100, Cornelia Huck wrote:
> On Mon, 18 Jan 2021 14:16:26 -0400
> Jason Gunthorpe wrote:
>
> > On Mon, Jan 18, 2021 at 05:00:09PM +0100, Cornelia Huck wrote:
> >
> > > > You can say that all the HW specific things are in the mlx5_vfio_pci
> > > > driver. It is
On Tue, Jan 19, 2021 at 07:38:24PM +0900, Sergey Senozhatsky wrote:
> On (21/01/19 01:47), Matthew Wilcox wrote:
> [..]
> >
> > > So maybe DUMP_PREFIX_UNHASHED can do the unhashed dump only when
> > > CONFIG_DEBUG_KERNEL=y and fallback to DUMP_PREFIX_ADDRESS otherwise?
> >
> > Distros enable CONF
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 1e2a199f6ccdc15cf111d68d212e2fd4ce65682e
commit: 2f713615ddd9d805b6c5e79c52e0e11af99d2bf1 libceph: move msgr1 protocol
implementation to its own file
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If you fix the
On 1/19/21 1:45 PM, Kees Cook wrote:
How about this so the base address is hashed once, with the offset added
to it for each line instead of each line having a "new" hash that makes
no sense:
diff --git a/lib/hexdump.c b/lib/hexdump.c
index 9301578f98e8..20264828752d 100644
--- a/lib/hexdump.c
+
ig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a004-20210119
x86_64 randconfig-a006-20210119
x86_64 randconfig-a001-20210119
x86_64 randconfig-a003-20210
Doc comments only:
On 1/8/21 1:25 PM, mgr...@linux.intel.com wrote:
> diff --git a/Documentation/vpu/xlink-core.rst
> b/Documentation/vpu/xlink-core.rst
> new file mode 100644
> index ..1c471ec803d3
> --- /dev/null
> +++ b/Documentation/vpu/xlink-core.rst
> @@ -0,0 +1,81 @@
> +.. SPDX
On Tue, 19 Jan 2021 16:21:35 +0100 Andrew Lunn wrote:
> On Sat, Jan 16, 2021 at 04:13:22PM +, Alexander Lobakin wrote:
> > container_of() macro hides a local variable '__mptr' inside. This
> > becomes a problem when several container_of() are nested in each
> > other within single line or plain
Use an additional bit of the VFIO_DEVICE_INFO_CAP_ZPCI_GROUP flags
field to pass whether or not the associated device supports relaxed
length and alignment for some I/O operations.
Signed-off-by: Matthew Rosato
Acked-by: Niklas Schnelle
Reviewed-by: Pierre Morel
---
drivers/vfio/pci/vfio_pci_z
601 - 700 of 1354 matches
Mail list logo
