>-Original Message-
>From: Ulf Hansson
>Sent: Thursday, December 17, 2020 10:42 PM
>To: Bhaskara Budiredla
>Cc: Kees Cook ; Colin Cross
>; Tony Luck ; Sunil Kovvuri
>Goutham ; linux-...@vger.kernel.org; Linux
>Kernel Mailing List ; Christoph Hellwig
>
>Subject: Re: [EXT] Re: [PATCH
On Thu, Dec 17, 2020 at 12:55:39PM -0800, Dave Hansen wrote:
> On 11/6/20 3:29 PM, ira.we...@intel.com wrote:
> > + /* Arm for context switch test */
> > + write(fd, "1", 1);
> > +
> > + /* Context switch out... */
> > + sleep(4);
> > +
> > + /*
On Thu, Dec 17, 2020 at 03:50:55PM +0100, Thomas Gleixner wrote:
> On Fri, Nov 06 2020 at 15:29, ira weiny wrote:
> > --- a/arch/x86/kernel/process.c
> > +++ b/arch/x86/kernel/process.c
> > @@ -43,6 +43,7 @@
> > #include
> > #include
> > #include
> > +#include
> >
> > #include
Linux VM on Hyper-V crashes with the latest mainline:
[4.069624] detected buffer overflow in strcpy
[4.077733] kernel BUG at lib/string.c:1149!
..
[4.085819] RIP: 0010:fortify_panic+0xf/0x11
...
[4.085819] Call Trace:
[4.085819] acpi_device_add.cold.15+0xf2/0xfb
[
On Thu, Dec 17, 2020 at 7:53 AM Matthew Wilcox wrote:
>
> On Thu, Dec 17, 2020 at 10:03:11AM +0800, Xiangyang Yu wrote:
> > Fixed the warning when building with warnings enabled (W=1),
> > This function is only used in filemap.c, so mark this function
> > with 'static'.
>
> Good grief, no. Look
On Thu, Dec 17, 2020 at 12:41:50PM -0800, Dave Hansen wrote:
> On 11/6/20 3:29 PM, ira.we...@intel.com wrote:
> > void disable_TSC(void)
> > @@ -644,6 +668,8 @@ void __switch_to_xtra(struct task_struct *prev_p,
> > struct task_struct *next_p)
> >
> > if ((tifp ^ tifn) & _TIF_SLD)
> >
On 17-12-20, 10:55, Catalin Marinas wrote:
> Hi Viresh,
>
> On Thu, Dec 17, 2020 at 01:27:32PM +0530, Viresh Kumar wrote:
> > On 15-12-20, 11:04, Viresh Kumar wrote:
> > > Every time I have stumbled upon this routine, I get confused with the
> > > way 'have_policy' is used and I have to dig in to
pneigh_enqueue() tries to obtain a random delay by mod
NEIGH_VAR(p, PROXY_DELAY). However, NEIGH_VAR(p, PROXY_DELAY)
migth be zero at that point because someone could write zero
to /proc/sys/net/ipv4/neigh/[device]/proxy_delay after the
callers check it.
This patch double-checks NEIGH_VAR(p,
On 12/17/20 7:20 PM, Alexei Starovoitov wrote:
On Thu, Dec 17, 2020 at 09:26:09AM -0800, Yonghong Song wrote:
On 12/17/20 7:31 AM, Florent Revest wrote:
On Mon, Dec 14, 2020 at 7:47 AM Yonghong Song wrote:
On 12/11/20 6:40 AM, Florent Revest wrote:
On Wed, Dec 2, 2020 at 10:18 PM
BeagleBoard.org [0] currently uses an out-of-tree driver called
bone-pinmux-helper [1] developed by Pantelis Antoniou [2] back in 2013.
The driver assists users of our BeagleBone and PocketBeagle boards in
rapid prototyping by allowing them to change at run-time between defined
set of pinctrl
Hi Catalin,
Thanks for your explanation.
> > so there is two points
> > 1. out-of-tree function can't be approved
> > I totally agree with this :) so we may have a driver upstream in the
> > future.
>
> It may not be upstreamable if it relies on the old APM interface ;).
>
> > 2. APM
[+Cc Bjorn, Alan and linux-pci]
On Thu, Dec 17, 2020 at 12:57 AM Takashi Iwai wrote:
>
> On Wed, 16 Dec 2020 17:22:17 +0100,
> Takashi Iwai wrote:
> >
> > On Wed, 16 Dec 2020 17:07:45 +0100,
> > Kai-Heng Feng wrote:
> > >
> > > On Wed, Dec 16, 2020 at 11:58 PM Takashi Iwai wrote:
> > > >
> > >
On 12/15/20 7:46 AM, Marc Zyngier wrote:
> On 2020-12-15 15:39, Guenter Roeck wrote:
>> On 12/15/20 7:26 AM, Marc Zyngier wrote:
>>> On 2020-12-15 15:21, Guenter Roeck wrote:
Hi Marc,
On 12/15/20 2:19 AM, Marc Zyngier wrote:
> Hi Gunter,
>
> On 2020-12-15 00:21, Guenter
syzbot is feeding invalid superblock data to JFS for mount testing.
JFS does not check several of the fields -- just assumes that they
are good since the JFS_MAGIC and version fields are good.
In this case (syzbot reproducer), we have s_l2bsize == 0xda0c,
pad == 0xf045, and s_state == 0x50, all
On 2020/12/18 上午9:51, Zou Wei wrote:
Fix the following sparse warning:
drivers/vdpa/vdpa_sim/vdpa_sim_net.c:36:4: warning: symbol 'macaddr_buf' was
not declared. Should it be static?
Reported-by: Hulk Robot
Signed-off-by: Zou Wei
---
drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 2 +-
1 file
Hi all,
News: there will be no linux-next releases between Dec 24 and Jan
3 inclusive.
Please do not add any v5.12 destined code to your linux-next included
branches until after v5.11-rc1 has been released.
Changes since 20201217:
The ext4 tree gained a conflict against Linus' tree
On Tue, Dec 15, 2020 at 07:33:40PM +0200, Andy Shevchenko wrote:
> On Tue, Dec 15, 2020 at 6:44 PM Calvin Johnson
> wrote:
> >
> > Introduce fwnode_mdiobus_register_phy() to register PHYs on the
> > mdiobus. From the compatible string, identify whether the PHY is
> > c45 and based on this create
On 12/12/2020 3:45 AM, Douglas Anderson wrote:
In Linux, if a driver does disable_irq() and later does enable_irq()
on its interrupt, I believe it's expecting these properties:
* If an interrupt was pending when the driver disabled then it will
still be pending after the driver re-enables.
On Tue, Dec 15, 2020 at 07:53:26PM +0200, Andy Shevchenko wrote:
> On Tue, Dec 15, 2020 at 6:44 PM Calvin Johnson
> wrote:
> >
> > Introduce fwnode_mdiobus_register() to register PHYs on the mdiobus.
> > If the fwnode is DT node, then call of_mdiobus_register().
> > If it is an ACPI node, then:
On 2020-12-14 22:32, Bean Huo wrote:
On Sun, 2020-12-13 at 19:41 -0800, Can Guo wrote:
Fixes: 88a92d6ae4fe ("scsi: ufs: Serialize eh_work with system PM
events and async scan")
Signed-off-by: Can Guo
---
drivers/scsi/ufs/ufshcd.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
On Tue, Dec 15, 2020 at 07:55:01PM +0200, Andy Shevchenko wrote:
> On Tue, Dec 15, 2020 at 6:44 PM Calvin Johnson
> wrote:
> >
> > fwnode_mdiobus_register() internally takes care of both DT
> > and ACPI cases to register mdiobus. Replace existing
> > of_mdiobus_register() with
On Fri, Dec 18, 2020 at 05:18:16AM +0800, Young Hsieh wrote:
> Hi Greg,
>
> Thanks. I am looking for the Essential, RAS & Perf patches for AMD Milan as
> follows:
>
I don't see anything here :(
> I am not familiar the rules for stable kernel patches, can you help to
> elaborate ? Thanks
On 2020-12-16 21:16, Stanley Chu wrote:
hba->devfreq is zero-initialized thus it is not required
to check its existence in ufshcd_add_lus() function which
is invoked during initialization only.
Signed-off-by: Stanley Chu
---
drivers/scsi/ufs/ufshcd.c | 14 ++
1 file changed, 6
Hi all,
Commits
ee04fe87f4d0 ("cifs: Re-indent cifs_swn_reconnect()")
2c6dd2f9742d ("cifs: Unlock on errors in cifs_swn_reconnect()")
fb2356b3739b ("cifs: Delete a stray unlock in cifs_swn_reconnect()")
are missing a Signed-off-by from their author.
This is the problem with the mailing
On 2020/12/18 11:10, Dan Williams wrote:
> On Fri, Nov 20, 2020 at 1:23 AM Zhen Lei wrote:
>>
>> Swap the calling sequence of krealloc() and __request_region(), call the
>> latter first. In this way, the value of dev_dax->nr_range does not need to
>> be considered when __request_region()
Since commit 5fe71d271df8 ("irqchip/gic-v3-its: Tag ITS device as shared if
allocating for a proxy device"), some of the devices are wrongly marked as
"shared" by the ITS driver on systems equipped with the ITS(es). The
problem is that the @info->flags may not be initialized anywhere and we end
up
I have now amended the patches to have the correct author and repushed
On Thu, Dec 17, 2020 at 11:57 PM Stephen Rothwell wrote:
>
> Hi all,
>
> Commits
>
> ee04fe87f4d0 ("cifs: Re-indent cifs_swn_reconnect()")
> 2c6dd2f9742d ("cifs: Unlock on errors in cifs_swn_reconnect()")
> fb2356b3739b
On 2020-12-16 21:16, Stanley Chu wrote:
Cancelling suspend_work and resume_work is only required while
suspending clk-scaling. Thus moving these two invokes into
ufshcd_suspend_clkscaling() function.
Signed-off-by: Stanley Chu
---
drivers/scsi/ufs/ufshcd.c | 17 ++---
1 file
On 2020/11/20 17:22, Zhen Lei wrote:
> Swap the calling sequence of krealloc() and __request_region(), call the
> latter first. In this way, the value of dev_dax->nr_range does not need to
> be considered when __request_region() failed.
>
> Signed-off-by: Zhen Lei
> ---
> drivers/dax/bus.c |
On 2020-12-16 21:16, Stanley Chu wrote:
hba->devfreq is zero-initialized thus it is not required
to check its existence in ufshcd_add_lus() function which
is invoked during initialization only.
Signed-off-by: Stanley Chu
---
drivers/scsi/ufs/ufshcd.c | 14 ++
1 file changed, 6
When mounting a cgroup hierarchy with disabled controller in cgroup v1,
all available controllers will be attached.
Add disabled controller check in cgroup1_parse_param() and return directly
if the specified controller is disabled.
Signed-off-by: Chen Zhou
---
Changes in v2:
- Fix line over 80
Hi Laurent,
Thanks for reviewing.
On Tue, Dec 15, 2020 at 07:00:28PM +0200, Laurent Pinchart wrote:
> Hi Calvin,
>
> Thank you for the patch.
>
> On Tue, Dec 15, 2020 at 10:13:11PM +0530, Calvin Johnson wrote:
> > Using fwnode_get_id(), get the reg property value for DT node
> > and get the
On Tue, Dec 15, 2020 at 07:45:16PM +0200, Andy Shevchenko wrote:
> On Tue, Dec 15, 2020 at 6:44 PM Calvin Johnson
> wrote:
> >
> > Using fwnode_get_id(), get the reg property value for DT node
> > and get the _ADR object value for ACPI node.
>
> and -> or
>
> ...
>
> > +/**
> > + *
On 2020-12-16 21:16, Stanley Chu wrote:
Manipulate clock scaling related stuff only if the host capability
supports clock scaling feature to avoid redundant code execution.
Signed-off-by: Stanley Chu
---
drivers/scsi/ufs/ufshcd.c | 64 ---
1 file changed,
On 2020-12-16 21:16, Stanley Chu wrote:
Fix build warnings as below due to incorrect function description
of ufshcd_try_to_abort_task().
ufshcd.c:6651: warning: Function parameter or member 'hba' not
described in 'ufshcd_try_to_abort_task'
ufshcd.c:6651: warning: Function parameter or member
On 2020-12-16 21:16, Stanley Chu wrote:
Hi,
This series cleans up and refactors clk-scaling feature, and shall not
change any functionality.
This series is based on Can's series "Three changes related with UFS
clock scaling" in 5.10/scsi-fixes branch in Martin's tree.
Hi Stanley,
Thanks for
On server-class POWER machines, we don't need the SWIOTLB unless we're a
secure VM. Nevertheless, if CONFIG_SWIOTLB is enabled we unconditionally
allocate it.
In most cases this is harmless, but on a few machine configurations (e.g.,
POWER9 powernv systems with 4 GB area reserved for crashdump
Since the [start, end) is a half-open interval, a range with the end equal
to the start of another range should not be considered as overlapped.
Signed-off-by: Jiahui Cen
---
lib/logic_pio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/logic_pio.c b/lib/logic_pio.c
Hi Can,
On Fri, 2020-12-18 at 14:20 +0800, Can Guo wrote:
> On 2020-12-16 21:16, Stanley Chu wrote:
> > Hi,
> > This series cleans up and refactors clk-scaling feature, and shall not
> > change any functionality.
> >
> > This series is based on Can's series "Three changes related with UFS
> >
On 12/17/20 2:01 PM, Rob Herring wrote:
[...]
+#ifdef CONFIG_IMA_KEXEC
+/**
+ * arch_ima_add_kexec_buffer - do arch-specific steps to add the IMA buffer
+ *
+ * @image: kimage struct to set IMA buffer data
+ * @load_addr: Starting address where IMA buffer is loaded at
+ * @size: Number of
On 2020-12-15 13:43, Stanley Chu wrote:
Hi Can,
On Sun, 2020-12-13 at 08:31 -0800, Can Guo wrote:
In contexts like suspend, shutdown and error handling, we need to
suspend
devfreq to make sure these contexts won't be disturbed by clock
scaling.
However, suspending devfreq is not enough since
On 2020-12-18 14:24, Stanley Chu wrote:
Hi Can,
On Fri, 2020-12-18 at 14:20 +0800, Can Guo wrote:
On 2020-12-16 21:16, Stanley Chu wrote:
> Hi,
> This series cleans up and refactors clk-scaling feature, and shall not
> change any functionality.
>
> This series is based on Can's series "Three
On 16. 12. 20, 13:07, kernel test robot wrote:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: d01e7f10dae29eba0f9ada82b65d24e035d5b2f9
commit: 07edff9265204e15c9fc8d07cc69e38c4c484e15 vt: keyboard, reorder user
buffer handling in vt_do_kdgkb_ioctl
Reported-by: kernel test robot
Signed-off-by: kernel test robot
---
core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 4cc0303611650c..4e15193aafad6a 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@
Hi Saravana,
I love your patch! Perhaps something to improve:
[auto build test WARNING on driver-core/driver-core-testing]
[also build test WARNING on linus/master next-20201217]
[cannot apply to linux/master v5.10]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
Hi Jens,
On Thu, Dec 17, 2020 at 6:44 PM swapnil ingle wrote:
>
> Adding linux-r...@vger.kernel.org
>
> On Fri, Nov 27, 2020 at 1:54 PM Danil Kipnis
> wrote:
>>
>> On Fri, Nov 27, 2020 at 1:31 PM Swapnil Ingle wrote:
>> >
>> > Adding name to the Contributors List
>> >
>> > Signed-off-by:
Hi Saravana,
I love your patch! Perhaps something to improve:
[auto build test WARNING on driver-core/driver-core-testing]
[also build test WARNING on linus/master next-20201217]
[cannot apply to linux/master v5.10]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
On 17.12.20 19:25, Andrew Cooper wrote:
On 16/12/2020 08:21, Jürgen Groß wrote:
On 15.12.20 21:59, Andrew Cooper wrote:
On 15/12/2020 11:10, Juergen Gross wrote:
In case a process waits for any Xenstore action in the xenbus driver
it should be interruptible by signals.
Signed-off-by: Juergen
The OF match table is only used when OF is enabled.
Fixes: cd3f609823a5 ("Input: new da7280 haptic driver")
Reported-by: kernel test robot
Signed-off-by: Dmitry Torokhov
---
drivers/input/misc/da7280.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/input/misc/da7280.c
Hi Jiri,
On Thu, Dec 17, 2020 at 12:22:17PM +0100, Jiri Kosina wrote:
> On Sat, 5 Dec 2020, Dmitry Torokhov wrote:
>
> > The driver has its own HID descriptor parsing code, that had and still
> > has several issues discovered by syzbot and other tools. Ideally we
> > should move the driver over
Hi,
[adding linux-mm]
On 12/16/20 1:54 AM, Toralf Förster wrote:
> Hi,
>
> I got this recently at this hardened Gentoo Linux server:
>
> Linux mr-fox 5.10.1 #1 SMP Tue Dec 15 22:09:42 CET 2020 x86_64 Intel(R)
> Xeon(R) CPU E5-1650 v3 @ 3.50GHz GenuineIntel GNU/Linux
>
>
> Dec 15 23:31:51
It is now possible to only build book3s/32 kernel for
CPUs without hash table.
Opt out hash related code when CONFIG_PPC_BOOK3S_604 is not selected.
Signed-off-by: Christophe Leroy
---
v2: Rebased
---
arch/powerpc/kernel/head_book3s_32.S | 12
arch/powerpc/mm/book3s32/Makefile
On 2020/12/18 14:17, Chen Zhou wrote:
> When mounting a cgroup hierarchy with disabled controller in cgroup v1,
> all available controllers will be attached.
>
> Add disabled controller check in cgroup1_parse_param() and return directly
> if the specified controller is disabled.
>
>
ufshcd_hba_exit() is always called after ufshcd_exit_clk_scaling() and
ufshcd_exit_clk_gating(), so move ufshcd_exit_clk_scaling/gating() to
ufshcd_hba_exit().
Reviewed-by: Stanley Chu
Reviewed-by: Bean Huo
Signed-off-by: Can Guo
---
drivers/scsi/ufs/ufshcd.c | 32
In contexts like suspend, shutdown and error handling, we need to suspend
devfreq to make sure these contexts won't be disturbed by clock scaling.
However, suspending devfreq is not enough since users can still trigger a
clock scaling by manipulating the sysfs node clkscale_enable and devfreq
Commit 73cc291c27024 ("Make sure clk scaling happens only when HBA is
runtime ACTIVE") is no longer needed since commit f7a42540928a8 ("scsi:
ufs: Protect some contexts from unexpected clock scaling") is a more
mature fix to protect UFS LLD stability from clock scaling invoked through
sysfs nodes
On Thu, Dec 17, 2020 at 10:19:37PM +0100, Alexandre Belloni wrote:
> Hello,
>
> On 05/12/2020 16:51:36+0100, Greg KH wrote:
> > > To me, the documentation was written, and reviewed, more from the
> > > perspective of "why not open code a custom bus instead". So I can see
> > > after the fact how
On 17-12-20, 16:34, Rob Herring wrote:
> The correct syntax for JSON pointers begins with a '/' after the '#'.
> Without a '/', the string should be interpretted as a subschema
> identifier. The jsonschema module currently doesn't handle subschema
> identifiers and incorrectly allows JSON pointers
* H. Nikolaus Schaller [201212 11:59]:
> This reverts
>
> commit f1f028ff89cb ("DTS: ARM: gta04: introduce legacy spi-cs-high to make
> display work again")
>
> which had to be intruduced after
>
> commit 6953c57ab172 ("gpio: of: Handle SPI chipselect legacy bindings")
>
> broke the GTA04
Hi Saravana,
I love your patch! Perhaps something to improve:
[auto build test WARNING on driver-core/driver-core-testing]
[also build test WARNING on linus/master next-20201217]
[cannot apply to linux/master v5.10]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
* Aaro Koskinen [201214 23:01]:
> From: Linus Walleij
>
> Commit 45c5775460f3 ("usb: ohci-omap: Fix descriptor conversion") tried to
> fix all issues related to ohci-omap descriptor conversion, but a wrong
> patch was applied, and one needed change to the OSK board file is still
> missing. Fix
On 17-12-20, 21:05, Dmitry Osipenko wrote:
> Introduce core voltage scaling for NVIDIA Tegra20/30 SoCs, which reduces
> power consumption and heating of the Tegra chips. Tegra SoC has multiple
> hardware units which belong to a core power domain of the SoC and share
> the core voltage. The voltage
when get request SW timeout, if CMD/DAT xfer done irq coming right now,
then there is race between the msdc_request_timeout work and irq handler,
and the host->cmd and host->data may set to NULL in irq handler. also,
current flow ensure that only one path can go to msdc_request_done(), so
no need
On 26-11-20, 19:45, AngeloGioacchino Del Regno wrote:
> 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
Hi Randy,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on shaggy/jfs-next]
[also build test WARNING on linux/master linus/master v5.10 next-20201217]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest
Hi，
The patch https://www.spinics.net/lists/linux-xfs/msg47389.html for xfstests
will fix this regression.
Thanks,
Kaixu
On 2020/12/18 13:58, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit:
On Thu, 2020-12-17 at 10:14 -0500, Tejun Heo wrote:
> Hello,
>
> On Thu, Dec 17, 2020 at 07:48:49PM +0800, Ian Kent wrote:
> > > What could be done is to make the kernfs node attr_mutex
> > > a pointer and dynamically allocate it but even that is too
> > > costly a size addition to the kernfs
> -Original Message-
> From: Rob Herring
> Sent: 2020年12月16日 4:33
> To: Alice Guo (OSS)
> Cc: shawn...@kernel.org; s.ha...@pengutronix.de; ker...@pengutronix.de;
> feste...@gmail.com; k...@kernel.org; devicet...@vger.kernel.org;
> linux-arm-ker...@lists.infradead.org;
From: Zhaoyang Huang
Add SLAB_RECLAIM_ACCOUNT to ashmem_range cache since it has registered
shrinker, which make memAvailable more presiced.
Signed-off-by: Zhaoyang Huang
---
drivers/staging/android/ashmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Signed-off-by: Stephen Zhang
---
arch/x86/kvm/lapic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
index 3136e05..7882322 100644
--- a/arch/x86/kvm/lapic.c
+++ b/arch/x86/kvm/lapic.c
@@ -674,7 +674,7 @@ static bool
Hi Jakub,
On Thu, 17 Dec 2020 at 17:58, Jakub Kicinski wrote:
>
> On Thu, 17 Dec 2020 16:34:09 +0100 Loic Poulain wrote:
> > MHI net is protocol agnostic, the payload protocol depends on the modem
> > configuration, which can be either RMNET (IP muxing and aggregation) or
> > raw IP. This patch
On Fri, Dec 18, 2020 at 09:51:35AM +0800, Zou Wei wrote:
Fix the following sparse warning:
drivers/vdpa/vdpa_sim/vdpa_sim_net.c:36:4: warning: symbol 'macaddr_buf' was
not declared. Should it be static?
Reported-by: Hulk Robot
Signed-off-by: Zou Wei
---
drivers/vdpa/vdpa_sim/vdpa_sim_net.c
Do you need a Loan @ 2% P.A? Mail us your: Names,Home Add,Mob No,Email
id,Amount Needed,Loan Duration,Occupation :If you are interested kindly contact
us via email for more details
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
On Thu, Dec 17, 2020 at 11:30:18AM +0800, Jason Wang wrote:
>
> On 2020/12/16 下午5:47, Michael S. Tsirkin wrote:
> > On Wed, Dec 16, 2020 at 02:47:57PM +0800, Jason Wang wrote:
> > > Hi All:
> > >
> > > This series tries to add the support for control virtqueue in vDPA.
> > >
> > > Control
Since mmap for userspace is based on page alignment, add page alignment
for iram alloc from pool, otherwise, some good data located in the same
page of dmab->area maybe touched wrongly by userspace like pulseaudio.
Signed-off-by: Robin Gong
---
sound/core/memalloc.c | 3 ++-
1 file changed, 2
The UUID room will be exhausted fake when loop attach/dettach backing dev.
Using zero_uuid to the UUID room after dettach normaly.
And attach dev can request UUID room successfully.
Signed-off-by: Yi Li
Signed-off-by: Li bing
---
drivers/md/bcache/super.c | 20 +---
1 file
Hi Kun, Günter,
On Wed, Dec 16, 2020 at 9:17 PM Guenter Roeck wrote:
> On Wed, Dec 16, 2020 at 09:27:28AM -0800, Kun Yi wrote:
> > On Wed, Dec 16, 2020 at 8:31 AM Guenter Roeck wrote:
> > >
> > > On Wed, Dec 16, 2020 at 02:46:41PM +0100, Geert Uytterhoeven wrote:
> > > > The AMD SB Temperature
This patch set is to add support for playback recover after hard suspend and
resume.
It includes:
1. Reverting part of previous commit, which is for handling registers invalid
state
after hard suspend.
2. Adding pm ops in component driver and do regcache sync.
Changes Since v1 and v2:
--
To support playback continuation after hard suspend(bypass powerd)
and resume do regcache sync with component driver pm ops.
Signed-off-by: V Sujith Kumar Reddy
Signed-off-by: Srinivasa Rao Mandadapu
Reviewed-by: Srinivas Kandagatla
Tested-by: Steev Klimaszewski
---
On 16.12.20 14:36, Johannes Berg wrote:
> From: Johannes Berg
>
> Perhaps something got moved around at some point, but the
> current path that gets inserted has "/scripts/gdb" twice,
> since the script is located in scripts/gdb/ already. Fix
> the path.
>
> Signed-off-by: Johannes Berg
> ---
On 16.12.20 14:56, Johannes Berg wrote:
> From: Johannes Berg
>
> If we store the relative path, the user might later cd to a
> different directory, and that would break the automatic symbol
> resolving that happens when a module is loaded into the target
> kernel. Fix this by storing the
MI2S and DMA control registers are not volatile, so remove these from volatile
registers list.
Registers reset state check by reading non volatile registers makes no use,
so remove error check from cpu and platform trigger callbacks.
Initialized map variable two times in lpass platform trigger
Hi Atish,
On Thu, Dec 17, 2020 at 3:49 PM Atish Patra wrote:
>
> memblock_enforce_memory_limit accepts the maximum memory size not the last
> address. Fix the function invocation correctly.
>
> Fixes: 1bd14a66ee52 ("RISC-V: Remove any memblock representing unusable
> memory area")
>
>
Add command to EC_CMD_REBOOT_EC to reset EC but don't boot AP.
Signed-off-by: Pi-Hsun Shih
---
The corresponding changes in ChromeOS EC firmware is at crrev.com/c/2428361
---
include/linux/platform_data/cros_ec_commands.h | 1 +
1 file changed, 1 insertion(+)
diff --git
Signed-off-by: Pi-Hsun Shih
---
drivers/platform/chrome/cros_ec_sysfs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/platform/chrome/cros_ec_sysfs.c
b/drivers/platform/chrome/cros_ec_sysfs.c
index f521a5c65091..8210fb10e839 100644
---
Hi Jan,
> > -sys.path.insert(0, os.path.dirname(__file__) + "/scripts/gdb")
> > +sys.path.insert(0, os.path.dirname(__file__))
> >
> > try:
> > gdb.parse_and_eval("0")
> >
>
> How did you test that, which setup? I just ran "gdb
> /build/vmlinux", and "python print(sys.path)" didn't
Thanks Mark for your Time!!!
On 12/14/2020 11:20 PM, Mark Brown wrote:
On Mon, Dec 14, 2020 at 06:13:22PM +0530, Srinivasa Rao Mandadapu wrote:
On 12/1/2020 11:21 PM, Mark Brown wrote:
Later from review comments by Srinivas kandagatla, I got to know
about regcache sync APIs, which can be
From: Johannes Berg
If we store the relative path, the user might later cd to a
different directory, and that would break the automatic symbol
resolving that happens when a module is loaded into the target
kernel. Fix this by storing the abspath() of each path given,
just like we already do for
Hi Adam,
On Wed, Dec 16, 2020 at 6:03 PM Adam Ford wrote:
> On Wed, Dec 16, 2020 at 8:55 AM Geert Uytterhoeven
> wrote:
> > On Sun, Dec 13, 2020 at 7:38 PM Adam Ford wrote:
> > > When the board was added, clock drivers were being updated done at
> > > the same time to allow the versaclock
From: SeongJae Park
SeongJae Park (5):
xen/xenbus: Allow watches discard events before queueing
xen/xenbus: Add 'will_handle' callback support in xenbus_watch_path()
xen/xenbus/xen_bus_type: Support will_handle watch callback
xen/xenbus: Count pending messages for each watch
From: SeongJae Park
This commit adds support of the 'will_handle' watch callback for
'xen_bus_type' users.
This is part of XSA-349
This is upstream commit be987200fbaceaef340872841d4f7af2c5ee8dc3
Cc: sta...@vger.kernel.org
Signed-off-by: SeongJae Park
Reported-by: Michael Kurth
Reported-by:
From: SeongJae Park
Some code does not directly make 'xenbus_watch' object and call
'register_xenbus_watch()' but use 'xenbus_watch_path()' instead. This
commit adds support of 'will_handle' callback in the
'xenbus_watch_path()' and it's wrapper, 'xenbus_watch_pathfmt()'.
This is part of
From: SeongJae Park
This commit adds a counter of pending messages for each watch in the
struct. It is used to skip unnecessary pending messages lookup in
'unregister_xenbus_watch()'. It could also be used in 'will_handle'
callback.
This is part of XSA-349
This is upstream commit
On Wed, Dec 16, 2020 at 2:40 PM syzbot
wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 1d0e850a49a5b56f8f3cb51e74a11e2fedb96be6
> Author: David Howells
> Date: Fri Oct 16 12:21:14 2020 +
>
> afs: Fix cell removal
>
> bisection log:
From: SeongJae Park
If handling logics of watch events are slower than the events enqueue
logic and the events can be created from the guests, the guests could
trigger memory pressure by intensively inducing the events, because it
will create a huge number of pending events that exhausting the
Thanks Mark for your Time!!!
On 12/14/2020 11:20 PM, Mark Brown wrote:
On Mon, Dec 14, 2020 at 06:13:22PM +0530, Srinivasa Rao Mandadapu wrote:
On 12/1/2020 11:21 PM, Mark Brown wrote:
Later from review comments by Srinivas kandagatla, I got to know
about regcache sync APIs, which can be
Hello,
On 17.12.20 02:13, Jakub Kicinski wrote:
>> +netdev_warn(priv->dev, "HW Timestamping init failed:
>> %pe\n",
>> +ERR_PTR(ret));
>
> why convert to ERR_PTR and use %pe and not just %d?
To get a symbolic error name if support is
On Wed, Dec 16, 2020 at 9:55 PM Matthew Wilcox wrote:
>
> On Wed, Dec 16, 2020 at 11:34:10AM -0800, syzbot wrote:
> > Unfortunately, I don't have any reproducer for this issue yet.
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by:
On Wed, Dec 16, 2020 at 11:48:55PM -0800, Atish Patra wrote:
> memblock_enforce_memory_limit accepts the maximum memory size not the last
> address. Fix the function invocation correctly.
>
> Fixes: 1bd14a66ee52 ("RISC-V: Remove any memblock representing unusable
> memory area")
>
>
On Thu, Dec 17, 2020 at 8:04 AM Joe Lawrence wrote:
>
> On 12/16/20 1:14 AM, Masahiro Yamada wrote:
> > On Tue, Dec 8, 2020 at 11:31 PM Artem Savkov wrote:
> >>
> >> On Tue, Dec 08, 2020 at 05:20:35PM +0800, WANG Chao wrote:
> >>> Sorry for the late reply.
> >>>
> >>> On 11/25/20 at 10:42P,
501 - 600 of 988 matches
Mail list logo
