On 5/14/2020 7:56 AM, Eric W. Biederman wrote:
> Kees Cook writes:
>
>> On Tue, May 12, 2020 at 04:47:14PM -0700, Kees Cook wrote:
>>> And now I wonder if qemu actually uses the resulting AT_EXECFD ...
>> It does, though I'm not sure if this is to support crossing mount points,
>> dropping
How about this then?
David
---
commit fa37b6c7e2f86d16ede1e0e3cb73857152d51825
Author: David Howells
Date: Thu May 14 17:48:55 2020 +0100
keys: Move permissions checking decisions into the checking code
Overhaul the permissions checking, moving the decisions of which permits to
From: Bartosz Golaszewski
mdio-moxart doesn't use regulators in the driver code. We can remove
the regulator include.
Signed-off-by: Bartosz Golaszewski
---
drivers/net/phy/mdio-moxart.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/phy/mdio-moxart.c
On 5/14/2020 7:49 AM, Stanley Chu wrote:
Hi Asutosh,
On Thu, 2020-05-14 at 10:23 +0800, Stanley Chu wrote:
Hi Asutosh,
On Wed, 2020-05-13 at 12:31 -0700, Asutosh Das (asd) wrote:
On 5/12/2020 3:47 AM, Stanley Chu wrote:
Currently UFS host driver promises VCC supply if UFS device
needs to do
The commit "disregard Clause 22 registers present bit..." clears
the low bit of the devices_in_package data which is being used
in get_phy_c45_ids() to determine if a phy/register is responding
correctly. That check is against 0x1FFF, but since the low
bit is always cleared, the check can
On Thu 14 May 07:15 PDT 2020, Vinod Koul wrote:
> On 12-05-20, 17:54, Bjorn Andersson wrote:
> > In all modern Qualcomm platforms the mutex region of the TCSR is forked
> > off into its own block, all with a offset of 0 and stride of 4096. So
> > add support for directly memory mapping this
- On May 14, 2020, at 12:39 PM, Borislav Petkov b...@alien8.de wrote:
> On Thu, May 14, 2020 at 12:03:30PM -0400, Mathieu Desnoyers wrote:
>> - #MC triggered, queuing task work,
>> - unrelated signal happens to be delivered to task,
>> - exit to usermode loop handles do_signal first,
>> -
From: Michael Srba
This patch wires up display support on Samsung Galaxy A3 2015.
Signed-off-by: Michael Srba
---
.../qcom/msm8916-samsung-a2015-common.dtsi| 44 +++
.../boot/dts/qcom/msm8916-samsung-a3u-eur.dts | 54 +++
2 files changed, 98 insertions(+)
From: Robert Beckett
Avoid LDB and IPU DI clocks both using the same parent. LDB requires
pasthrough clock to avoid breaking timing while IPU DI does not.
Force IPU DI clocks to use IMX6QDL_CLK_PLL2_PFD0_352M as parent
and LDB to use IMX6QDL_CLK_PLL5_VIDEO_DIV.
This fixes an issue where
Hey Linus,
/* Summary */
This contains a single fix for all exported legacy fork helpers to block
accidental access to clone3() features in the upper 32 bits of their
respective flags arguments.
I got Cced on a glibc issue where someone reported consistent failures for
the legacy clone() syscall
Casey Schaufler writes:
> On 5/14/2020 7:56 AM, Eric W. Biederman wrote:
>> Kees Cook writes:
>>
>>> On Tue, May 12, 2020 at 04:47:14PM -0700, Kees Cook wrote:
And now I wonder if qemu actually uses the resulting AT_EXECFD ...
>>> It does, though I'm not sure if this is to support crossing
On Wed, 13 May 2020 15:05:47 -0500, Dan Murphy wrote:
> Add ALSA controls to configure the PDM clocks.
> The clocks need to be configurable to accommodate various microphones
> that use clocks for low power/low resolution modes to high power/high
> resolution modes.
Applied to
On Thu, 14 May 2020 07:33:36 -0500, Dan Murphy wrote:
> Add ALSA controls to configure the PDM clocks.
> The clocks need to be configurable to accommodate various microphones
> that use clocks for low power/low resolution modes to high power/high
> resolution modes.
Applied to
On Thu, May 14, 2020 at 06:59:38PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> mdio-moxart doesn't use regulators in the driver code. We can remove
> the regulator include.
>
> Signed-off-by: Bartosz Golaszewski
Reviewed-by: Andrew Lunn
Andrew
On 5/14/2020 8:01 AM, Stanley Chu wrote:
Currently UFS host driver promises VCC supply if UFS device
needs to do WriteBooster flush during runtime suspend.
However the UFS specification mentions,
"While the flushing operation is in progress, the device is
in Active power mode."
Therefore UFS
On 5/14/2020 9:58 AM, David Howells wrote:
> How about this then?
>
> David
> ---
> commit fa37b6c7e2f86d16ede1e0e3cb73857152d51825
> Author: David Howells
> Date: Thu May 14 17:48:55 2020 +0100
>
> keys: Move permissions checking decisions into the checking code
>
> Overhaul the
The of_find_device_by_node() helper has its dummy counterpart for when
CONFIG_OF is not enabled. However, it is clearly stated in the kernel
documentation that it "takes a reference to the embedded struct device
which needs to be dropped after use". Which means the of_dev_put()
helper might have
The kernel documentation of:
* bus_to_virt()
* memcpy_fromio()
* memcpy_toio()
refers to older parameters.
Update it to fit the actual names.
Signed-off-by: Miquel Raynal
---
include/asm-generic/io.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
On Tue 12 May 20:57 PDT 2020, Baolin Wang wrote:
> On Wed, May 13, 2020 at 8:55 AM Bjorn Andersson
> wrote:
> >
> > In all modern Qualcomm platforms the mutex region of the TCSR is forked
> > off into its own block, all with a offset of 0 and stride of 4096. So
> > add support for directly
On 17-04-20, 00:00, Bjorn Andersson wrote:
> Handle supply regulators for GDSCs to allow probe deferral when regulators are
> not yet present/enabled and to allow the GDSC to enable/disable dependencies
> as
> needed.
Reviewed-by: Vinod Koul
--
~Vinod
On 05-04-20, 23:00, Bjorn Andersson wrote:
> On some device the reset line for the UFS memory needs to be tickled in
> order for UFS to initialize properly, add this to the ufs_mem_hc node.
Reviewed-by: Vinod Koul
--
~Vinod
Hi Chun-Kuang,
On 14/5/20 18:44, Chun-Kuang Hu wrote:
> Hi, Enric:
>
> Enric Balletbo i Serra 於 2020年5月14日 週四
> 下午11:42寫道：
>>
>> Hi Chun-Kuang,
>>
>> On 14/5/20 16:28, Chun-Kuang Hu wrote:
>>> Hi, Enric:
>>>
>>> Enric Balletbo Serra 於 2020年5月14日 週四 上午12:41寫道：
Hi Chun-Kuang,
On 5/14/2020 9:59 AM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> mdio-moxart doesn't use regulators in the driver code. We can remove
> the regulator include.
>
> Signed-off-by: Bartosz Golaszewski
Reviewed-by: Florian Fainelli
--
Florian
On 05-04-20, 23:00, Bjorn Andersson wrote:
> On some device the reset line for the UFS memory needs to be tickled in
> order for UFS to initialize properly, add this to the ufs_mem_hc node.
Reviewed-by: Vinod Koul
--
~Vinod
On Thu, May 14, 2020 at 02:30:28PM +0300, Felipe Balbi wrote:
> Felipe Balbi writes:
>
> > Hi,
> >
> > Sandeep Maheswaram writes:
> >> +static int dwc3_qcom_interconnect_init(struct dwc3_qcom *qcom)
> >> +{
> >> + struct device *dev = qcom->dev;
> >> + int ret;
> >> +
> >> + if
On 17-10-19, 22:58, Bjorn Andersson wrote:
> Specify regulators and enable the node. The firmware uses the 8
> bit version of the host capability message, so specify this quirk.
Reviewed-by: Vinod Koul
--
~Vinod
On Wed, 13 May 2020 20:55:20 -0700 Wang Wenhu wrote:
> Make a substitution of kzalloc with devm_kzalloc to simplify the
> ipa_probe() process.
>
> Signed-off-by: Wang Wenhu
The code is perfectly fine as is. What problem are you trying to solve?
On Thu, May 14, 2020 at 08:46:18AM +0800, Boqun Feng wrote:
> On Wed, May 13, 2020 at 06:39:03AM +0900, Akira Yokosawa wrote:
> > From 96fa6680e3b990633ecbb6d11acf03a161b790bd Mon Sep 17 00:00:00 2001
> > From: Akira Yokosawa
> > Date: Sun, 10 May 2020 15:12:57 +0900
> > Subject: [PATCH RESEND
czw., 14 maj 2020 o 19:13 Florian Fainelli napisał(a):
>
>
>
> On 5/14/2020 9:59 AM, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski
> >
> > mdio-moxart doesn't use regulators in the driver code. We can remove
> > the regulator include.
> >
> > Signed-off-by: Bartosz Golaszewski
>
>
The host driver should decide whether to use SGLs or PRPs and they
currently assume the flags are cleared after the call to
nvme_setup_cmd(). However, passed-through commands may erroneously
set these bits; so clear them for all cases.
Signed-off-by: Logan Gunthorpe
Reviewed-by: Sagi Grimberg
On 22-04-20, 13:10, Robert Foss wrote:
> Add device treee support for the Qualcomm APQ8016 SBC, otherwise known as
> the Dragonboard 410c with the D3 mezzanine expansion board.
>
> The D3 mezzanine ships in a kit with a OmniVision 5640 sensor module,
> which is what this DT targets.
>
>
From: Chaitanya Kulkarni
This patch updates KConfig file for the NVMeOF target where we add new
option so that user can selectively enable/disable passthru code.
Signed-off-by: Chaitanya Kulkarni
[log...@deltatee.com: fixed some of the wording in the help message]
Signed-off-by: Logan
When CONFIG_NVME_TARGET_PASSTHRU as 'passthru' directory will
be added to each subsystem. The directory is similar to a namespace
and has two attributes: device_path and enable. The user must set the
path to the nvme controller's char device and write '1' to enable the
subsystem to use passthru.
Export nvme_put_ns(), nvme_command_effects(), nvme_execute_passthru_rq()
and nvme_find_get_ns() for use in the nvmet passthru code.
The exports are conditional on CONFIG_NVME_TARGET_PASSTHRU.
Based-on-a-patch-by: Chaitanya Kulkarni
Signed-off-by: Logan Gunthorpe
Reviewed-by: Max Gurtovoy
Separate the code to obtain command effects from the code
to start a passthru request and open code nvme_known_admin_effects()
in the new helper.
The new helper function will be necessary for nvmet passthru
code to determine if we need to change out of interrupt context
to handle the effects.
This is v13 of the passthru patchset which is mostly a resend of v12
with Sagi's reviewed-by tags collected.
Below, I'll reiterrate some points I made previously that haven't been
responded to:
I don't think cloning the ctrl_id or the subsysnqn is a good idea.
I sent an email trying to explain
This patch adds helper functions which are used in the NVMeOF configfs
when the user is configuring the passthru subsystem. Here we ensure
that only one subsys is assigned to each nvme_ctrl by using an xarray
on the cntlid.
The subsystem's version number is overridden by the passed through
Add passthru command handling capability for the NVMeOF target and
export passthru APIs which are used to integrate passthru
code with nvmet-core.
The new file passthru.c handles passthru cmd parsing and execution.
In the passthru mode, we create a block layer request from the nvmet
request and
Introduce a new nvme_execute_passthru_rq() helper which calls
nvme_passthru_[start|end]() around blk_execute_rq(). This ensures
all passthru calls (including nvme_submit_io()) will be wrapped
appropriately.
nvme_execute_passthru_rq() will also be useful for the nvmet passthru
code.
nvme_ctrl_get_by_path() is analagous to blkdev_get_by_path() except it
gets a struct nvme_ctrl from the path to its char dev (/dev/nvme0).
It makes use of filp_open() to open the file and uses the private
data to obtain a pointer to the struct nvme_ctrl. If the fops of the
file do not match,
On Thu 14 May 10:01 PDT 2020, michael.s...@seznam.cz wrote:
> From: Michael Srba
>
> This patch wires up display support on Samsung Galaxy A3 2015.
>
> Signed-off-by: Michael Srba
>
> ---
> .../qcom/msm8916-samsung-a2015-common.dtsi| 44 +++
>
On Wed, 13 May 2020 17:39:21 +0300, Matti Vaittinen wrote:
> The BD71837 had a HW "feature" where changing the regulator output
> voltages of other regulators but bucks 1-4 might cause spikes if
> regulators were enabled. Thus SW prohibit voltage changes for other
> regulators except for bucks 1-4
On Thu, May 14, 2020 at 06:01:52PM +0200, Andrew Lunn wrote:
> On Thu, May 14, 2020 at 03:47:16PM +, Christian Herber wrote:
> > Hi Andrew,
> >
> > > On Wed, May 13, 2020 at 03:39:00PM +0200, Andrew Lunn wrote:
> > >> On Thu, May 14, 2020 at 02:09:59PM +0200, Oleksij Rempel wrote:
> > >>
On Thu, 14 May 2020, Jeremy Cline wrote:
> A number of userspace tools, such as systemtap, need a way to see the
> current lockdown state so they can gracefully deal with the kernel being
> locked down. The state is already exposed in
> /sys/kernel/security/lockdown, but is only readable by root.
Mathieu Desnoyers writes:
> - On May 5, 2020, at 9:49 AM, Thomas Gleixner t...@linutronix.de wrote:
>> +
>> +static __always_inline void debug_exit(unsigned long dr7)
>> +{
>> +set_debugreg(dr7, 7);
>> +}
>
> Out of curiosity, what prevents the compiler from moving instructions
> outside
On Thu, 14 May 2020 20:41:21 +0800 Huazhong Tan wrote:
> This patchset adds some cleanups for the HNS3 ethernet driver.
You may want to spell out 'state' instead of 'stat' in patch 3, stat is
often used as abbreviation of statistic. But that's a nit pick, up to
you:
Reviewed-by: Jakub Kicinski
On 5/14/2020 10:20 AM, Bartosz Golaszewski wrote:
> czw., 14 maj 2020 o 19:13 Florian Fainelli napisał(a):
>>
>>
>>
>> On 5/14/2020 9:59 AM, Bartosz Golaszewski wrote:
>>> From: Bartosz Golaszewski
>>>
>>> mdio-moxart doesn't use regulators in the driver code. We can remove
>>> the regulator
On 5/14/20 10:08 AM, Miquel Raynal wrote:
> The kernel documentation of:
> * bus_to_virt()
> * memcpy_fromio()
> * memcpy_toio()
> refers to older parameters.
>
> Update it to fit the actual names.
>
> Signed-off-by: Miquel Raynal
> ---
> include/asm-generic/io.h | 16
> 1
* Pavel Machek [200513 19:10]:
> Hi!
>
> > Here's the updated set of these patches fixed up for Johan's and
> > Pavel's earlier comments.
> >
> > This series does the following:
> >
> > 1. Adds functions to n_gsm.c for serdev-ngsm.c driver to use
> >
> > 2. Adds a generic serdev-ngsm.c driver
On Thu, 14 May 2020, Mickaël Salaün wrote:
> > This needs to be converted to the LSM API via superblock blob stacking.
> >
> > See Casey's old patch:
> > https://lore.kernel.org/linux-security-module/20190829232935.7099-2-ca...@schaufler-ca.com/
>
> s_landlock_inode_refs is quite similar to
On 14-05-20, 10:00, Bjorn Andersson wrote:
> On Thu 14 May 07:15 PDT 2020, Vinod Koul wrote:
>
> > On 12-05-20, 17:54, Bjorn Andersson wrote:
> > > In all modern Qualcomm platforms the mutex region of the TCSR is forked
> > > off into its own block, all with a offset of 0 and stride of 4096. So
>
Hi again,
On 14/5/20 19:12, Enric Balletbo i Serra wrote:
> Hi Chun-Kuang,
>
> On 14/5/20 18:44, Chun-Kuang Hu wrote:
>> Hi, Enric:
>>
>> Enric Balletbo i Serra 於 2020年5月14日 週四
>> 下午11:42寫道：
>>>
>>> Hi Chun-Kuang,
>>>
>>> On 14/5/20 16:28, Chun-Kuang Hu wrote:
Hi, Enric:
Enric
On Mon, May 11, 2020 at 10:34 AM Paolo Bonzini wrote:
>
> Hi Jonathan, I think the remaining sticky point is this one:
Apologies it took a couple days for me to respond; I wanted to finish
evaluating our current usage to make sure I had a full picture; I'll
summarize our state at the bottom.
>
Mathieu Desnoyers writes:
> - On May 5, 2020, at 9:16 AM, Thomas Gleixner t...@linutronix.de wrote:
>
>> From: Peter Zijlstra
>>
>
> Patch title: singal -> signal.
>
>> Convert #MC over to using task_work_add(); it will run the same code
>> slightly later, on the return to user path of the
Hello
The DP83822 Ethernet PHY has the ability to connect via a Fiber port. The
DP83825 or DP83826 do not have this ability. In order to keep the same
driver the DP83822 and the 825/826 phy_driver call backs need to be changed
so that the DP83822 has it's own call back for config_init and adds
The DP83822 can be configured to use a Fiber connection. The strap
register is read to determine if the device has been configured to use
a fiber connection. With the fiber connection the PHY can be configured
to detect whether the fiber connection is active by either a high signal
or a low
Add a dt binding for the TI dp83822 ethernet phy device.
CC: Rob Herring
Signed-off-by: Dan Murphy
---
.../devicetree/bindings/net/ti,dp83822.yaml | 49 +++
1 file changed, 49 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/ti,dp83822.yaml
diff --git
- On May 14, 2020, at 1:38 PM, Thomas Gleixner t...@linutronix.de wrote:
> Mathieu Desnoyers writes:
>> - On May 5, 2020, at 9:16 AM, Thomas Gleixner t...@linutronix.de wrote:
>>
>>> From: Peter Zijlstra
>>>
>>
>> Patch title: singal -> signal.
>>
>>> Convert #MC over to using
On Thu, May 14, 2020 at 04:25:35PM +0200, Bartlomiej Zolnierkiewicz wrote:
> Thank you for in-detail explanations, for this patch:
>
> Acked-by: Bartlomiej Zolnierkiewicz
>
> Could you also please take care of adding missing checks for {get,put}_user()
> failures later?
Umm... OK; put_user()
On 14/05/20 19:35, Jonathan Adams wrote:
>> In general for statsfs we took a more explicit approach where each
>> addend in a sum is a separate stats_fs_source. In this version of the
>> patches it's also a directory, but we'll take your feedback and add both
>> the ability to hide directories
Hi,
On Thu, May 14, 2020 at 9:30 AM Matthias Kaehlcke wrote:
>
> Hi Abhishek,
>
> On Wed, May 13, 2020 at 08:41:25PM -0700, Abhishek Pandit-Subedi wrote:
> > WCN3991 supports transparent WBS (host encoded mSBC). Add a flag to the
> > device match data to show WBS is supported.
>
> In general
- On May 14, 2020, at 1:28 PM, Thomas Gleixner t...@linutronix.de wrote:
> Mathieu Desnoyers writes:
>> - On May 5, 2020, at 9:49 AM, Thomas Gleixner t...@linutronix.de wrote:
>>> +
>>> +static __always_inline void debug_exit(unsigned long dr7)
>>> +{
>>> + set_debugreg(dr7, 7);
>>> +}
On Wed, 13 May 2020, Alexei Starovoitov wrote:
> On Tue, May 12, 2020 at 06:56:38AM +0100, Alan Maguire wrote:
> > The printk family of functions support printing specific pointer types
> > using %p format specifiers (MAC addresses, IP addresses, etc). For
> > full details see
On Thu, May 14, 2020 at 11:35 AM Christophe Kerello
wrote:
>
> Hi Rob,
>
> On 5/14/20 5:00 PM, Rob Herring wrote:
> > On Wed, May 06, 2020 at 11:11:15AM +0200, Christophe Kerello wrote:
> >> These bindings can be used on SOCs where the FMC2 NAND controller is
> >> in standalone. In case that the
On Thu, May 14, 2020 at 8:04 AM Arnaldo Carvalho de Melo
wrote:
>
> Em Thu, Mar 05, 2020 at 11:11:10PM -0800, Ian Rogers escreveu:
> > Allow the CC compiler to accept a CFLAGS environment variable.
> > Make the architecture test directory agree with the code comment.
> > This doesn't change the
Good morning Sai,
On Thu, May 14, 2020 at 04:29:15PM +0530, Sai Prakash Ranjan wrote:
> From: Tingwei Zhang
>
> On some Qualcomm Technologies Inc. SoCs like SC7180, there
> exists a hardware errata where the APSS (Application Processor
> SubSystem)/CPU watchdog counter is stopped when ETM
During the initialization process, ipmr_new_table() is called
to create new tables which in turn calls ipmr_get_table() which
traverses net->ipv4.mr_tables without holding the writer lock.
However, this is safe to do so as no tables exist at this time.
Hence add a suitable lockdep expression to
ipmr_for_each_table() macro uses list_for_each_entry_rcu()
for traversing outside of an RCU read side critical section
but under the protection of rtnl_mutex. Hence, add the
corresponding lockdep expression to silence the following
false-positive warning at boot:
[4.319347]
On Thu, May 14, 2020 at 10:09:03AM -0500, Rob Herring wrote:
> On Wed, 6 May 2020 20:42:19 +0300, wrote:
> > From: Serge Semin
> >
> > It's a Cluster Power Controller embedded into the MIPS IP cores.
> > Currently the corresponding dts node is supposed to have compatible
> > and reg properties.
No functional change intended. We will need to analyze slot information
to map PTEs for KVM_MEM_ALLONES slots aggressively.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/kvm/mmu/mmu.c | 14 --
arch/x86/kvm/mmu/paging_tmpl.h | 7 +--
2 files changed, 13 insertions(+), 8
Test the newly introduced KVM_MEM_ALLONES memslots:
- Reads from all pages return '0xff'
- Writes to all pages cause KVM_EXIT_MMIO
Signed-off-by: Vitaly Kuznetsov
---
tools/testing/selftests/kvm/Makefile | 1 +
.../testing/selftests/kvm/include/kvm_util.h | 1 +
The idea of the patchset was suggested by Michael S. Tsirkin.
PCIe config space can (depending on the configuration) be quite big but
usually is sparsely populated. Guest may scan it by accessing individual
device's page which, when device is missing, is supposed to have 'pci
holes' semantics:
On Thu, May 14, 2020 at 10:09:43AM -0500, Rob Herring wrote:
> On Wed, 6 May 2020 20:42:20 +0300, wrote:
> > From: Serge Semin
> >
> > It's a Common Device Memory Map controller embedded into the MIPS IP
> > cores, which dts node is supposed to have compatible and reg properties.
> >
> >
All PTEs in KVM_MEM_ALLONES slots point to the same read-only page
in KVM so instead of mapping each page upon first access we can map
everything aggressively.
Suggested-by: Michael S. Tsirkin
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/kvm/mmu/mmu.c | 20 ++--
Label names in kvm_init() are horrible, rename them to make it obvious
what we are going to do on the failure path.
Signed-off-by: Vitaly Kuznetsov
---
virt/kvm/kvm_main.c | 33 -
1 file changed, 16 insertions(+), 17 deletions(-)
diff --git a/virt/kvm/kvm_main.c
PCIe config space can (depending on the configuration) be quite big but
usually is sparsely populated. Guest may scan it by accessing individual
device's page which, when device is missing, is supposed to have 'pci
holes' semantics: reads return '0xff' and writes get discarded. Currently,
On Wed, 13 May 2020 22:24:56 -0400 (EDT)
Mathieu Desnoyers wrote:
> Also, considering that "inline" is not sufficient to ensure the compiler
> does not emit a traceable function, I suspect you'll also want to mark
> "native_get_debugreg" and "native_set_debugreg" always inline as well.
I was
> On May 14, 2020, at 2:29 AM, Lorenzo Pieralisi
> wrote:
>
> Please update the subject:
>
> Subject: "ACPI/IORT: Fix PMCG node single ID mapping handling"
>
> On Wed, May 13, 2020 at 05:12:02PM -0700, Tuan Phan wrote:
>> PMCG node can have zero ID mapping if its overflow interrupt
>> is
On 2020-05-07 13:21, Bjorn Andersson wrote:
On Thu 16 Apr 11:38 PDT 2020, Rishabh Bhatnagar wrote:
This patch adds the inline coredump functionality. The current
coredump implementation uses vmalloc area to copy all the segments.
But this might put a lot of strain on low memory targets as the
On Thu, May 14, 2020 at 10:05 AM Christian Brauner
wrote:
>
> This contains a single fix for all exported legacy fork helpers to block
> accidental access to clone3() features in the upper 32 bits of their
> respective flags arguments.
I've taken this pull, but I really think the minimal and
On Thu, May 14, 2020 at 08:24:54AM -0400, Qian Cai wrote:
>
>
> > On May 14, 2020, at 7:37 AM, syzbot
> > wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: c9529331 Add linux-next specific files f
Hi Babu,
Thank you very much for taking a look.
On 5/14/2020 9:45 AM, Babu Moger wrote:
> Hi Reinnette,
>
> The patches did not apply on my tree. I got the latest tree today. You
Which tree did you use as baseline? These patches should apply cleanly
on top of the other resctrl patches already
On Thu, May 14, 2020 at 11:46:23AM -0400, Qian Cai wrote:
>
>
> > On May 14, 2020, at 11:34 AM, Paul E. McKenney wrote:
> >
> > On Thu, May 14, 2020 at 10:03:21AM -0400, Qian Cai wrote:
> >>
> >>
> >>> On May 14, 2020, at 9:54 AM, Paul E. McKenney wrote:
> >>>
> >>> On Thu, May 14, 2020 at
Rob,
Could you also take a look at this patch? There are several patchsets I've sent
which depend on the vendor-prefix it defines. So when you get to check those
patchsets DT files, the dt_binding_check will fail without it. Is it possible
somehow to pick this patch up from here and apply it
From: Colin Ian King
Currently ldo_pwr has the LDO25 voltage bits set to zero and then
it is overwritten with the new voltage setting. The assignment
looks incorrect, it should be bit-wise or'ing in the new voltage
setting rather than a direct assignment.
Addresses-Coverity: ("Unused value")
Vivek Goyal writes:
> On Mon, May 11, 2020 at 06:47:44PM +0200, Vitaly Kuznetsov wrote:
>> Concerns were expressed around (ab)using #PF for KVM's async_pf mechanism,
>> it seems that re-using #PF exception for a PV mechanism wasn't a great
>> idea after all. The Grand Plan is to switch to using
Hi folks,
On Tue, May 12, 2020 at 04:41:54PM +0300, Heikki Krogerus wrote:
> Hi guys,
>
> On Mon, May 11, 2020 at 01:46:35PM -0700, Prashant Malani wrote:
> > Hi Rob,
> >
> > Thank you for reviewing the patch. Kindly see my comments inline:
> >
> > On Mon, May 11, 2020 at 02:28:00PM -0500, Rob
From: Colin Ian King
Variable conn is not initialized and can potentially contain
garbage causing a false -EPERM return on the !conn check.
Fix this by initializing it to false.
Addresses-Coverity: ("Uninitialized scalar variable")
Fixes: f2494de388bd ("fsinfo: Add an attribute that lists all
Hi,
On Wed, May 13, 2020 at 8:35 PM Ravi Kumar Bokka (Temp)
wrote:
>
> Hi doug,
>
> Thanks for your feedback. Please find below inline comments.
Probably the mailing list didn't see them. You responded with HTML
mail. Please be careful to only respond in plain text.
> Regards,
>
> Ravi
Hi,
I notice that you didn't respond to any of my feedback [1], only
Srinivas's. Any reason why? It turns out that Srinivas had quite a
lot of the same feedback as I did, but please make sure you didn't
miss anything I suggested. More inline below.
On Thu, May 14, 2020 at 5:26 AM Ravi Kumar
On May 14, 2020 8:07:59 PM GMT+02:00, Linus Torvalds
wrote:
>On Thu, May 14, 2020 at 10:05 AM Christian Brauner
> wrote:
>>
>> This contains a single fix for all exported legacy fork helpers to
>block
>> accidental access to clone3() features in the upper 32 bits of their
>> respective flags
On Mon, Apr 06, 2020 at 05:11:34PM +0530, Amol Grover wrote:
> Hello,
>
> With respect to the patch https://lore.kernel.org/patchwork/patch/1202512/
> I boot tested with CONFIG_PROVE_RCU_LIST=y and encountered a susppicious RCU
> usage warning in "security/apparmor/include/lib.h". I thought of
On 2020-05-11 21:22, Anshuman Khandual wrote:
Add the following new trace events which will help in validating migration
events involving PMD based THP pages.
1. THP_PMD_MIGRATION_ENTRY_SET
2. THP_PMD_MIGRATION_ENTRY_REMOVE
There are no clear method to confirm whether a THP migration happened
On Wed, 6 May 2020 20:42:21 +0300, wrote:
> From: Serge Semin
>
> Add "BAIKAL ELECTRONICS, JSC" to the list of devicetree vendor prefixes
> as "baikal".
>
> Website: http://www.baikalelectronics.com
>
> Signed-off-by: Serge Semin
> Cc: Alexey Malahov
> Cc: Thomas Bogendoerfer
> Cc: Paul
From: Colin Ian King
Currently burst is clamping on rate and not burst, the assignment
of burst from the clamping discards the previous assignment of burst.
This looks like a cut-n-paste error from the previous clamping
calculation on ramp. Fix this by replacing ramp with burst.
On Thu, May 14, 2020 at 11:22 AM Christian Brauner
wrote:
>
> Seemed weird to me to change something that's been exposed to userspace for
> that long.
Well, the internal declarations aren't actually "exposed" to user
space - it's not like it's the declaration of the system call, that's
The following commit has been merged into the x86/splitlock branch of tip:
Commit-ID: 0ed7bf1d92eafc37bb9eb7c8692a8e44d24f9b99
Gitweb:
https://git.kernel.org/tip/0ed7bf1d92eafc37bb9eb7c8692a8e44d24f9b99
Author:Fenghua Yu
AuthorDate:Thu, 30 Apr 2020 16:46:35 -07:00
On Thu, May 14, 2020 at 12:30:54PM -0500, Dan Murphy wrote:
> Add a dt binding for the TI dp83822 ethernet phy device.
>
> CC: Rob Herring
> Signed-off-by: Dan Murphy
> ---
> .../devicetree/bindings/net/ti,dp83822.yaml | 49 +++
> 1 file changed, 49 insertions(+)
> create
On 5/13/20 4:59 PM, Eric W. Biederman wrote:
> Careful with your terminology. ELF sections are for .o's For
> executables ELF have segments. And reading through the code it is the
> program segments that are independently relocatable.
Sorry, I have trouble keeping this stuff straight when it's
Hi Mathieu,
On 2020-05-14 23:30, Mathieu Poirier wrote:
Good morning Sai,
On Thu, May 14, 2020 at 04:29:15PM +0530, Sai Prakash Ranjan wrote:
From: Tingwei Zhang
On some Qualcomm Technologies Inc. SoCs like SC7180, there
exists a hardware errata where the APSS (Application Processor
1 - 100 of 1589 matches
Mail list logo
