The following changes since commit 1e7468bd9d30a21e059af477106dc5588ae52dff:
clk: Specify IOMEM dependency for HSDK pll driver (2020-07-11 09:28:10 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
tags/clk-for-linus
for you to
Thanks, applied, although I rewrote the commit description to make it
be a bit more clearer:
fs: prevent BUG_ON in submit_bh_wbc()
If a device is hot-removed --- for example, when a physical device is
unplugged from pcie slot or a nbd device's network is shutdown ---
this can
On Mon, Aug 3, 2020 at 12:36 PM Jordan Crouse wrote:
>
> Add support to create a io-pgtable for use by targets that support
> per-instance pagetables. In order to support per-instance pagetables the
> GPU SMMU device needs to have the qcom,adreno-smmu compatible string and
> split pagetables
virtiofs device has a range of memory which is mapped into file inodes
using dax. This memory is mapped in qemu on host and maps different
sections of real file on host. Size of this memory is limited
(determined by administrator) and depending on filesystem size, we will
soon reach a situation
When a file is opened with O_TRUNC, we need to make sure that any other
DAX operation is not in progress. DAX expects i_size to be stable.
In fuse_iomap_begin() we check for i_size at multiple places and we expect
i_size to not change.
Another problem is, if we setup a mapping in
The device communicates FUSE_SETUPMAPPING/FUSE_REMOVMAPPING alignment
constraints via the FUST_INIT map_alignment field. Parse this field and
ensure our DAX mappings meet the alignment constraints.
We don't actually align anything differently since our mappings are
already 2MB aligned. Just
Hi All,
This is V2 of the patches. I had posted V1 here.
https://lore.kernel.org/linux-fsdevel/20200304165845.3081-1-vgo...@redhat.com/
I have taken care of most of the comments from V1.
Amir had suggested that some of the code can be moved to a new file, may
be post series. I have left that
From: Sebastien Boeuf
On MMIO a new set of registers is defined for finding SHM
regions. Add their definitions and use them to find the region.
Signed-off-by: Sebastien Boeuf
Cc: k...@vger.kernel.org
Cc: "Michael S. Tsirkin"
---
drivers/virtio/virtio_mmio.c | 32
This option was introduced so that for virtio_fs we don't show any mounts
options fuse_show_options(). Because we don't offer any of these options
to be controlled by mounter.
Very soon we are planning to introduce option "dax" which mounter should
be able to specify. And no_mount_options does
From: Sebastien Boeuf
On PCI the shm regions are found using capability entries;
find a region by searching for the capability.
Signed-off-by: Sebastien Boeuf
Signed-off-by: Dr. David Alan Gilbert
Signed-off-by: kbuild test robot
Cc: k...@vger.kernel.org
Cc: "Michael S. Tsirkin"
---
From: Sebastien Boeuf
Virtio defines 'shared memory regions' that provide a continuously
shared region between the host and guest.
Provide a method to find a particular region on a device.
Signed-off-by: Sebastien Boeuf
Signed-off-by: Dr. David Alan Gilbert
Cc: k...@vger.kernel.org
Cc:
Add a mount option to allow using dax with virtio_fs.
Signed-off-by: Vivek Goyal
---
fs/fuse/fuse_i.h| 7
fs/fuse/inode.c | 3 ++
fs/fuse/virtio_fs.c | 82 +
3 files changed, 78 insertions(+), 14 deletions(-)
diff --git
This reduces code duplication and make it little easier to read code.
Signed-off-by: Vivek Goyal
---
fs/fuse/virtio_fs.c | 50 +++--
1 file changed, 30 insertions(+), 20 deletions(-)
diff --git a/fs/fuse/virtio_fs.c b/fs/fuse/virtio_fs.c
index
Add logic to free up a busy memory range. Freed memory range will be
returned to free pool. Add a worker which can be started to select
and free some busy memory ranges.
Process can also steal one of its busy dax ranges if free range is not
available. I will refer it to as direct reclaim.
If
This patch implements basic DAX support. mmap() is not implemented
yet and will come in later patches. This patch looks into implemeting
read/write.
We make use of interval tree to keep track of per inode dax mappings.
Do not use dax for file extending writes, instead just send WRITE message
to
This is done along the lines of ext4 and xfs. I primarily wanted ->writepages
hook at this time so that I could call into dax_writeback_mapping_range().
This in turn will decide which pfns need to be written back.
Signed-off-by: Vivek Goyal
---
fs/fuse/file.c | 21 -
1 file
virtiofs does not have a block device but it has dax device.
Modify bdev_dax_pgoff() to be able to handle that.
If there is no bdev, that means dax offset is 0. (It can't be a partition
block device starting at an offset in dax device).
This is little hackish. There have been discussions about
We need some kind of locking mechanism here. Normal file systems like
ext4 and xfs seems to take their own semaphore to protect agains
truncate while fault is going on.
We have additional requirement to protect against fuse dax memory range
reclaim. When a range has been selected for reclaim, we
Introduce two new fuse commands to setup/remove memory mappings. This
will be used to setup/tear down file mapping in dax window.
Signed-off-by: Vivek Goyal
Signed-off-by: Peng Tao
---
include/uapi/linux/fuse.h | 29 +
1 file changed, 29 insertions(+)
diff --git
fuse_file_put(sync) can be called with sync=true/false. If sync=true,
it waits for release request response and then calls iput() in the
caller's context. If sync=false, it does not wait for release request
response, frees the fuse_file struct immediately and req->end function
does the iput().
Divide the dax memory range into fixed size ranges (2MB for now) and put
them in a list. This will track free ranges. Once an inode requires a
free range, we will take one from here and put it in interval-tree
of ranges assigned to inode.
Signed-off-by: Vivek Goyal
Signed-off-by: Peng Tao
---
This list will be used selecting fuse_dax_mapping to free when number of
free mappings drops below a threshold.
Signed-off-by: Vivek Goyal
---
fs/fuse/file.c | 22 ++
fs/fuse/fuse_i.h | 7 +++
fs/fuse/inode.c | 4
3 files changed, 33 insertions(+)
diff --git
Hi Linus,
Please pull this fix to my kallsyms_show_value() refactoring for
v5.9-rc1. About a month after the original refactoring landed, 0day
noticed that there was a path through the kernfs binattr read handlers
that did not have PAGE_SIZEd buffers, and the module "sections" read
handler made a
From: Stefan Hajnoczi
Add DAX mmap() support.
Signed-off-by: Stefan Hajnoczi
---
fs/fuse/file.c | 62 +-
1 file changed, 61 insertions(+), 1 deletion(-)
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index 194fe3e404a7..be7d90eb5b41 100644
---
From: Stefan Hajnoczi
Setup a dax device.
Use the shm capability to find the cache entry and map it.
The DAX window is accessed by the fs/dax.c infrastructure and must have
struct pages (at least on x86). Use devm_memremap_pages() to map the
DAX window PCI BAR and allocate struct page.
On Fri, Aug 07, 2020 at 01:32:41PM -0600, Rob Herring wrote:
> Fix various typos and inconsistent capitalization of CPU in the libperf
> man pages.
>
> Cc: Peter Zijlstra
> Cc: Ingo Molnar
> Cc: Arnaldo Carvalho de Melo
> Cc: Mark Rutland
> Cc: Alexander Shishkin
> Cc: Jiri Olsa
> Cc:
On Fri, Aug 07, 2020 at 01:32:25PM -0600, Rob Herring wrote:
> Commit 3ce311afb558 ("libperf: Move to tools/lib/perf") moved libperf
> out of tools/perf/, but failed to update MAINTAINERS.
>
> Cc: Peter Zijlstra
> Cc: Ingo Molnar
> Cc: Arnaldo Carvalho de Melo
> Cc: Mark Rutland
> Cc:
On 8/7/20 1:43 PM, Arnaldo Carvalho de Melo wrote:
>> @@ -2958,9 +2967,10 @@ static int timehist_check_attr(struct perf_sched
>> *sched,
>>
>> static int perf_sched__timehist(struct perf_sched *sched)
>> {
>> -const struct evsel_str_handler handlers[] = {
>> +struct evsel_str_handler
Hello!
On 8/7/20 8:49 PM, Lad Prabhakar wrote:
> Add du node to r8a7742 SoC DT. Boards that want to enable the DU
Both "du" and "DU" on a single line? :-)
> need to specify the output topology.
>
> Signed-off-by: Lad Prabhakar
> Reviewed-by: Marian-Cristian Rotariu
>
[...]
MBR, Sergei
On Thu, Jun 11, 2020 at 2:59 AM Tomeu Vizoso wrote:
>
> Bifrost devices do support the flush reduction feature, so on first job
> submit we were trying to read the register while still powered off.
>
> If the GPU is powered off, the feature doesn't bring any benefit, so
> don't try to read.
>
>
On Fri, Aug 07, 2020 at 11:20:05AM -0700, Kees Cook wrote:
> When refactoring the SCM_RIGHTS code, I accidentally mis-merged my
> native/compat diffs, which entirely broke using SCM_RIGHTS in compat
> mode. Use the correct helper.
>
> Reported-by: Christian Zigotzky
> Link:
Hi Linus,
Please pull this seccomp update for v5.9-rc1-fix1. This fixes my typo in
the SCM_RIGHTS refactoring, thanks to Thadeu Lima de Souza Cascardo for
tracking it down, and to Christian Zigotzky and Alex Xu for their
reports.
Thanks!
-Kees
The following changes since commit
Em Fri, Aug 07, 2020 at 10:48:44AM -0600, David Ahern escreveu:
> Commit fbd705a0c618 ("sched: Introduce the 'trace_sched_waking' tracepoint")
> added sched_waking tracepoint which should be preferred over sched_wakeup
> when analyzing scheduling delays.
>
> Update 'perf sched record' to collect
On Fri, 2020-08-07 at 16:14 +0200, Dietmar Eggemann wrote:
> On 31/07/2020 09:42, Rik van Riel wrote:
> > Possible solution
> > ...
> I imagine that I can see what you want to achieve here ;-)
>
> But it's hard since your v5 RFC
>
A recent change to a default value of configuration variable
(ENABLE_X86_RELAX_RELOCATIONS OFF -> ON) in LLVM now causes Clang's
integrated assembler to emit R_X86_64_GOTPCRELX/R_X86_64_REX_GOTPCRELX
relocations. LLD will relax instructions with these relocations based on
whether the image is
Switches fdpic coredumps away from original aout dumping primitives
to the same kind of regset use as regular elf coredumps do.
The following changes since commit b4e9c9549f62329d2412f899635fddc5212b9cd4:
introduction of regset ->get() wrappers, switching ELF coredumps to those
On Fri, Aug 07, 2020 at 11:41:09AM -0700, Hugh Dickins wrote:
> My home testing was, effectively, on top of c6fe44d96fc1 (v5.8 plus
> your two patches): I did not have in the io_uring changes from the
> current tree. In glancing there, I noticed one new and one previous
> instance of
Lots of things take locks, due to a wee bug, RCU-lockdep didn't notice
that the locking tracepoints were using RCU.
Push rcu_idle_{enter,exit}() as deep as possible into the idle paths,
this also resolves a lot of _rcuidle()/RCU_NONIDLE() usage.
Specifically, sched_clock_idle_wakeup_event() will
Hi,
Syzbot report:
https://lkml.kernel.org/r/e3068105ac405...@google.com
triggered a whole bunch of fallout.
These 3 patches are in reverse order of discovery. With them applied the
reproducer no longer triggers and the machine boots without errors.
I also spend half the day
The lockdep tracepoints are under the lockdep recursion counter, this
has a bunch of nasty side effects:
- TRACE_IRQFLAGS doesn't work across the entire tracepoint, leading to
all sorts of dodgy complaints.
- RCU-lockdep doesn't see the tracepoints either, hiding numerous
"suspicious RCU
Much of the complexity in irqenter_{enter,exit}() is due to #PF being
the sole exception that can schedule from kernel context.
One additional wrinkle with #PF is that it is non-maskable, it can
happen _anywhere_. Due to this, and the wonders of tracing, we can get
the 'normal' NMI nesting vs
Commit 3ce311afb558 ("libperf: Move to tools/lib/perf") moved libperf
out of tools/perf/, but failed to update MAINTAINERS.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Arnaldo Carvalho de Melo
Cc: Mark Rutland
Cc: Alexander Shishkin
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Rob Herring
---
Fix various typos and inconsistent capitalization of CPU in the libperf
man pages.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Arnaldo Carvalho de Melo
Cc: Mark Rutland
Cc: Alexander Shishkin
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Rob Herring
---
From: Maciej Żenczykowski
Fixes: is_umdir_used - pid filename too long
pids are no longer limited to 16-bits, bump to 32-bits,
ie. 9 decimal characters. Additionally sizeof("/") already
returns 2 - ie. it already accounts for trailing zero.
Cc: Jeff Dike
Cc: Richard Weinberger
Cc: Anton
On Fri, Aug 7, 2020 at 4:18 AM Zhihao Cheng wrote:
> That's where we hold different views. I have 3 viewpoints（You can point
> out which one you disagree.）:
>
> 1. If kthread_stop() happens at line 12, ubi thread is *marked* with
> stop flag, it will stop at kthread_should_stop() as long as it
On Fri, 7 Aug 2020 10:32:31 -0700, Guenter Roeck wrote:
> On Fri, Aug 07, 2020 at 06:28:01PM +0200, Stephen Kitt wrote:
> >
> > -static int ltc2978_probe(struct i2c_client *client,
> > -const struct i2c_device_id *id)
> > +static int ltc2978_probe(struct i2c_client *client)
From: Sultan Alsawaf
There's no reason to hold an RCU read lock the entire time while
optimistically spinning for a mutex lock. This can needlessly lengthen
RCU grace periods and slow down synchronize_rcu() when it doesn't brute
force the RCU grace period via rcupdate.rcu_expedited=1.
From: Sultan Alsawaf
There's no reason to hold an RCU read lock the entire time while
optimistically spinning for a rwsem. This can needlessly lengthen RCU
grace periods and slow down synchronize_rcu() when it doesn't brute
force the RCU grace period via rcupdate.rcu_expedited=1.
Signed-off-by:
Hi Kees,
Thanks a lot for your patch! I think your patch works because I can patch the
Git source code but the kernel doesn’t boot. In my point of view your
modifications aren’t responsible for this second issue. The kernel can’t
initialize the graphics card anymore. I think the latest DRM
On 8/7/20 11:08 AM, Florian Fainelli wrote:
>
>
> On 8/7/2020 9:21 AM, Guenter Roeck wrote:
>> On Fri, Aug 07, 2020 at 04:59:02PM +0530, madhuparnabhowmi...@gmail.com
>> wrote:
>>> From: Madhuparna Bhowmik
>>>
>>> In rdc321x_wdt_probe(), rdc321x_wdt_device.queue is initialized
>>> after
On Fri, Aug 7, 2020 at 11:41 AM Hugh Dickins wrote:
>
> +
> + /*
> +* If we hoped to pass PG_locked on to the next locker, but found
> +* no exclusive taker, then we must clear it before dropping q->lock.
> +* Otherwise unlock_page() can race
Hi Marco and Kees,
On Fri, Aug 07, 2020 at 08:06PM +0300, Pekka Enberg wrote:
> > Anything interesting in your .config? The fault does not reproduce
> > with 5.8.0 + x86-64 defconfig.
On Fri, Aug 7, 2020 at 8:18 PM Marco Elver wrote:
> It's quite close to defconfig, just some extra options for
On Fri, Aug 07, 2020 at 02:07:59PM -0400, Mathieu Desnoyers wrote:
> One thing I find weird about Peter's patch is that it adds a
> MEMBERRIER_CMD_PRIVATE_EXPEDITED_RSEQ without a corresponding
> MEMBARRIER_CMD_REGISTER_PRIVATE_EXPEDITED_RSEQ. Considering that
> the SYNC_CORE variant already has
On 8/7/20 11:30 AM, Evgeny Novikov wrote:
> 07.08.2020, 19:21, "Guenter Roeck" :
>> On Fri, Aug 07, 2020 at 04:59:02PM +0530, madhuparnabhowmi...@gmail.com
>> wrote:
>>> From: Madhuparna Bhowmik
>>>
>>> In rdc321x_wdt_probe(), rdc321x_wdt_device.queue is initialized
>>> after misc_register(),
On Fri, Aug 7, 2020 at 11:25 AM Mathieu Desnoyers
wrote:
>
> - On Aug 7, 2020, at 1:55 PM, Peter Oskolkov p...@posk.io wrote:
>
> > On Thu, Aug 6, 2020 at 5:27 PM Boqun Feng wrote:
> [...]
> >> What if the manager thread update ->percpu_list_ptr and call
> >> membarrier() here? I.e.
> >>
>
On Fri, 2020-08-07 at 13:31 -0400, Mimi Zohar wrote:
> On Sat, 2020-08-08 at 02:41 +1000, James Morris wrote:
> > On Thu, 6 Aug 2020, Mimi Zohar wrote:
> >
> > > On Thu, 2020-08-06 at 09:51 +1000, James Morris wrote:
> > > > On Wed, 5 Aug 2020, Mimi Zohar wrote:
> > > >
> > > > > If block layer
On Thu, 6 Aug 2020, Linus Torvalds wrote:
> On Thu, Aug 6, 2020 at 11:00 AM Matthew Wilcox wrote:
> >
> > It wasn't clear to me whether Hugh thought it was an improvement or
> > not that trylock was now less likely to jump the queue. There're
> > the usual "fair is the opposite of throughput"
On Fri, Aug 07, 2020 at 10:54:51AM -0700, Dey, Megha wrote:
> So from the hierarchical domain standpoint, we will have:
> - For DSA device: vector->intel-IR->IDXD
> - For Jason's device: root domain-> domain A-> Jason's device's IRQ domain
> - For any other intel IMS device in the future which
>
On 7/25/2020 9:15 PM, Florian Fainelli wrote:
> Hi Thomas,
>
> This patch series fixes W=1 -Wmissing-prototypes warnings for the
> bcm47xx_sprom.c firmware file.
Thomas, can you apply these patches if you are fine with them? Thanks
>
> Thanks!
>
> Florian Fainelli (2):
> firmware:
On Mon, Aug 3, 2020 at 11:45 PM Sai Prakash Ranjan
wrote:
>
> MSM bus scaling has moved on to use interconnect framework
> and downstream bus scaling apis are not present anymore.
> Remove them as they are nop anyways in the current code,
> no functional change.
>
thanks, nice cleanup.. I'm
And similarly, rename head_pincount() --> head_compound_pincount().
These names are more accurate (or less misleading) than the original
ones.
Cc: Qian Cai
Cc: Matthew Wilcox
Cc: Vlastimil Babka
Cc: Kirill A. Shutemov
Signed-off-by: John Hubbard
---
Hi,
This is a follow-up patch to v2 of
On 8/7/2020 3:04 AM, Álvaro Fernández Rojas wrote:
> Current board declarations are a mess. Let's put some order and make them
> follow the same structure. Also board declarations tabs.
> Switch to SPDX license identifier.
>
> Signed-off-by: Álvaro Fernández Rojas
That is a lot of churn, not
On Fri, Aug 7, 2020 at 1:07 PM Joel Fernandes (Google)
wrote:
>
>
> This series improves/adds to RCU's warnings about CPU hotplug and adds
> documentation and testing.
>
> v3->v4: Minor cleanups.
>
> Joel Fernandes (Google) (5):
> rcu/tree: Add a warning if CPU being onlined did not report QS
On 8/7/2020 3:04 AM, Álvaro Fernández Rojas wrote:
> EHCI and OHCI share the same USB ports. Therefore, if the board has OHCI
> it should also have EHCI.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
07.08.2020, 19:21, "Guenter Roeck" :
> On Fri, Aug 07, 2020 at 04:59:02PM +0530, madhuparnabhowmi...@gmail.com wrote:
>> From: Madhuparna Bhowmik
>>
>> In rdc321x_wdt_probe(), rdc321x_wdt_device.queue is initialized
>> after misc_register(), hence if ioctl is called before its
>>
On 8/7/2020 3:04 AM, Álvaro Fernández Rojas wrote:
> There's no EHCI controller on BCM6348.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 8/7/20 2:18 AM, David Laight wrote:
> From: Eric Dumazet
>> Sent: 06 August 2020 23:21
>>
>> On 7/22/20 11:09 PM, Christoph Hellwig wrote:
>>> Rework the remaining setsockopt code to pass a sockptr_t instead of a
>>> plain user pointer. This removes the last remaining set_fs(KERNEL_DS)
>>>
On Fri, Aug 7, 2020 at 12:19 AM Christoph Hellwig wrote:
>
> On Thu, Aug 06, 2020 at 11:23:34PM -0700, John Stultz wrote:
> > So I've finally rebase-bisected it down to:
> > a31edb2059ed ("net: improve the user pointer check in init_user_sockptr")
> >
On Fri, Aug 07, 2020 at 11:20:05AM -0700, Kees Cook wrote:
> When refactoring the SCM_RIGHTS code, I accidentally mis-merged my
> native/compat diffs, which entirely broke using SCM_RIGHTS in compat
> mode. Use the correct helper.
>
> Reported-by: Christian Zigotzky
> Link:
- On Aug 7, 2020, at 1:55 PM, Peter Oskolkov p...@posk.io wrote:
> On Thu, Aug 6, 2020 at 5:27 PM Boqun Feng wrote:
[...]
>> What if the manager thread update ->percpu_list_ptr and call
>> membarrier() here? I.e.
>>
>> CPU0CPU1
>>
On 8/7/2020 3:04 AM, Álvaro Fernández Rojas wrote:
> There are 3 duplicated new lines, let's remove them.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 8/7/20 11:08 AM, Florian Fainelli wrote:
>
>
> On 8/7/2020 9:21 AM, Guenter Roeck wrote:
>> On Fri, Aug 07, 2020 at 04:59:02PM +0530, madhuparnabhowmi...@gmail.com
>> wrote:
>>> From: Madhuparna Bhowmik
>>>
>>> In rdc321x_wdt_probe(), rdc321x_wdt_device.queue is initialized
>>> after
When refactoring the SCM_RIGHTS code, I accidentally mis-merged my
native/compat diffs, which entirely broke using SCM_RIGHTS in compat
mode. Use the correct helper.
Reported-by: Christian Zigotzky
Link: https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-August/216156.html
Reported-by: "Alex
On Fri, Jul 31, 2020 at 3:36 PM Akshu Agrawal wrote:
>
> Hi,
>
> This series of patch does the following:
> 1. Changes the name of the AMD SoC general purpose clk
> from ST(a version of SoC) to FCH (name of the IP).
> 2. Then make the drivers support both older and newer versions of
> SoC.
>
>
On 8/7/2020 6:14 AM, Greg KH wrote:
> On Thu, Aug 06, 2020 at 01:00:54PM -0700, Florian Fainelli wrote:
>>
>>
>> On 7/20/2020 11:26 AM, Florian Fainelli wrote:
>>> On 7/20/20 6:04 AM, Greg KH wrote:
On Thu, Jul 09, 2020 at 12:50:23PM -0700, Florian Fainelli wrote:
> From: Will Deacon
On Fri, Aug 7, 2020 at 11:06 AM Daniel Lezcano
wrote:
>
> Ok, I will send a fix.
I ended up doing it during my morning routine of looking around for,
and applying, random patches.
So it's commit 0f5d0a4c01cc ("thermal: don't make THERMAL_NETLINK
'default y'") in my tree now.
On Fri, Jul 31, 2020 at 4:08 PM Kees Cook wrote:
>
> From: Arvind Sankar
>
> The BFD linker generates run-time relocations for z_input_len and
> z_output_len, even though they are absolute symbols.
>
> This is fixed for binutils-2.35 [1]. Work around this for earlier
> versions by defining two
On Fri, Aug 7, 2020 at 12:51 PM Randy Dunlap wrote:
>
> Drop a repeated word in comments.
> {open, is, then}
>
> Signed-off-by: Randy Dunlap
> Cc: Paul Moore
> Cc: Stephen Smalley
> Cc: Eric Paris
> Cc: seli...@vger.kernel.org
> Cc: James Morris
> Cc: "Serge E. Hallyn"
> Cc:
On Fri, Aug 07, 2020 at 10:48:36AM -0700, Linus Torvalds wrote:
> On Fri, Aug 7, 2020 at 10:35 AM Catalin Marinas
> wrote:
> > Acked-by: Catalin Marinas
> >
> > Linus, could you please pick this up directly? Otherwise, it will wait
> > until we reach -rc1 to avoid basing a branch on a random
On 8/7/2020 9:21 AM, Guenter Roeck wrote:
> On Fri, Aug 07, 2020 at 04:59:02PM +0530, madhuparnabhowmi...@gmail.com wrote:
>> From: Madhuparna Bhowmik
>>
>> In rdc321x_wdt_probe(), rdc321x_wdt_device.queue is initialized
>> after misc_register(), hence if ioctl is called before its
>>
On Fri, Aug 7, 2020 at 11:37 AM Pu Wen wrote:
>
> Add device HID HYGO0010 to match the Hygon ACPI Vendor ID (HYGO) that
> was registered in http://www.uefi.org/acpi_id_list, and the I2C
> controller on Hygon paltform will use the HID.
>
> Signed-off-by: Pu Wen
> Acked-by: Andy Shevchenko
>
- On Aug 7, 2020, at 1:48 PM, Peter Oskolkov p...@posk.io wrote:
> On Thu, Aug 6, 2020 at 10:37 AM Mathieu Desnoyers
> wrote:
>>
[...]
>> Also, should this belong to the membarrier or the rseq system call ? It just
>> looks like the membarrier happens to implement very similar things for
>>
On Thu, Jul 30, 2020 at 3:51 PM Nick Desaulniers
wrote:
>
> If the link register was zeroed out, do not attempt to use it for
> address calculations for which there are currently no fixup handlers,
> which can lead to a panic during unwind. Since panicking triggers
> another unwind, this can lead
Hi Andrei,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on cryptodev/master]
[also build test WARNING on crypto/master next-20200807]
[cannot apply to powerpc/next sparc-next/master v5.8]
[If your patch is applied to the wrong git tree, kindly drop us a note
On 07/08/2020 17:54, Linus Torvalds wrote:
> On Fri, Aug 7, 2020 at 2:40 AM Daniel Lezcano
> wrote:
>>
>> It defaults to 'y' because the previous (but unused) implementation was
>> unconditionally compiled-in and because of the thermal users needs.
>>
>> Is default=y wrong given this history?
>
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-5.9-rc1-2
with top-most commit 0873ad923a05751a29a92229739ce2737c29d348
Merge branch 'pm-core'
on top of commit 04084978003c1a1810a0b1fea581078106394a32
Merge tag 'pm-5.9-rc1' of
On Fri, 07 Aug 2020 14:27:48 +0200 Rouven Czerwinski wrote:
> I just tested on my x86_64 workstation and these specific tests fail
> there too, do they only work on 5.8? They were added in 5.8, but I am
> running 5.7.11 here. It looks like these failures are not
> MSG_CMSG_COMPAT related.
>
>
On 8/7/20 10:35 AM, Catalin Marinas wrote:
> On Fri, Aug 07, 2020 at 07:45:21AM -0700, Guenter Roeck wrote:
>> Commit 585524081ecd ("random: random.h should include archrandom.h, not
>> the other way around") tries to fix a problem with recursive inclusion
>> of linux/random.h and
The pull request you sent on Thu, 6 Aug 2020 21:08:17 -0700:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.9-merge-7
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5631c5e0eb9035d92ceb20fcd9cdb7779a3f5cc7
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 7 Aug 2020 07:04:50 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-5.9-rc1-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e51418191f5a741b5f94764798c81bf69dec4806
Thank you!
--
Deet-doot-dot, I
Hi,
Thanks for the patch!
On 8/7/20 7:20 PM, Andrei Botila wrote:
> From: Andrei Botila
>
> Standardize the way input lengths equal to 0 are handled in all skcipher
> algorithms. All the algorithms return 0 for input lengths equal to zero.
>
> Signed-off-by: Andrei Botila
> ---
>
On Thu, Aug 6, 2020 at 5:27 PM Boqun Feng wrote:
>
> On Thu, Aug 06, 2020 at 10:05:44AM -0700, Peter Oskolkov wrote:
> > Based on Google-internal RSEQ work done by
> > Paul Turner and Andrew Hunter.
> >
> > This patch adds a selftest for MEMBARRIER_CMD_PRIVATE_RESTART_RSEQ_ON_CPU.
> > The test
Hi Thomas,
On 8/7/2020 9:47 AM, Thomas Gleixner wrote:
Jason Gunthorpe writes:
Though it is more of a rational and a cookbook on how to combine
existing technology pieces. (eg PASID, platform_msi, etc)
The basic approach of SIOV's IMS is that there is no longer a generic
interrupt
On Thu, 6 Aug 2020, Cfir Cohen wrote:
> The LAUNCH_SECRET command performs encryption of the
> launch secret memory contents. Mark pinned pages as
> dirty, before unpinning them.
> This matches the logic in sev_launch_update().
>
> Signed-off-by: Cfir Cohen
Acked-by: David Rientjes
On Fri, Aug 7, 2020 at 10:35 AM Catalin Marinas wrote:
>
> Acked-by: Catalin Marinas
>
> Linus, could you please pick this up directly? Otherwise, it will wait
> until we reach -rc1 to avoid basing a branch on a random commit.
Already done, since I was the cause of the mess. But because I did
On Mon, Jul 20, 2020 at 05:13:59PM -0400, Vivek Goyal wrote:
> Page fault error handling behavior in kvm seems little inconsistent when
> page fault reports error. If we are doing fault synchronously
> then we capture error (-EFAULT) returned by __gfn_to_pfn_memslot() and
> exit to user space and
Excerpts from Thadeu Lima de Souza Cascardo's message of August 7, 2020 1:36 pm:
> On Fri, Aug 07, 2020 at 08:48:46AM -0700, Linus Torvalds wrote:
>> On Fri, Aug 7, 2020 at 8:19 AM Alex Xu (Hello71) wrote:
>> >
>> > On Linus' master, wine fails to start with the following error:
>> >
>> > wine
On Fri, Aug 7, 2020 at 6:38 AM wrote:
>
[...]
> I'm thinking even this is a problem, we can end up sending IPIs to CPUs
> outside out partition (they might be NOHZ_FULL) and that's a no-no too.
>
> Something like so perhaps... that really limits it to CPUs that match
> our mm.
Thanks for the
Add LVDS encoder node to r8a7742 SoC DT.
Signed-off-by: Lad Prabhakar
Reviewed-by: Marian-Cristian Rotariu
---
arch/arm/boot/dts/r8a7742.dtsi | 54 ++
1 file changed, 54 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7742.dtsi b/arch/arm/boot/dts/r8a7742.dtsi
Add du node to r8a7742 SoC DT. Boards that want to enable the DU
need to specify the output topology.
Signed-off-by: Lad Prabhakar
Reviewed-by: Marian-Cristian Rotariu
---
arch/arm/boot/dts/r8a7742.dtsi | 35 ++
1 file changed, 35 insertions(+)
diff --git
201 - 300 of 954 matches
Mail list logo
