On 2020-10-10 06:31:57 [+0200], Mike Galbraith wrote:
so this then. Do you have more of these?
--->8
Subject: [PATCH] tcp: Remove superfluous BH-disable around listening_hash
Commit
9652dc2eb9e40 ("tcp: relax listening_hash operations")
removed the need to
On 10/12/20 9:27 AM, Nabeel M Mohamed wrote:
> +#define MPIOC_MAGIC ('2')
Hi,
That value should be documented in
Documentation/userspace-api/ioctl/ioctl-number.rst.
thanks.
--
~Randy
On Mon, Oct 12, 2020 at 09:28:29AM -0700, Dave Hansen wrote:
> kmap_atomic() is always preferred over kmap()/kmap_thread().
> kmap_atomic() is _much_ more lightweight since its TLB invalidation is
> always CPU-local and never broadcast.
>
> So, basically, unless you *must* sleep while the mapping
On Thu, Oct 08, 2020 at 01:26:16PM -0700, Nicolin Chen wrote:
> Hi Krzysztof,
>
> On Thu, Oct 08, 2020 at 12:32:58PM +0200, Krzysztof Kozlowski wrote:
> > On Wed, Oct 07, 2020 at 05:37:44PM -0700, Nicolin Chen wrote:
> > > This is a cleanup change to prepare for new swgroups.
> >
> > What type
On Mon, Oct 12, 2020 at 04:10:45PM +0100, Guillaume Tucker wrote:
> You can get serial console on recent enough Chromebooks with a
> debug interface such as SuzyQable:
>
> https://www.sparkfun.com/products/14746
>
> It's not a USB Type-C adapter, it has a debug interface which
> works with
On Wed, Oct 7, 2020 at 8:41 PM Limonciello, Mario
wrote:
>
> > On Wed, 2020-10-07 at 15:58 +, Limonciello, Mario wrote:
> > >
> > > > On Mon, 2020-10-05 at 12:58 +, Limonciello, Mario wrote:
> > > > > > On modern systems CPU/GPU/... performance is often dynamically
> > > > > >
Add ABGR format with 10-bit components packed in 64-bit per pixel.
This format can be used to handle
VK_FORMAT_R10X6G10X6B10X6A10X6_UNORM_4PACK16 on little-endian
architectures.
Signed-off-by: Matteo Franchin
Reviewed-by: Brian Starkey
Acked-by: Daniel Vetter
---
drivers/gpu/drm/drm_fourcc.c
When the fcport is about to be deleted we should return EBUSY instead
of ENODEV. Only for EBUSY the request will be requeued in a multipath
setup.
Also in case we have a valid qpair but the firmware has not yet
started return EBUSY to avoid dropping the request.
Signed-off-by: Daniel Wagner
---
On Sat, 10 Oct 2020 at 09:15, Xu Yilun wrote:
>
> This driver is for the EMIF private feature implemented under FPGA
> Device Feature List (DFL) framework. It is used to expose memory
> interface status information as well as memory clearing control.
>
> The purpose of memory clearing block is to
On Mon, Oct 12, 2020 at 04:40:40PM +0200, Willy Tarreau wrote:
> Well, to be precise, they don't have *anymore*. I used to exclusively
> select laptops having a serial port given that I was using it daily with
> routers, until I had to resign when I abandonned my good old NC8000 :-/
Yah, with all
On Mon, Oct 12, 2020 at 1:46 PM Hans de Goede wrote:
>
> Hi Daniel,
>
> On 10/12/20 12:30 PM, Daniel Lezcano wrote:
> >
> > Hi Hans,
> >
> > On 07/10/2020 12:43, Hans de Goede wrote:
> >> Hi,
> >>
> >> On 10/6/20 2:20 PM, Daniel Lezcano wrote:
> >>> The density of components greatly increased the
On Mon, Oct 12, 2020 at 09:07:15AM -0700, Arun Easi wrote:
> This does not appear to be cut against the latest for-next/staging; "rval"
> is not used there for the initial set of returns.
Indeed, forgot to use staging. It's against queue. Let me update it.
> Anyway, returning EBUSY is the right
The following changes since commit f4d51dffc6c01a9e94650d95ce0104964f8ae822:
Linux 5.9-rc4 (2020-09-06 17:11:40 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fscrypt-for-linus
for you to fetch changes up to
On 12/10/20 9:48 pm, Masahiro Yamada wrote:
> On Sun, Oct 4, 2020 at 12:19 AM Ujjwal Kumar
> wrote:
>>
>> This patch series aims at removing the dependency on execute
>> bit of the scripts in the kbuild system.
>>
>> If not working with fresh clone of linux-next, clean the srctree:
>> make
Frequency returned by 'cpuinfo_cur_freq' using counters is not fixed
and keeps changing slightly. This change returns a consistent value
from freq_table. If the reconstructed frequency has acceptable delta
from the last written value, then return the frequency corresponding
to the last written
On Sun, Oct 11, 2020 at 11:57 PM Xing Zhengjun
wrote:
>
> Hi Linus,
>
>Do you have time to look at this? Thanks. I re-test it in v5.9-rc8,
> the regression still existed.
This is one of the series vm-scalability tests that got a huge
improvement (up to 160%) when I did the complete page
Hi Lorenzo,
On 08/10/20 8:38 pm, Lorenzo Pieralisi wrote:
> On Thu, Oct 01, 2020 at 07:02:04PM +0530, Kishon Vijay Abraham I wrote:
>
> [...]
>
Yeah, I don't see any registers in the DRA7x PCIe wrapper for disabling
error forwarding.
>>>
>>> It's a DWC port logic register AFAICT, but
If the user wants to stop controlling uclamp and let the task inherit
the value from the group, we need a method to reset.
Add SCHED_FLAG_UTIL_CLAMP_RESET flag to allow the user to reset uclamp via
sched_setattr syscall.
Signed-off-by: Yun Hsiang
---
include/uapi/linux/sched.h | 9 -
Adds buffer management routines used by the mlog IO path.
Mlog objects are containers for record logging. An mlog is
structured as a series of consecutive log blocks where each
log block is exactly one sector in size. Records of
arbitrary size can be appended to an mlog until it's full.
Mlog
Hi Lukasz,
On Monday 12 Oct 2020 at 14:48:20 (+0100), Lukasz Luba wrote:
>
>
> On 10/12/20 11:59 AM, Ionela Voinescu wrote:
> > On Monday 12 Oct 2020 at 11:22:57 (+0100), Lukasz Luba wrote:
> > [..]
> > > > > I thought about it and looked for other platforms' DT to see if can
> > > > > reuse
>
This adds locking hierarchy documentation for mpool and
updates ioctl-number.rst with mpool driver's ioctl code.
Co-developed-by: Greg Becker
Signed-off-by: Greg Becker
Co-developed-by: Pierre Labat
Signed-off-by: Pierre Labat
Co-developed-by: John Groves
Signed-off-by: John Groves
This adds the open, release and mpool management ioctls for
the mpool driver.
The create, destroy, activate, deactivate and rename ioctls
are issued to the mpool control device (/dev/mpoolctl),
and the rest are issued to the mpool device
(/dev/mpool/).
The mpool control device is owned by (root,
This adds headers containing the following on-media formats:
- Mpool superblock
- Object management records: create, update, delete, and erase
- Mpool configuration record
- Media class config and spare record
- OID checkpoint and version record
- Mlog page header and framing records
Mpool metadata is stored in metadata containers (MDC). An
mpool can have a maximum of 256 MDCs, MDC-0 through MDC-255.
The following metadata manager functionality is added here
for object persistence:
- Initialize and validate MDC0
- Allocate and initialize MDC 1-N. An mpool is created with
16
This adds utilities to translate structures to and from their
on-media format. All mpool metadata is stored on media in
little-endian format.
The metadata records are both versioned and contains a record
type. This allows the record format to change over time, new
record types to be added and old
This adds the mblock and mlog management ioctls: alloc, commit,
abort, destroy, read, write, fetch properties etc.
The mblock and mlog management ioctl handlers are thin wrappers
around the core mblock/mlog lifecycle management and IO routines
introduced in an earlier patch.
The object
On 10/12/20 9:19 AM, Eric Biggers wrote:
> On Sun, Oct 11, 2020 at 11:56:35PM -0700, Ira Weiny wrote:
>>> And I still don't really understand. After this patchset, there is still
>>> code
>>> nearly identical to the above (doing a temporary mapping just for a memcpy)
>>> that
>>> would still be
This adds the Kconfig and Makefile for mpool.
Co-developed-by: Greg Becker
Signed-off-by: Greg Becker
Co-developed-by: Pierre Labat
Signed-off-by: Pierre Labat
Co-developed-by: John Groves
Signed-off-by: John Groves
Signed-off-by: Nabeel M Mohamed
---
drivers/Kconfig| 2 ++
This adds a mechanism to track object-level usage metrics and use
that metrics to proactively evict mblock data from the page cache.
The proactive reaping is employed just before the onset of memory
pressure, which greatly improves throughput and reduces tail
latencies for read and memory
This adds utility routines to:
- Create and initialize a media class with an mpool volume
- Initialize and validate superblocks on all media class
volumes
- Open and initialize all media class volumes
- Allocate metadata container 0 (MDC0) and update the
superblock on capacity media class
Metadata manager interface to allocate, commit, abort, erase, read,
write, and destroy objects.
Metadata containers (MDC-1 through MDC-255) store the metadata for
accessing client allocated objects (mblocks and mlogs). An object
identifier for an mblock or mlog encodes the MDC storing its
This adds mpool lifecycle management functions: create,
activate, deactivate, destroy, rename, add a new media
class, fetch properties etc.
An mpool is created with a mandatory capacity media class
volume. A pool drive (PD) instance is initialized for each
media class volume using the attributes
This implements the mlog lifecycle management functions:
allocate, commit, abort, destroy, append, read etc.
Mlog objects are containers for record logging. Mlogs can be
appended with arbitrary sized records and once full, an mlog
must be erased before additional records can be appended.
Mlog
This adds the mpool control plane infrastructure to manage
mpools.
There is a unit object instance for each device object
created by the mpool driver. A minor number is reserved
for each unit object.
The mpool control device (/dev/mpoolctl) gets a minor
number of 0. An mpool device (/dev/mpool/)
This implements the mmap file operation for the mpool driver.
Mblock and mlog writes avoid the Linux page cache. Mblocks are
written, committed, and made immutable before they can be read
either directly (avoiding the page cache) or memory-mapped.
Mlogs are always read and updated directly and
Provides utilities to initialize, read, update, and erase mpool
superblocks.
Mpool stores two copies of superblocks, one at offset 0 and the
other at offset 8K in zone 0 of each media class volume. SB0 is
the authoritative copy and SB1 is used for recovery in the event
of corruption.
The
This adds structures used by mpool ioctls and utility routines
for logging, UUID management etc.
The mpool ioctls can be categorized as follows:
1. IOCTLs issued to the mpool control device (/dev/mpoolctl)
- Mpool life cycle management (MPIOC_MP_*)
2. IOCTLs issued to the mpool device
The smap layer implements a free space map for each media class
volume in an active mpool.
Free space maps are maintained in memory only. When an mpool is
activated, the free space map is reconstructed from the object
metadata read from media. This approach has the following
advantages:
- Objects
Add headers containing the basic in-memory structures used by mpool.
- mclass.h: media classes
- mlog.h: mlog objects
- mp.h, mpcore.h: mpool objects
- params.h: mpool parameters
- pd.h: pool drive interface
- pmd.h, pmd_obj.h: Metadata manager
- sb.h: superblock interface
- smap.h: space map
This patch series introduces the mpool object storage media pool driver.
Mpool implements a simple transactional object store on top of block
storage devices.
Mpool was developed for the Heterogeneous-Memory Storage Engine (HSE)
project, which is a high-performance key-value storage engine
Metadata containers are used for storing and maintaining metadata.
MDC APIs are implemented as helper functions built on a pair of
mlogs per MDC. It embodies the concept of compaction to deal with
one of the mlog pairs filling, what it means to compact is
use-case dependent.
The MDC APIs make it
The pool drive (pd) component interfaces with the block layer to
read, write, flush, and discard mpool objects.
The underlying block device(s) are opened during mpool activation
and remains open until deactivated.
Read/write IO to an mpool device is chunked by the PD layer.
Chunking interleaves
Implements the mblock lifecycle management functions: allocate,
commit, abort, read, write, destroy etc.
Mblocks are containers comprising a linear sequence of bytes that
can be written exactly once, are immutable after writing, and can
be read in whole or in part as needed until deleted.
Mpool
On Mon, 2020-10-12 at 08:16 -0700, Jakub Kicinski wrote:
> On Mon, 12 Oct 2020 14:20:16 +0200 Bartosz Golaszewski wrote:
> > On Mon, Sep 28, 2020 at 9:17 AM Bartosz Golaszewski
> > wrote:
> > >
> > > From: Bartosz Golaszewski
> > >
> > > It's a valid use-case for ixgbe_mii_bus_init() to return
* Masami Hiramatsu wrote:
> From: Peter Zijlstra
>
> Only x86 provides try_cmpxchg() outside of the atomic_t interfaces,
> provide generic fallbacks to create this interface from the widely
> available cmpxchg() function.
>
> Signed-off-by: Peter Zijlstra (Intel)
> Acked-by: Will Deacon
* Masami Hiramatsu wrote:
> From: Peter Zijlstra
>
> Signed-off-by: Peter Zijlstra (Intel)
Because you are forwarding this patch here, I've added your SOB:
Signed-off-by: Masami Hiramatsu
(Let me know if that's not OK.)
Thanks,
Ingo
On Mon, Oct 12, 2020 at 7:46 AM Steven Rostedt wrote:
>
> On Mon, 12 Oct 2020 09:26:13 -0500
> Tom Zanussi wrote:
>
> > Hi Steve,
> >
> > Looks ok to me.
> >
> > Acked-by: Tom Zanussi
>
> Great!
>
> I'll pull this patch into my tree. It doesn't look like patch 2/2 is
> dependent on this and
Linus,
Please pull the latest perf/kprobes git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-kprobes-2020-10-12
# HEAD: bcb53209be5cb32d485507452edda19b78f31d84 kprobes: Fix to check probe
enabled before disarm_kprobe_ftrace()
This tree prepares to unify the
On Sun, Oct 11, 2020 at 11:56:35PM -0700, Ira Weiny wrote:
> >
> > And I still don't really understand. After this patchset, there is still
> > code
> > nearly identical to the above (doing a temporary mapping just for a memcpy)
> > that
> > would still be using kmap_atomic().
>
> I don't
On Sun, Oct 4, 2020 at 12:19 AM Ujjwal Kumar wrote:
>
> This patch series aims at removing the dependency on execute
> bit of the scripts in the kbuild system.
>
> If not working with fresh clone of linux-next, clean the srctree:
> make distclean
> make tools/clean
>
> To test the dependency on
Hi Sanjay,
I love your patch! Perhaps something to improve:
[auto build test WARNING on vkoul-dmaengine/next]
[also build test WARNING on linus/master sparc-next/master v5.9]
[cannot apply to next-20201012]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
On Mon, Oct 12, 2020 at 2:45 AM Jiri Olsa wrote:
>
> On Fri, Oct 09, 2020 at 11:40:56PM -0700, Ian Rogers wrote:
> > The existing approach to synchronization between threads in the numa
> > benchmark is unbalanced mutexes. This synchronization causes thread
> > sanitizer to warn of locks being
commit d97a9d7aea04 ("staging/speakup: Add inflection synth parameter")
introduced a new "inflection" speakup parameter next to "pitch", but
the values of the var_id_t enum are actually used by the keymap tables
so we must not renumber them. The effect was that notably the volume
control shortcut
The existing approach to synchronization between threads in the numa
benchmark is unbalanced mutexes. This synchronization causes thread
sanitizer to warn of locks being taken twice on a thread without an
unlock, as well as unlocks with no corresponding locks.
This change replaces the
On Mon, 12 Oct 2020 14:07:49 +0530 Reji Thomas wrote:
> seg6: Fix End.X nexthop to use oif.
> Currently End.X action doesn't consider the outgoing interface
> while looking up the nexthop.This breaks packet path functionality
> while using link local address as the End.X nexthop.The patch
>
On Sun, Oct 11, 2020 at 11:48:28AM +0900, Daniel Palmer wrote:
> The driver uses the pin names to find the right interrupt for
> a pin from the device tree so this header reduces the need to
> have multiple copies of the same string all over the place.
>
> This header also adds defines for the
On Mon, Oct 12, 2020 at 6:08 PM Marco Elver wrote:
>
> On Mon, 12 Oct 2020 at 17:25, Andrey Konovalov wrote:
> >
> > Currently there's a KCOV remote coverage collection section in
> > __usb_hcd_giveback_urb(). Initially that section was added based on the
> > assumption that
On Sun, 11 Oct 2020 11:48:27 +0900, Daniel Palmer wrote:
> Add a binding description for the MStar/SigmaStar GPIO controller
> found in the MSC313 and later ARMv7 SoCs.
>
> Signed-off-by: Daniel Palmer
> ---
> .../bindings/gpio/mstar,msc313-gpio.yaml | 69 +++
> MAINTAINERS
Linus,
Please pull the latest perf/core git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-core-2020-10-12
# HEAD: f91072ed1b7283b13ca57fcfbece5a3b92726143 perf/core: Fix race in the
perf_mmap_close() function
These are the performance events changes for
On Mon, Oct 12, 2020 at 11:58:58AM +0300, Alexey Budankov wrote:
>
> Read trace files located at data directory into tool process memory.
> Basic analysis support of data directories is provided for report
> mode. Raw dump (-D) and aggregated reports are available for data
> directories, still
On Mon, 12 Oct 2020 at 17:25, Andrey Konovalov wrote:
>
> Currently there's a KCOV remote coverage collection section in
> __usb_hcd_giveback_urb(). Initially that section was added based on the
> assumption that usb_hcd_giveback_urb() can only be called in interrupt
> context as indicated by a
On Mon, 2020-10-12 at 11:33 +0200, Thomas Gleixner wrote:
> On Sun, Oct 11 2020 at 22:15, David Woodhouse wrote:
> > On 11 October 2020 18:12:08 BST, Thomas Gleixner wrote:
> > > On Sat, Oct 10 2020 at 12:58, David Woodhouse wrote:
> > > > On 10 October 2020 12:44:10 BST, Thomas Gleixner
> > >
On Mon, 12 Oct 2020, 2:11am, Daniel Wagner wrote:
> When the fcport is about to be deleted we should return EBUSY instead
> of ENODEV. Only for EBUSY the request will be requeued in a multipath
> setup.
>
> Also in case we have a valid qpair but the firmware has not yet
> started return EBUSY to
On Thu, Oct 08, 2020 at 05:57:23PM +0200, Rafael J. Wysocki wrote:
> On Thu, Oct 8, 2020 at 5:03 PM Ionela Voinescu
> wrote:
[...]
>
> >The PSD domains (ACPI) and the new DT binding will tell
> >which CPUs are actually in the same clock domain for whomever is
> >interested, despite
On Mon, Oct 12, 2020 at 11:57:00AM +0300, Alexey Budankov wrote:
> diff --git a/tools/perf/util/session.h b/tools/perf/util/session.h
> index abdb8518a81f..4fc9ccdf7970 100644
> --- a/tools/perf/util/session.h
> +++ b/tools/perf/util/session.h
> @@ -42,6 +42,7 @@ struct reader {
> u64
On Mon, Oct 12, 2020 at 9:59 PM Johannes Weiner wrote:
>
> On Sat, Oct 10, 2020 at 06:45:21PM +0800, Muchun Song wrote:
> > Move the mem_cgroup_sockets_enabled() checks into memcg socket charge
> > or uncharge functions, so the users don't have to explicitly check that
> > condition.
> >
> > This
On Mon, Oct 12, 2020 at 11:55:07AM +0300, Alexey Budankov wrote:
>
> Open files located at data directory in case of read access mode.
Need some rationale. Is this a bug fix? Did the case not matter
before?
>
> Signed-off-by: Alexey Budankov
> ---
> tools/perf/util/data.c | 4
> 1 file
On 12/10/2020 13:46, Hans de Goede wrote:
> Hi Daniel,
>
> On 10/12/20 12:30 PM, Daniel Lezcano wrote:
>>
>> Hi Hans,
>>
>> On 07/10/2020 12:43, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 10/6/20 2:20 PM, Daniel Lezcano wrote:
The density of components greatly increased the last decade bringing
On Mon, Oct 12, 2020 at 11:22:57AM +0100, Lukasz Luba wrote:
[...]
>
> True, the SCMI clock does not support discovery of clock tree:
> (from 4.6.1 Clock management protocol background)
> 'The protocol does not cover discovery of the clock tree, which must be
> described through firmware tables
On Mon, Oct 12, 2020 at 11:54:24AM +0300, Alexey Budankov wrote:
> @@ -180,7 +183,8 @@ static int ordered_events__deliver_event(struct
> ordered_events *oe,
> ordered_events);
>
> return perf_session__deliver_event(session, event->event,
>
On Sat, Oct 10, 2020 at 04:43:12PM +0800, Chunfeng Yun wrote:
> Add some optional properties which are needed for hard wired devices
>
> Signed-off-by: Chunfeng Yun
> ---
> v2 changes suggested by Rob:
>1. modify pattern to support any USB class
>2. refer to usb-device.yaml instead of
On Mon, Oct 12, 2020 at 05:10:21PM +0200, Lukas Bulwahn wrote:
>
>
> On Mon, 12 Oct 2020, Alan Stern wrote:
> > Real code contains so many assumptions, especially if you include ones
> > which are obvious to everybody, that such a tool seems impractical.
> >
>
> I fear that problem applies to
Hi,
rickyniu writes:
> From: Benoit Goby
missing Signed-off-by for author
> USB accessory mode allows users to connect USB host hardware
> specifically designed for Android-powered devices. The accessories
> must adhere to the Android accessory protocol outlined in the
>
Linus,
Please pull the latest core/static_call git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-static_call-2020-10-12
# HEAD: 69e0ad37c9f32d5aa1beb02aab4ec0cd055be013 static_call: Fix return
type of static_call_init
This tree introduces static_call(),
On Fri, Oct 09, 2020 at 09:01:41AM -0500, Rob Herring wrote:
> On Fri, Oct 09, 2020 at 12:10:03PM +0100, Nicola Mazzucato wrote:
> > Hi Viresh, I'm glad it helped.
> >
> > Please find below my reply.
> >
> > On 10/9/20 6:39 AM, Viresh Kumar wrote:
> > > On 08-10-20, 17:00, Nicola Mazzucato wrote:
Convert Qualcomm cpufreq devicetree binding to YAML.
Signed-off-by: Manivannan Sadhasivam
---
Changes in v2:
* Removed qcom,freq-domain property which doesn't belong to this binding
.../bindings/cpufreq/cpufreq-qcom-hw.txt | 172 ---
.../bindings/cpufreq/cpufreq-qcom-hw.yaml
On Fri, Oct 09, 2020 at 11:09:21AM +0530, Viresh Kumar wrote:
> On 08-10-20, 17:00, Nicola Mazzucato wrote:
> > On 10/8/20 4:03 PM, Ionela Voinescu wrote:
> > > Hi Viresh,
> > >
> > > On Thursday 08 Oct 2020 at 16:32:41 (+0530), Viresh Kumar wrote:
> > >> On 07-10-20, 13:58, Nicola Mazzucato
> -Original Message-
> From: Andreas Schwab
> Sent: Friday, October 9, 2020 11:55 PM
> To: Sagar Kadam
> Cc: linux-kernel@vger.kernel.org; linux-ri...@lists.infradead.org; linux-
> i...@vger.kernel.org; pe...@korsgaard.com; and...@lunn.ch; Paul
> Walmsley ( Sifive) ;
Introduce user-mode Indirect Branch Tracking (IBT) support. Update setup
routines to include IBT.
Signed-off-by: Yu-cheng Yu
---
arch/x86/include/asm/cet.h| 3 ++
arch/x86/include/asm/disabled-features.h | 8 -
arch/x86/kernel/cet.c | 33
From: "H.J. Lu"
When Indirect Branch Tracking (IBT) is enabled, vDSO functions may be
called indirectly, and must have ENDBR32 or ENDBR64 as the first
instruction. The compiler must support -fcf-protection=branch so that it
can be used to compile vDSO.
Signed-off-by: H.J. Lu
Signed-off-by:
From: "H.J. Lu"
Add ENDBR32 to __kernel_vsyscall entry point.
Signed-off-by: H.J. Lu
Signed-off-by: Yu-cheng Yu
Acked-by: Andy Lutomirski
---
arch/x86/entry/vdso/vdso32/system_call.S | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/entry/vdso/vdso32/system_call.S
From: "H.J. Lu"
Update ARCH_X86_CET_STATUS and ARCH_X86_CET_DISABLE for Indirect Branch
Tracking.
Signed-off-by: H.J. Lu
Signed-off-by: Yu-cheng Yu
---
arch/x86/kernel/cet_prctl.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cet_prctl.c
Introduce Kconfig option X86_BRANCH_TRACKING_USER.
Indirect Branch Tracking (IBT) provides protection against CALL-/JMP-
oriented programming attacks. It is active when the kernel has this
feature enabled, and the processor and the application support it.
When this feature is enabled, legacy
An indirect CALL/JMP moves the indirect branch tracking (IBT) state machine
to WAIT_ENDBR status until the instruction reaches an ENDBR opcode. If the
CALL/JMP does not reach an ENDBR opcode, the processor raises a control-
protection fault. WAIT_ENDBR status can be read from MSR_IA32_U_CET.
Update arch_setup_elf_property() for Indirect Branch Tracking.
Signed-off-by: Yu-cheng Yu
---
arch/x86/Kconfig | 2 ++
arch/x86/kernel/process_64.c | 8
2 files changed, 10 insertions(+)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 15c7f2606c9d..cc9876f85e91
Control-flow Enforcement (CET) is a new Intel processor feature that blocks
return/jump-oriented programming attacks. Details are in "Intel 64 and
IA-32 Architectures Software Developer's Manual" [1].
This is the second part of CET and enables Indirect Branch Tracking (IBT).
It is built on top
On Sun, Oct 11, 2020 at 11:15:14PM +0200, Clément Péron wrote:
> make dtbs_check warm about unknown address/size-cells property in the
> pinetab device-tree.
>
> This is because these information are not necessary.
>
> Drop them.
>
> Signed-off-by: Clément Péron
Queued as a fix for 5.10
On Mon, Oct 12, 2020 at 7:35 AM Daniel Vetter wrote:
>
> On Sun, Oct 11, 2020 at 07:09:34PM -0700, Rob Clark wrote:
> > From: Rob Clark
> >
> > Unfortunately, due to an dev_pm_opp locking interaction with
> > mm->mmap_sem, we need to do pm get before aquiring obj locks,
> > otherwise we can have
Shadow Stack provides protection against function return address
corruption. It is active when the processor supports it, the kernel has
CONFIG_X86_SHADOW_STACK_USER, and the application is built for the feature.
This is only implemented for the 64-bit kernel. When it is enabled, legacy
Hi,
rickyniu writes:
> Below commit is to add log and send uevent:
> 0003-ANDROID-usb-f_accessory-send-uevent-for-51-52-reques.patch
if you're sending something new...
> Benoit Goby (1):
> ANDROID: usb: gadget: f_accessory: Add Android Accessory function
>
> Vijayavardhan Vennapusa (1):
>
On the same principle as commit 773edeadf672 ("powerpc/mm: Add mask
of possible MMU features"), add mask for MMU features that are
always there in order to optimise out dead branches.
Signed-off-by: Christophe Leroy
---
v2: Features must be anded with MMU_FTRS_POSSIBLE instead of ~0, otherwise
A control-protection fault is triggered when a control-flow transfer
attempt violates Shadow Stack or Indirect Branch Tracking constraints.
For example, the return address for a RET instruction differs from the copy
on the Shadow Stack; or an indirect JMP instruction, without the NOTRACK
prefix,
INCSSP(Q/D) increments shadow stack pointer and 'pops and discards' the
first and the last elements in the range, effectively touches those memory
areas.
The maximum moving distance by INCSSPQ is 255 * 8 = 2040 bytes and
255 * 4 = 1020 bytes by INCSSPD. Both ranges are far from PAGE_SIZE.
Thus,
Account shadow stack pages to stack memory.
Signed-off-by: Yu-cheng Yu
---
arch/x86/mm/pgtable.c | 7 +++
include/linux/pgtable.h | 11 +++
mm/mmap.c | 5 +
3 files changed, 23 insertions(+)
diff --git a/arch/x86/mm/pgtable.c b/arch/x86/mm/pgtable.c
index
Kernel read-only PTEs are setup as _PAGE_DIRTY_HW. Since these become
shadow stack PTEs, remove the dirty bit.
Signed-off-by: Yu-cheng Yu
Cc: "H. Peter Anvin"
Cc: Kees Cook
Cc: Thomas Gleixner
Cc: Dave Hansen
Cc: Christoph Hellwig
Cc: Andy Lutomirski
Cc: Ingo Molnar
Cc: Borislav Petkov
This patch adds basic shadow stack enabling/disabling routines. A task's
shadow stack is allocated from memory with VM_SHSTK flag and has a fixed
size of min(RLIMIT_STACK, 4GB).
Signed-off-by: Yu-cheng Yu
---
arch/x86/include/asm/cet.h| 28
Shadow stack accesses are those that are performed by the CPU where it
expects to encounter a shadow stack mapping. These accesses are performed
implicitly by CALL/RET at the site of the shadow stack pointer. These
accesses are made explicitly by shadow stack management instructions like
WRUSSQ.
After the introduction of _PAGE_COW, a modified page's PTE can have either
_PAGE_DIRTY_HW or _PAGE_COW. Change _PAGE_DIRTY to _PAGE_DIRTY_BITS.
Signed-off-by: Yu-cheng Yu
Reviewed-by: Kees Cook
Cc: David Airlie
Cc: Joonas Lahtinen
Cc: Jani Nikula
Cc: Daniel Vetter
Cc: Rodrigo Vivi
Cc:
The kernel allocates (and frees on thread exit) a new shadow stack for a
pthread child.
It is possible for the kernel to complete the clone syscall and set the
child's shadow stack pointer to NULL and let the child thread allocate
a shadow stack for itself. There are two issues in
Before introducing _PAGE_COW for non-hardware memory management purposes in
the next patch, rename _PAGE_DIRTY to _PAGE_DIRTY_HW and _PAGE_BIT_DIRTY to
_PAGE_BIT_DIRTY_HW to make meanings more clear. There are no functional
changes from this patch.
Signed-off-by: Yu-cheng Yu
Reviewed-by: Kees
601 - 700 of 1792 matches
Mail list logo
