On Thu, Oct 22, 2020 at 10:22:25PM +0100, Matthew Wilcox (Oracle) wrote:
> Use the new blk_completion infrastructure to wait for multiple I/Os.
> Also coalesce adjacent buffer heads into a single BIO instead of
> submitting one BIO per buffer head. This doesn't work for fscrypt yet,
> so keep the
Hi Heikki,
On Thu, Oct 22, 2020 at 5:43 AM Heikki Krogerus
wrote:
>
> On Thu, Oct 22, 2020 at 12:25:07AM -0700, Prashant Malani wrote:
> > Hi Greg,
> >
> > On Thu, Oct 22, 2020 at 12:17 AM Greg KH wrote:
> > >
> > > > > > +What:
> > > > > >
Hi Loic,
On 10/22/20 3:20 AM, Loic Poulain wrote:
Hi Hemant,
A few comments inline.
On Thu, 22 Oct 2020 at 10:22, Hemant Kumar wrote:
This MHI client driver allows userspace clients to transfer
raw data between MHI device and host using standard file operations.
Driver instantiates UCI
Hi,
On Wed, Oct 21, 2020 at 10:05 PM Alexandru Stan wrote:
>
> The extra 0 only adds one point in the userspace visible range,
> so this change is almost a noop with the current driver behavior.
>
> We don't need the 0% point, userspace seems to handle this just fine
> because it uses the
On Thu, Oct 22, 2020 at 6:37 AM wrote:
>
> Hi Tomasz,
>
> On 2020-10-13 19:09, Tomasz Figa wrote:
> > Hi Vikash,
> >
> > On Tue, Oct 13, 2020 at 02:56:21PM +0530, vgaro...@codeaurora.org
> > wrote:
> >>
> >> On 2020-10-08 19:51, Tomasz Figa wrote:
> >> > On Wed, Oct 7, 2020 at 9:33 PM wrote:
>
Hi,
On Wed, Oct 21, 2020 at 10:05 PM Alexandru Stan wrote:
>
> We want userspace to represent the human perceived brightness.
> Since the led drivers and the leds themselves don't have a
> linear response to the value we give them in terms of perceived
> brightness, we'll bake the curve into the
On Thu, 2020-10-22 at 15:06 -0700, Moritz Fischer wrote:
> The driver does not implement a shutdown handler which leads to
> issues
> when using kexec in certain scenarios. The NIC keeps on fetching
> descriptors which gets flagged by the IOMMU with errors like this:
>
> DMAR: DMAR:[DMA read]
Replace blocking cma_release() with a non-blocking cma_release_nowait()
call, so there is no more need to temporarily drop hugetlb_lock.
Signed-off-by: Roman Gushchin
---
mm/hugetlb.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
This small patchset introduces a non-blocking version of cma_release()
and simplifies the code in hugetlbfs, where previously we had to
temporarily drop hugetlb_lock around the cma_release() call.
It should help Zi Yan on his work on 1 GB THPs: splitting a gigantic
THP under a memory pressure
cma_release() has to lock the cma_lock mutex to clear the cma bitmap.
It makes it a blocking function, which complicates its usage from
non-blocking contexts. For instance, hugetlbfs code is temporarily
dropping the hugetlb_lock spinlock to call cma_release().
This patch introduces a non-blocking
On Fri, 2020-10-23 at 02:35 +0530, Aditya wrote:
> On 23/10/20 1:03 am, Joe Perches wrote:
> > On Fri, 2020-10-23 at 00:44 +0530, Aditya wrote:
> > > On 22/10/20 9:40 pm, Joe Perches wrote:
> > > > On Thu, 2020-10-22 at 20:20 +0530, Aditya Srivastava wrote:
> > > > > Presence of hexadecimal
On Thu, Oct 22 2020 at 09:28, Marcelo Tosatti wrote:
> On Wed, Oct 21, 2020 at 10:25:48PM +0200, Thomas Gleixner wrote:
>> The right answer to this is to utilize managed interrupts and have
>> according logic in your network driver to handle CPU hotplug. When a CPU
>> goes down, then the queue
On Thu, Oct 22, 2020 at 01:23:55PM -0700, Sami Tolvanen wrote:
> Use scs_alloc() to allocate also IRQ and SDEI shadow stacks instead of
> using statically allocated stacks.
>
> Signed-off-by: Sami Tolvanen
Reviewed-by: Kees Cook
--
Kees Cook
On Thu, Oct 22, 2020 at 01:23:54PM -0700, Sami Tolvanen wrote:
> The kernel currently uses kmem_cache to allocate shadow call stacks,
> which means an overflow may not be immediately detected and can
> potentially result in another task's shadow stack to be overwritten.
>
> This change switches
--
Mein Name ist Manuel Franco, ich bin der Gewinner des Powerball Mega
Jackpot-Gewinners in Höhe von 768 Millionen US-Dollar aus New Jersey,
USA,
und ich freue mich, Ihnen zu gratulieren, dass Sie zufällig unter den 5
glücklichen Menschen ausgewählt wurden, denen ich jeweils 2 Millionen
Hi Tushar,
On Wed, 2020-09-23 at 12:20 -0700, Tushar Sugandhi wrote:
> Currently, IMA does not provide a generic function for kernel components
> to measure their data. A generic function provided by IMA would
> enable various parts of the kernel with easier and faster on-boarding to
> use IMA
On Thu, Oct 22, 2020 at 03:52:20PM -0500, YiFei Zhu wrote:
> On Mon, Oct 12, 2020 at 7:31 PM YiFei Zhu wrote:
> >
> > On Mon, Oct 12, 2020 at 5:57 PM Kees Cook wrote:
> > > I think it's fine to just have this "dangle" with a help text update of
> > > "if seccomp action caching is supported by
The current code can lose RCU callbacks at shutdown time, which can
result in hangs. This lossage can happen as follows:
o A thread invokes call_rcu_data_free(), which executes up through
the wake_call_rcu_thread(). At this point, the call_rcu_data
structure has been
From: Thomas Gleixner
Lockdep state handling on NMI enter and exit is nothing specific to X86. It's
not any different on other architectures. Also the extra state type is not
necessary, irqentry_state_t can carry the necessary information as well.
Move it to common code and extend
From: Fenghua Yu
PKS allows kernel users to define domains of page mappings which have
additional protections beyond the paging protections.
Add an API to allocate, use, and free a protection key which identifies
such a domain. Export 5 new symbols pks_key_alloc(), pks_mknoaccess(),
From: Ira Weiny
When only user space pkeys are enabled faulting within the kernel was an
unexpected condition which should never happen. Therefore a WARN_ON in
the kernel fault handler would detect if it ever did. Now this is no
longer the case if PKS is enabled and supported.
Report a Pkey
From: Ira Weiny
Protection Keys User (PKU) and Protection Keys Supervisor (PKS) work in
similar fashions and can share common defines. Specifically PKS and PKU
each have:
1. A single control register
2. The same number of keys
3. The same number of bits in the register
From: Ira Weiny
The PKRS MSR is defined as a per-logical-processor register. This
isolates memory access by logical CPU. Unfortunately, the MSR is not
managed by XSAVE. Therefore, tasks must save/restore the MSR value on
context switch.
Define a saved PKRS value in the task struct, as well
From: Fenghua Yu
Protection Keys for Supervisor pages (PKS) enables fast, hardware thread
specific, manipulation of permission restrictions on supervisor page
mappings. It uses the same mechanism of Protection Keys as those on
User mappings but applies that mechanism to supervisor mappings
From: Ira Weiny
The core PKS functionality provides an interface for kernel users to
reserve keys to their domains set up the page tables with those keys and
control access to those domains when needed.
Define test code which exercises the core functionality of PKS via a
debugfs entry. Basic
From: Ira Weiny
Changes from RFC V3[3]
Rebase to TIP master
Update test error output
Standardize on 'irq_state' for state variables
From Dave Hansen
Update commit messages
Add/clean up comments
Add X86_FEATURE_PKS to
From: Ira Weiny
In preparation for adding PKS information to struct irqentry_state_t
change all call sites and usages to pass the struct by reference
instead of by value.
While we are editing the call sites it is a good time to standardize on
the name 'irq_state'.
Signed-off-by: Ira Weiny
From: Ira Weiny
Define a helper, update_pkey_val(), which will be used to support both
Protection Key User (PKU) and the new Protection Key for Supervisor
(PKS) in subsequent patches.
Co-developed-by: Peter Zijlstra
Signed-off-by: Peter Zijlstra
Signed-off-by: Ira Weiny
---
Changes from RFC
From: Ira Weiny
The PKRS MSR is not managed by XSAVE. It is preserved through a context
switch but this support leaves exception handling code open to memory
accesses during exceptions.
2 possible places for preserving this state were considered,
irqentry_state_t or pt_regs.[1] pt_regs was
On 2020-10-22 4:04 p.m., Omar Sandoval wrote:
> On Thu, Oct 22, 2020 at 12:45:25PM -0600, Logan Gunthorpe wrote:
>>
>> On 2020-10-08 10:40 a.m., Logan Gunthorpe wrote:
>>> Hi,
>>>
>>> This series adds blktests for the nvmet passthru feature that was merged
>>> for 5.9. It's been reconciled with
On rare occations there is the following error:
mmc0: Tuning timeout, falling back to fixed sampling clock
There are SD cards which takes a significant longer time to reply to the
first CMD19 command. The eSDHC takes the data timeout value into account
during the tuning period. The SDHCI core
On 22.10.2020 23.02, Kees Cook wrote:
On Thu, Oct 22, 2020 at 01:39:07PM +0300, Topi Miettinen wrote:
But I think SELinux has a more complete solution (execmem) which can track
the pages better than is possible with seccomp solution which has a very
narrow field of view. Maybe this facility
Hi Linus,
Please pull this small refactoring series that moves all the support
functions for file range remapping (aka reflink and dedupe) out of
mm/filemap.c and fs/read_write.c and into fs/remap_range.c.
It's been a full week since the initial discussion[1] on fsdevel, and in
that time, nobody
--
Mein Name ist Manuel Franco, ich bin der Gewinner des Powerball Mega
Jackpot-Gewinners in Höhe von 768 Millionen US-Dollar aus New Jersey,
USA,
und ich freue mich, Ihnen zu gratulieren, dass Sie zufällig unter den 5
glücklichen Menschen ausgewählt wurden, denen ich jeweils 2 Millionen
On Thu, 22 Oct 2020 15:26:53 +0100
Colin King wrote:
> From: Colin Ian King
>
> Fix several spelling mistakes in vm documentation.
>
> Signed-off-by: Colin Ian King
> ---
> Documentation/vm/mmu_notifier.rst | 2 +-
> Documentation/vm/page_migration.rst | 2 +-
>
On Thu, Oct 22 2020 at 23:43, Thomas Gleixner wrote:
> On Fri, Oct 09 2020 at 11:46, David Woodhouse wrote:
> Aside of that it works magically because polarity,trigger and mask bit
> have been set up before. But of course a comment about this is
> completely overrated.
Also this part:
> -static
The driver does not implement a shutdown handler which leads to issues
when using kexec in certain scenarios. The NIC keeps on fetching
descriptors which gets flagged by the IOMMU with errors like this:
DMAR: DMAR:[DMA read] Request device [5e:00.0]fault addr f000
DMAR: DMAR:[DMA read]
From: Al Viro
> Sent: 22 October 2020 20:25
>
> On Thu, Oct 22, 2020 at 12:04:52PM -0700, Nick Desaulniers wrote:
>
> > Passing an `unsigned long` as an `unsigned int` does no such
> > narrowing: https://godbolt.org/z/TvfMxe (same vice-versa, just tail
> > calls, no masking instructions).
> > So
In a heterogeneous multiprocessor system, specifying the 'maxcpus'
parameter on kernel command line does not provide sufficient control
over which CPUs are brought online at kernel boot time, since CPUs may
have nonuniform performance characteristics. Thus, add bootcpus kernel
parameter to control
From: Nick Desaulniers
> Sent: 22 October 2020 20:05
>
...
> Passing an `unsigned long` as an `unsigned int` does no such
> narrowing: https://godbolt.org/z/TvfMxe (same vice-versa, just tail
> calls, no masking instructions).
Right but is the called function going to use 32bit ops
and/or mask
On Thu, Oct 22, 2020 at 12:45:25PM -0600, Logan Gunthorpe wrote:
>
> On 2020-10-08 10:40 a.m., Logan Gunthorpe wrote:
> > Hi,
> >
> > This series adds blktests for the nvmet passthru feature that was merged
> > for 5.9. It's been reconciled with Sagi's blktest series that Omar
> > recently
On Thu, Oct 15, 2020 at 01:52:16AM +, Peng Fan wrote:
> > Subject: [PATCH 07/13] remoteproc: Introduce function rproc_detach()
> >
> > Introduce function rproc_detach() to enable the remoteproc core to release
> > the resources associated with a remote processor without stopping its
> >
Hi Peng - I restarting work on this topic.
On Thu, Oct 15, 2020 at 01:37:42AM +, Peng Fan wrote:
> > Subject: [PATCH 05/13] remoteproc: Add new detach() remoteproc operation
> >
> > Add an new detach() operation in order to support scenarios where the
> > remoteproc core is going away but
Hi Linus!
Latest fixes from the networking tree. Experimenting with the format
of the description further, I'll find out if you liked it based on how
it ends up looking in the tree :)
The following changes since commit 9ff9b0d392ea08090cd1780fb196f36dbb586529:
Merge tag 'net-next-5.10' of
From: Anirudh Ghayal
Convert bindings to YAML. Also add compatible string that adds support
for reporting the VBUS status that can be detected via a dedicated PMIC
pin.
Signed-off-by: Anirudh Ghayal
Signed-off-by: Guru Das Srinagesh
---
.../bindings/extcon/qcom,pm8941-misc.txt | 41
Add support to enable VBUS detection in the pm8941 extcon driver.
Changes from v2:
- Fix YAML errors in dt binding document.
Changes from v1:
- Change bindings from txt to YAML.
Anirudh Ghayal (2):
bindings: pm8941-misc: Convert to YAML and add support for VBUS
detection
extcon:
From: Anirudh Ghayal
VBUS can be detected via a dedicated PMIC pin. Add support
for reporting the VBUS status.
Signed-off-by: Anirudh Ghayal
Signed-off-by: Kavya Nunna
Signed-off-by: Guru Das Srinagesh
---
drivers/extcon/extcon-qcom-spmi-misc.c | 100 ++---
1
On Fri, Oct 09 2020 at 11:46, David Woodhouse wrote:
@@ -45,12 +45,11 @@ enum irq_alloc_type {
};
> +static void mp_swizzle_msi_dest_bits(struct irq_data *irq_data, void *_entry)
> +{
> + struct msi_msg msg;
> + u32 *entry = _entry;
Why is this a void * argument and then converting it
Considering both end_dir_add() and d_alloc_parallel(), the
dir->i_dir_seq wants acquire/release semantics, therefore
micro-optimize for ll/sc archs and use finer grained barriers
to provide (load)-ACQUIRE ordering (L->S + L->L). This comes
at no additional cost for most of x86, as sane tso models
PM8008 is a PMIC that contains 7 LDOs, 2 GPIOs, temperature monitoring,
and can be interfaced over I2C. This driver uses the regmap-irq
framework to handle interrupts, creates a regmap and uses it to
instantiate all the child nodes under it in the device tree.
Only four peripherals have been
Add device tree bindings for the driver for Qualcomm Technology Inc.'s
PM8008 MFD PMIC.
Signed-off-by: Guru Das Srinagesh
---
.../bindings/mfd/qcom,pm8008-irqchip.yaml | 102 +
1 file changed, 102 insertions(+)
create mode 100644
Changes from v1:
- Fixed YAML errors in dt binding document.
This is a follow-up as promised [1] to the earlier attempts [2] [3] to upstream
the driver that has been hitherto used to handle IRQs for Qualcomm's PMICs that
have multiple on-board peripherals when they are interfaced over the I2C
Some MFD chips do not have the register space for their peripherals
mapped out with a fixed stride. Add peripheral address offsets to the
framework to support such address spaces.
In this new scheme, the regmap-irq client registering with the framework
shall have to define the *_base registers
There's nothing special about zram and lzo. It works just fine without it, so
as long as at least one of the other supported compression algorithms is
selected.
Signed-off-by: Rui Salvaterra
---
v2: fix the dependency on CRYPTO.
drivers/block/zram/Kconfig | 6 +-
drivers/block/zram/zcomp.c
On Thu, Oct 22, 2020 at 01:59:32PM -0700, Eric Biggers wrote:
> Also note the following program succeeds on Linux 5.9 on x86_64. On kernels
> that have this bug, it should fail. (I couldn't get it to actually fail, so
> it
> must depend on the compiler and/or the kernel config...)
It doesn't.
Hello Linus,
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
tags/tag-chrome-platform-for-v5.10
for you
Pass a bio to decrypt_bio instead of a buffer_head to decrypt_bh.
Another step towards doing decryption per-BIO instead of per-BH.
Signed-off-by: Matthew Wilcox (Oracle)
---
fs/buffer.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/fs/buffer.c
Use the new decrypt_end_bio() instead of readpage_end_bio() if
fscrypt needs to be used. Remove the old end_buffer_async_read()
now that all BHs go through readpage_end_bio().
Signed-off-by: Matthew Wilcox (Oracle)
---
fs/buffer.c | 198
1
This new data structure allows a task to wait for N things to complete.
Usually the submitting task will handle cleanup, but if it is killed,
the last completer will take care of it.
Signed-off-by: Matthew Wilcox (Oracle)
---
block/blk-core.c| 61
If the filesystem returns an error from get_block, report it
instead of ineffectually setting PageError. Don't bother starting
any I/Os in this case since they won't bring the page Uptodate.
Signed-off-by: Matthew Wilcox (Oracle)
---
fs/buffer.c | 24 ++--
1 file changed,
This patchset does I/Os in larger chunks, if the blocks are adjacent.
More importantly, it returns the actual error from ->readpage for
filesystems which use block_read_full_page(). Unless fscrypt returns
an error, in which case it turns into EIO because it has to roundtrip
through bi_status.
I
Use the new blk_completion infrastructure to wait for multiple I/Os.
Also coalesce adjacent buffer heads into a single BIO instead of
submitting one BIO per buffer head. This doesn't work for fscrypt yet,
so keep the old code around for now.
Signed-off-by: Matthew Wilcox (Oracle)
---
This is prep work for doing decryption at the BIO level instead of
the BH level. It still works on one BH at a time for now.
Signed-off-by: Matthew Wilcox (Oracle)
---
fs/buffer.c | 45 +
1 file changed, 21 insertions(+), 24 deletions(-)
diff --git
On Thu, Oct 22, 2020 at 12:04 PM Andy Shevchenko
wrote:
>
> On Thu, Oct 22, 2020 at 11:53:50AM -0700, Brendan Higgins wrote:
> > On Thu, Oct 22, 2020 at 8:06 AM Andy Shevchenko
> > wrote:
> > > On Wed, Oct 21, 2020 at 10:47:50AM -0700, Daniel Latypov wrote:
>
> ...
>
> > > You need to put
Hi Peter,
On Thu, Oct 22, 2020 at 04:32:36PM +0100, Suzuki Poulose wrote:
> On 10/22/20 4:06 PM, Peter Zijlstra wrote:
> > On Thu, Oct 22, 2020 at 02:30:21PM +0100, Suzuki Poulose wrote:
> > > On 10/22/20 12:32 PM, Peter Zijlstra wrote:
> > > > On Thu, Oct 22, 2020 at 04:27:52PM +0530, Sai
Oops, this is broken, I'll send a v2 soon.
On Thu, 22 Oct 2020 at 17:11, Rui Salvaterra wrote:
>
> There's nothing special about zram and lzo. It works just fine without it, so
> as long as at least one of the other supported compression algorithms is
> selected.
>
> Additionally, drop the
Hi Tony,
I love your patch! Perhaps something to improve:
[auto build test WARNING on s390/features]
[also build test WARNING on linus/master next-20201022]
[cannot apply to kvms390/next linux/master v5.9]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
Hi Tushar,
The above Subject line should be truncated to "IMA: add policy to
measure critical data".
On Wed, 2020-09-23 at 12:20 -0700, Tushar Sugandhi wrote:
> There would be several candidate kernel components suitable for IMA
> measurement. Not all of them would have support for IMA
According to board schematic, PHY provides both, RX and TX delays.
However, according to "fix" Realtek provided for this board, only TX
delay should be provided by PHY.
Tests show that both variants work but TX only PHY delay works
slightly better.
Update ethernet node to reflect the fact that
On 23/10/20 1:03 am, Joe Perches wrote:
> On Fri, 2020-10-23 at 00:44 +0530, Aditya wrote:
>> On 22/10/20 9:40 pm, Joe Perches wrote:
>>> On Thu, 2020-10-22 at 20:20 +0530, Aditya Srivastava wrote:
Presence of hexadecimal address or symbol results in false warning
message by
On Thu, Oct 22, 2020 at 10:00:44AM -0700, Nick Desaulniers wrote:
> On Thu, Oct 22, 2020 at 9:40 AM Matthew Wilcox wrote:
> >
> > On Thu, Oct 22, 2020 at 04:35:17PM +, David Laight wrote:
> > > Wait...
> > > readv(2) defines:
> > > ssize_t readv(int fd, const struct iovec *iov, int
On Thu, Oct 22, 2020 at 06:12:50PM +0300, Vladimir Oltean wrote:
> From: Vladimir Oltean
>
> Similar to the workaround applied by Michael Walle in commit
> c2f448cff22a ("tty: serial: fsl_lpuart: add LS1028A support"), it turns
> out that the LPUARTx_FIFO encoding for fields TXFIFOSIZE and
On Wed, 21 Oct 2020 at 22:52, Naresh Kamboju wrote:
>
> On Wed, 21 Oct 2020 at 22:35, Linus Torvalds
> wrote:
> >
> > On Wed, Oct 21, 2020 at 9:58 AM Naresh Kamboju
> > wrote:
> > >
> > > LTP mm mtest05 (mmstress), mtest06_3 and mallocstress01 (mallocstress)
> > > tested on
> > > x86 KASAN
On Mon, Oct 12, 2020 at 7:31 PM YiFei Zhu wrote:
>
> On Mon, Oct 12, 2020 at 5:57 PM Kees Cook wrote:
> > I think it's fine to just have this "dangle" with a help text update of
> > "if seccomp action caching is supported by the architecture, provide the
> > /proc/$pid ..."
>
> I think it would
Read the 'brcm,tx-amplitude-millivolt' property from Device Tree and
propagate its value into the appropriate test transmit register to
change the TX amplitude.
Signed-off-by: Florian Fainelli
---
drivers/phy/broadcom/phy-brcm-sata.c | 32
1 file changed, 32
Hi Vinod, Kishon,
This patch series allows the configuration of the Broadcom SATA PHY TX
amplitude which may be required in order to meet specific tests.
Thanks!
Changes in v2:
- rebased against phy/next
- added Rob's Acked-by to the dt-binding patch
Florian Fainelli (2):
dt-bindings: phy:
Document a new property which allows the selection of the SATA AFE TX
amplitude in milli Volts. Possible values are 400, 500, 600 and 800mV.
Acked-by: Rob Herring
Signed-off-by: Florian Fainelli
---
Documentation/devicetree/bindings/phy/brcm-sata-phy.txt | 3 +++
1 file changed, 3
Hi!
> > > +++ b/drivers/net/can/ctucanfd/Kconfig
> > > @@ -21,4 +21,15 @@ config CAN_CTUCANFD_PCI
> > > PCIe board with PiKRON.com designed transceiver riser shield is
> > > available at https://gitlab.fel.cvut.cz/canbus/pcie-ctu_can_fd .
> > >
> > > +config CAN_CTUCANFD_PLATFORM
> > > +
On Thu, 2020-10-22 at 13:42 -0700, Nick Desaulniers wrote:
> .On Wed, Oct 21, 2020 at 7:36 PM Joe Perches wrote:
> > Use a more generic form for __section that requires quotes to avoid
> > complications with clang and gcc differences.
[]
> > a quick test of x86_64 and s390 would be good.
x86_64
On 10/20/20 4:59 AM, Serge Semin wrote:
> In accordance with the Generic xHCI bindings the corresponding node
> name is suppose to comply with the Generic USB HCD DT schema, which
> requires the USB nodes to have the name acceptable by the regexp:
> "^usb(@.*)?" . Make sure the
On 10/20/20 4:59 AM, Serge Semin wrote:
> In accordance with the Generic EHCI/OHCI bindings the corresponding node
> name is suppose to comply with the Generic USB HCD DT schema, which
> requires the USB nodes to have the name acceptable by the regexp:
> "^usb(@.*)?" . Make sure the "generic-ehci"
.On Wed, Oct 21, 2020 at 7:36 PM Joe Perches wrote:
>
> Use a more generic form for __section that requires quotes to avoid
> complications with clang and gcc differences.
>
> Remove the quote operator # from compiler_attributes.h __section macro.
>
> Convert all unquoted __section(foo) uses to
On Wed, 14 Oct 2020 15:27:27 -0400, Vivek Unune wrote:
> Add ports 5 and 7 which are connected to gmac cores 1 & 2.
> These will be disabled for now.
>
> Signed-off-by: Vivek Unune
> ---
Applied to devicetree/next, thanks!
--
Florian
On Thu, Oct 22, 2020 at 09:32:55PM +0100 Mel Gorman wrote:
> On Thu, Oct 22, 2020 at 07:59:43PM +0200, Rafael J. Wysocki wrote:
> > > > Agreed. I'd like the option to switch back if we make the default
> > > > change.
> > > > It's on the table and I'd like to be able to go that way.
> > > >
> > >
Hi Tushar,
On Wed, 2020-09-23 at 12:20 -0700, Tushar Sugandhi wrote:
> ima_match_rule_data() permits the func to pass empty func_data.
> For instance, for the following func, the func_data keyrings= is
> optional.
> measure func=KEY_CHECK keyrings=.ima
>
> But a new func in future may want
On Thu, Oct 8, 2020 at 4:22 PM Nick Kralevich wrote:
>
> On Wed, Oct 7, 2020 at 9:01 PM Andrea Arcangeli wrote:
> >
> > Hello Lokesh,
> >
> > On Wed, Oct 07, 2020 at 01:26:55PM -0700, Lokesh Gidra wrote:
> > > On Wed, Sep 23, 2020 at 11:56 PM Lokesh Gidra
> > > wrote:
> > > >
> > > > This
On Thu, Oct 22, 2020 at 07:59:43PM +0200, Rafael J. Wysocki wrote:
> > > Agreed. I'd like the option to switch back if we make the default change.
> > > It's on the table and I'd like to be able to go that way.
> > >
> >
> > Yep. It sounds chicken, but it's a useful safety net and a reasonable
> >
On Thu, 22 Oct 2020 12:30:28 +0200
Peter Zijlstra wrote:
> Subject: lockdep: Fix preemption WARN for spurious IRQ-enable
> From: Peter Zijlstra
> Date: Thu Oct 22 12:23:02 CEST 2020
>
> It is valid (albeit uncommon) to call local_irq_enable() without first
> having called local_irq_disable().
Hi Tony,
I love your patch! Perhaps something to improve:
[auto build test WARNING on s390/features]
[also build test WARNING on linus/master kvms390/next linux/master v5.9
next-20201022]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we
On Thu, Oct 22, 2020 at 8:50 PM Marco Elver wrote:
>
> On Thu, 22 Oct 2020 at 15:19, Andrey Konovalov wrote:
> >
> > TODO: no meaningful description here yet, please see the cover letter
> > for this RFC series.
> >
> > Signed-off-by: Andrey Konovalov
> > Link:
> >
The pull request you sent on Thu, 22 Oct 2020 22:49:05 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kconfig-v5.10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f9893351acaecf0a414baf9942b48d5bb5c688c6
Thank you!
--
The pull request you sent on Thu, 22 Oct 2020 22:46:51 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kbuild-v5.10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/746b25b1aa0f5736d585728ded70a8141da91edb
Thank you!
--
The pull request you sent on Thu, 22 Oct 2020 14:42:47 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git
> tags/modules-for-v5.10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2b71482060e1e6962720dbca1dff702580fa0748
Thank you!
--
Use scs_alloc() to allocate also IRQ and SDEI shadow stacks instead of
using statically allocated stacks.
Signed-off-by: Sami Tolvanen
---
arch/arm64/include/asm/scs.h | 21 ++-
arch/arm64/kernel/entry.S| 6 ++--
arch/arm64/kernel/irq.c | 2 ++
arch/arm64/kernel/scs.c |
On Thu, Oct 22, 2020 at 01:21:10PM -0700, Florian Fainelli wrote:
> On 10/22/20 1:16 PM, Vivek Unune wrote:
> > On Wed, Oct 14, 2020 at 03:27:27PM -0400, Vivek Unune wrote:
> >> Add ports 5 and 7 which are connected to gmac cores 1 & 2.
> >> These will be disabled for now.
> >>
> >> Signed-off-by:
As discussed a few months ago [1][2], virtually mapped shadow call stacks
are better for safety and robustness. This series dusts off the VMAP
option from the original SCS patch series and switches the kernel to use
virtually mapped shadow stacks unconditionally when SCS is enabled.
[1]
The kernel currently uses kmem_cache to allocate shadow call stacks,
which means an overflow may not be immediately detected and can
potentially result in another task's shadow stack to be overwritten.
This change switches SCS to use virtually mapped shadow stacks,
which increases shadow stack
Hello Pavel,
thanks for review.
For everybody: the amount of code, analyses etc. is really huge.
If you do not have time and consider this discussion as lost of your
time and or badwidth send me a note. I will remove your from the
recipients list and if you think that some lists should be
On 10/22/20 1:16 PM, Vivek Unune wrote:
> On Wed, Oct 14, 2020 at 03:27:27PM -0400, Vivek Unune wrote:
>> Add ports 5 and 7 which are connected to gmac cores 1 & 2.
>> These will be disabled for now.
>>
>> Signed-off-by: Vivek Unune
>> ---
>> .../boot/dts/bcm47094-linksys-panamera.dts| 24
On Wed, Oct 14, 2020 at 03:27:27PM -0400, Vivek Unune wrote:
> Add ports 5 and 7 which are connected to gmac cores 1 & 2.
> These will be disabled for now.
>
> Signed-off-by: Vivek Unune
> ---
> .../boot/dts/bcm47094-linksys-panamera.dts| 24 +++
> 1 file changed, 24
101 - 200 of 1016 matches
Mail list logo
