On Tue, Aug 04, 2020 at 10:53:16AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.192 release.
> There are 47 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me kno
On Tue, Aug 04, 2020 at 08:11:45AM +0200, Rasmus Villemoes wrote:
> On 03/08/2020 20.29, Kees Cook wrote:
> > Hi,
> >
> > I wonder if we should explicitly saturate the output of the overflow
> > helpers as a side-effect of overflow detection?
>
> Please no.
I'm entirely on the fence about this,
On Tue, Aug 04, 2020 at 10:53:28AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.137 release.
> There are 52 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me kno
On Tue, Aug 04, 2020 at 10:53:41AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.56 release.
> There are 86 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Tue, Aug 04, 2020 at 10:53:53AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.7.13 release.
> There are 116 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Tue, Aug 04, 2020 at 08:47:18PM +0300, Ilia Lin wrote:
> Hi Andrew and David,
Hi Ilia
Please don't top post.
>
> Thank you for your comments!
>
> The client driver is still work in progress, but it can be seen here:
> https://source.codeaurora.org/quic/la/kernel/msm-4.19/tree/drivers/platfo
On Tue, Aug 4, 2020 at 3:56 AM wrote:
>
> On Mon, Aug 03, 2020 at 05:06:14PM -0700, Josh Don wrote:
> > SMT siblings share caches, so cache hotness should be irrelevant for
> > cross-sibling migration.
> >
> > Proposed-by: Venkatesh Pallipadi
> > Signed-off-by: Josh Don
> > ---
> > kernel/sched
On Tue 04 Aug 00:35 PDT 2020, Amit Pundir wrote:
> On Tue, 4 Aug 2020 at 11:46, Bjorn Andersson
> wrote:
> > On Sat 01 Aug 08:55 PDT 2020, Amit Pundir wrote:
[..]
> > > diff --git a/arch/arm64/boot/dts/qcom/sdm845-beryllium.dts
> > > b/arch/arm64/boot/dts/qcom/sdm845-beryllium.dts
[..]
> > > +/*
On Sat, Jul 25, 2020 at 6:21 AM Kent Gibson wrote:
>
> Add support for edge detection to lines requested using
> GPIO_GET_LINE_IOCTL.
>
> Signed-off-by: Kent Gibson
> ---
[snip!]
> +
> +static irqreturn_t edge_irq_thread(int irq, void *p)
> +{
> + struct edge_detector *edet = p;
> +
On Tue, Aug 4, 2020 at 4:32 AM Kalyan Thota wrote:
>
> DPU resources reserved in the atomic_check path gets unwinded
> during modeset operation before commit happens in a non seamless
> transition.
>
> Update the reservations in the commit path to avoid resource
> failures. Secondly have dummy res
From: Min Li
This update includes adjphase support, more debug logs, firmware name
parameter, correct PTP_CLK_REQ_PEROUT support and use do_aux_work to
do delay work.
Signed-off-by: Min Li
---
drivers/ptp/ptp_idt82p33.c | 233 +
drivers/ptp/ptp_idt82
This is part of the multiplanar and singleplanar unification process.
v4l2_ext_pix_format is supposed to work for both cases.
We also add the concept of modifiers already employed in DRM to expose
HW-specific formats (like tiled or compressed formats) and allow
exchanging this information with the
Hello,
This is v5 of the Extended API for formats and buffers, which introduces
the following new ioctls:
int ioctl(int fd, VIDIOC_G_EXT_PIX_FMT, struct v4l2_ext_pix_format *argp)
int ioctl(int fd, VIDIOC_S_EXT_PIX_FMT, struct v4l2_ext_pix_format *argp)
int ioctl(int fd, VIDIOC_TRY_EXT_PIX_FMT, s
This should simplify things a bit as we now have a single
implementation instead of the MPLANE and !MPLANE versions.
Signed-off-by: Boris Brezillon
Signed-off-by: Helen Koike
---
Changes in v4:
- Update with new format and buffer structs
- Rebased on top of media/master (post 5.8-rc1)
Changes i
From: Hans Verkuil
Those extended buffer ops have several purpose:
1/ Fix y2038 issues by converting the timestamp into an u64 counting
the number of ns elapsed since 1970
2/ Unify single/multiplanar handling
3/ Add a new start offset field to each v4l2 plane buffer info struct
to support t
Add documentation and update references in current documentation for the
Extended API.
Signed-off-by: Helen Koike
---
Changes in v5:
- new patch
.../userspace-api/media/v4l/buffer.rst| 5 +
.../userspace-api/media/v4l/common.rst| 1 +
.../userspace-api/media/v4l/dev-capture.
Just a new version of v4l2_fill_mbus_format() and v4l2_fill_ext_pix_format()
to deal with the new v4l2_ext_pix_format struct.
This is needed to convert the VIMC driver to the EXT_FMT/EXT_BUF iocts.
Signed-off-by: Boris Brezillon
Signed-off-by: Helen Koike
---
Changes in v4:
- Add helper v4l2_fil
The VB2 layer is used by a lot of drivers. Patch it to support the
_EXT_PIX_FMT and _EXT_BUF ioctls in order to ease conversion of existing
drivers to these new APIs.
Note that internally, the VB2 core is now only using ext structs and old
APIs are supported through conversion wrappers.
Signed-of
Convert the driver to the _ext_fmt and _ext_buf API.
Signed-off-by: Boris Brezillon
Signed-off-by: Helen Koike
---
Changes in v4:
- Update with new format and buffer structs
- Rebased on top of media/master (post 5.8-rc1)
Changes in v3:
- Rebased on top of media/master (post 5.4-rc1)
Changes i
On 8/4/20 4:29 PM, Helen Koike wrote:
> Hello,
>
> This is v5 of the Extended API for formats and buffers, which introduces
> the following new ioctls:
>
> int ioctl(int fd, VIDIOC_G_EXT_PIX_FMT, struct v4l2_ext_pix_format *argp)
> int ioctl(int fd, VIDIOC_S_EXT_PIX_FMT, struct v4l2_ext_pix_fo
SMT siblings share caches, so cache hotness should be irrelevant for
cross-sibling migration.
Proposed-by: Venkatesh Pallipadi
Signed-off-by: Josh Don
---
kernel/sched/fair.c | 4
1 file changed, 4 insertions(+)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 1a68a0536add..ab
On 8/3/20 12:16 PM, Sean Christopherson wrote:
> On Mon, Aug 03, 2020 at 10:52:05AM -0500, Brijesh Singh wrote:
>> Thanks for series Sean. Some thoughts
>>
>>
>> On 7/31/20 4:23 PM, Sean Christopherson wrote:
>>> SEV currently needs to pin guest memory as it doesn't support migrating
>>> encrypte
From: Qiuxu Zhuo
Attempt to do function level reset for an RCiEP associated with an
RCEC device on fatal error.
Signed-off-by: Qiuxu Zhuo
---
drivers/pci/pcie/err.c | 31 ++-
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git a/drivers/pci/pcie/err.c b/dri
The Root Complex Event Collectors(RCEC) appear as peers to Root Ports
and also have the AER capability. So add RCEC support to the current AER
service driver and attach the AER service driver to the RCEC device.
Co-developed-by: Qiuxu Zhuo
Signed-off-by: Sean V Kelley
Signed-off-by: Qiuxu Zhuo
From: Qiuxu Zhuo
When an RCEC device signals error(s) to a CPU core, the CPU core
needs to walk all the RCiEPs associated with that RCEC to check
errors. So add the function pcie_walk_rcec() to walk all RCiEPs
associated with the RCEC device.
Co-developed-by: Sean V Kelley
Signed-off-by: Qiuxu
The Root Complex Event Collectors(RCEC) appear as peers of Root Ports
and also have the PME capability. So add RCEC support to the current PME
service driver and attach the PME service driver to the RCEC device.
Co-developed-by: Qiuxu Zhuo
Signed-off-by: Sean V Kelley
Signed-off-by: Qiuxu Zhuo
From: Qiuxu Zhuo
A PCIe Root Complex Event Collector(RCEC) has the base class 0x08,
sub-class 0x07, and programming interface 0x00. Add the class code
0x0807 to identify RCEC devices and add the defines for the RCEC
Endpoint Association Extended Capability.
See PCI Express Base Specification, ve
From: Qiuxu Zhuo
When attempting error recovery for an RCiEP associated with an RCEC device,
there needs to be a way to update the Root Error Status, the Uncorrectable
Error Status and the Uncorrectable Error Severity of the parent RCEC.
So add the 'rcec' field to the pci_dev structure and provid
From: Qiuxu Zhuo
The Root Complex Event Collectors(RCEC) appear as peers to Root Ports
and also have the AER capability. So add RCEC support to the current AER
error injection driver.
Co-developed-by: Sean V Kelley
Signed-off-by: Qiuxu Zhuo
Signed-off-by: Sean V Kelley
---
drivers/pci/pcie/a
From: Jonathan Cameron
Currently the kernel does not handle AER errors for Root Complex integrated
End Points (RCiEPs)[0]. These devices sit on a root bus within the Root Complex
(RC). AER handling is performed by a Root Complex Event Collector (RCEC) [1]
which is a effectively a type of RCiEP on
From: Sean V Kelley
On the use of FLR on RCiEPs for the fatal case, still interested in more
feedback from the earlier discussion here [1]:
[1]
https://lore.kernel.org/linux-pci/c21c050b-48b1-4429-b019-c81f3ab8e...@intel.com/
There is also the question of the absence of an FLR for non-fatal er
From: Qiuxu Zhuo
If a Root Complex Integrated Endpoint (RCiEP) is implemented, errors may
optionally be sent to a corresponding Root Complex Event Collector (RCEC).
Each RCiEP must be associated with no more than one RCEC. Interface errors
are reported to the OS by RCECs.
For an RCEC (technicall
Let's clean it up a bit, simplifying error handling and getting rid of
the label.
Reviewed-by: Baoquan He
Reviewed-by: Pankaj Gupta
Cc: Andrew Morton
Cc: Michal Hocko
Cc: Michael S. Tsirkin
Cc: Mike Kravetz
Signed-off-by: David Hildenbrand
---
mm/page_isolation.c | 17 +++--
1
When introducing virtio-mem, the semantics of ZONE_MOVABLE were rather
unclear, which is why we special-cased ZONE_MOVABLE such that partially
plugged blocks would never end up in ZONE_MOVABLE.
Now that the semantics are much clearer (and will be documented in
a follow-up patch including the new v
Let's move the split comment regarding bootmem allocations and memory
holes, especially in the context of ZONE_MOVABLE, to the PageReserved()
check.
Reviewed-by: Baoquan He
Cc: Andrew Morton
Cc: Michal Hocko
Cc: Michael S. Tsirkin
Cc: Mike Kravetz
Cc: Pankaj Gupta
Signed-off-by: David Hilden
Inside has_unmovable_pages(), we have a comment describing how unmovable
data could end up in ZONE_MOVABLE - via "movablecore". Also, besides
checking if the first page in the pageblock is reserved, we don't
perform any further checks in case of ZONE_MOVABLE.
In case of memory offlining, we set RE
Right now, if we have two isolations racing, we might trigger the
WARN_ON_ONCE() and to dump_page(NULL), dereferencing NULL. Let's just
return directly.
In the future, we might want to report -EAGAIN to the caller instead, as
this could indicate a temporary isolation failure only.
Reviewed-by: Ba
@Andrew can we give this a churn and consider it for v5.9 in case there
are no more comments?
Patch #1-#4,#6 have RBss or ACKs, patch #5 is virtio-mem stuff maintained
by me (and MST is aware).
---
When introducing virtio-mem, the semantics of ZONE_MOVABLE were rather
unclear, which is why we sp
Let's document what ZONE_MOVABLE means, how it's used, and which special
cases we have regarding unmovable pages (memory offlining vs. migration /
allocations).
Acked-by: Mike Rapoport
Cc: Andrew Morton
Cc: Michal Hocko
Cc: Michael S. Tsirkin
Cc: Mike Kravetz
Cc: Mike Rapoport
Cc: Pankaj Gup
On Sat, Jul 25, 2020 at 6:22 AM Kent Gibson wrote:
>
> Update uAPI documentation to deprecate v1 structs and ioctls.
>
> Signed-off-by: Kent Gibson
> ---
> include/uapi/linux/gpio.h | 26 ++
> 1 file changed, 26 insertions(+)
>
> diff --git a/include/uapi/linux/gpio.h b/i
On Tue, Aug 04, 2020 at 07:02:14PM +0200, Vlastimil Babka wrote:
> On 8/3/20 6:30 PM, Uladzislau Rezki (Sony) wrote:
> > Some background and kfree_rcu()
> > ===
> > The pointers to be freed are stored in the per-cpu array to improve
> > performance, to enable an easier-t
On Tue, Aug 04, 2020 at 06:12:03PM +0100, Matthew Wilcox wrote:
> On Tue, Aug 04, 2020 at 07:02:14PM +0200, Vlastimil Babka wrote:
> > > 2) There was a proposal from Matthew Wilcox:
> > > https://lkml.org/lkml/2020/7/31/1015
> > >
> > >
> > > On non-RT, we could make that lock a raw spinlock. O
From: Joe Perches
Date: Mon, 03 Aug 2020 20:23:13 -0700
> Use netdev_ in place of VELOCITY_PRT.
> Use pr_ in place of printk(KERN_.
>
> Miscellanea:
>
> o Add pr_fmt to prefix pr_ output with "via-velocity: "
> o Remove now unused functions and macros
> o Realign some logging lines
> o Remove d
Pavel
On 7/28/20 8:39 AM, Dan Murphy wrote:
Pavel
On 7/22/20 10:31 AM, Dan Murphy wrote:
Introduce the bindings for the Texas Instruments LP5036, LP5030, LP5024,
LP5018, LP5012 and LP5009 RGB LED device driver. The
LP5036/30/24/18/12/9
can control RGB LEDs individually or as part of a contr
On Tue, Aug 4, 2020 at 4:06 PM Arnd Bergmann wrote:
>
> On Tue, Aug 4, 2020 at 5:49 PM Daniel Gutson wrote:
> > On Tue, Aug 4, 2020 at 12:21 PM Arnd Bergmann wrote:
> >>
> >> On Tue, Aug 4, 2020 at 3:58 PM Daniel Gutson
> >> wrote:
> >> >
> >> > Context, the intel-spi has a module argument that
On Sun, Aug 02, 2020 at 07:22:26PM -0300, Jason Gunthorpe wrote:
> On Fri, Jul 31, 2020 at 02:11:22PM -0700, Rustam Kovhaev wrote:
>
> > IB roce driver receives NETDEV_UNREGISTER event, calls dev_hold() and
> > schedules work item to execute, and before wq gets a chance to complete
> > it, we retu
On Fri, Jun 26, 2020 at 2:52 PM Kees Cook wrote:
>
> On Fri, Jun 26, 2020 at 02:09:05PM -0700, Brendan Higgins wrote:
> > This patchset adds a centralized executor to dispatch tests rather than
> > relying on late_initcall to schedule each test suite separately along
> > with a couple of new featu
On Tue, Jul 7, 2020 at 9:31 PM Luis Chamberlain wrote:
>
> On Fri, Jun 26, 2020 at 02:22:11PM -0700, Brendan Higgins wrote:
> > On Fri, Jun 26, 2020 at 2:20 PM Kees Cook wrote:
> > >
> > > On Fri, Jun 26, 2020 at 02:09:06PM -0700, Brendan Higgins wrote:
> > > > Add a linker section where KUnit ca
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c0842fbc1b18c7a044e6ff3e8fa78bfa822c7d1a
commit: 4104a562e0ca62e971089db9d3c47794a0d7d4eb sched/core: Annotate curr
pointer in rq with __rcu
date: 6 months ago
config: x86_64-randconfig-s021-20200805 (atta
On Fri, Jun 26, 2020 at 2:29 PM Kees Cook wrote:
>
> On Fri, Jun 26, 2020 at 02:09:12PM -0700, Brendan Higgins wrote:
> > From: Alan Maguire
> >
> > Add a centralized executor to dispatch tests rather than relying on
> > late_initcall to schedule each test suite separately. Centralized
> > execut
The only usage of dcn20_res_pool_funcs is to assign its address to a
const pointer. Make it const to allow the compiler to put it in
read-only memory.
Signed-off-by: Rikard Falkeborn
---
drivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The only usage of dcn21_res_pool_funcs is to assign its address to a
const pointer. Make it const to allow the compiler to put it in
read-only memory.
Signed-off-by: Rikard Falkeborn
---
drivers/gpu/drm/amd/display/dc/dcn21/dcn21_resource.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The only usage of dcn30_res_pool_funcs is to assign its address to a
const pointer. Make it const to allow the compiler to put it in
read-only memory.
Signed-off-by: Rikard Falkeborn
---
drivers/gpu/drm/amd/display/dc/dcn30/dcn30_resource.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Constify a couple of instances of resource_funcs that are never
modified to allow the compiler to put it in read-only memory.
The other drivers in drivers/gpu/drm/amd/display/dc already have
these as const.
Rikard Falkeborn (3):
drm/amd/display: Constify dcn20_res_pool_funcs
drm/amd/display:
The wrappers in include/linux/pci-dma-compat.h should go away.
The patch has been generated with the coccinelle script below and has been
hand modified to replace GFP_ with a correct flag.
It has been compile tested.
When memory is allocated in 'wanxl_pci_init_one()', GFP_KERNEL can be used
becau
From: Ahmed Abdelsalam
Date: Tue, 4 Aug 2020 07:40:30 +
> This patch allows copying the DSCP from inner IPv4 header to the
> outer IPv6 header, when doing SRv6 Encapsulation.
>
> This allows forwarding packet across the SRv6 fabric based on their
> original traffic class.
>
> Signed-off-by
Previously the stm32h7 interrupt thread cleared all non-masked interrupts.
If an interrupt was to occur during the handling of another interrupt its
flag would be unset, resulting in a lost interrupt.
This patches fixes the issue by clearing only the currently set interrupt
flags.
Signed-off-by: T
On Fri, Jun 26, 2020 at 2:35 PM Kees Cook wrote:
>
> On Fri, Jun 26, 2020 at 02:09:14PM -0700, Brendan Higgins wrote:
> > TAP 14 allows an optional test plan to be emitted before the start of
> > the start of testing[1]; this is valuable because it makes it possible
> > for a test harness to detec
Documentation for sysfs backlight level interface requires that
values in both 'brightness' and 'actual_brightness' files are
interpreted to be in range from 0 to the value given in the
'max_brightness' file.
With amdgpu, max_brightness gives 255, and values written by the user
into 'brightness' a
On Fri, Jun 26, 2020 at 2:40 PM Kees Cook wrote:
>
> On Fri, Jun 26, 2020 at 02:09:15PM -0700, Brendan Higgins wrote:
> > From: David Gow
> >
> > Add a new kernel command-line option, 'kunit_shutdown', which allows the
> > user to specify that the kernel poweroff, halt, or reboot after
> > comple
The wrappers in include/linux/pci-dma-compat.h should go away.
The patch has been generated with the coccinelle script below and has been
hand modified to replace GFP_ with a correct flag.
It has been compile tested.
When memory is allocated in 'fst_add_one()', GFP_KERNEL can be used
because it i
On 8/4/20 2:53 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.7.13 release.
There are 116 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made b
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c0842fbc1b18c7a044e6ff3e8fa78bfa822c7d1a
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 7 weeks ago
config: x86_64-randconfig-s021-20200805 (attache
On 8/4/20 2:53 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.4.56 release.
There are 86 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by
On Tue, Aug 4, 2020 at 12:28 AM Al Viro wrote:
>
> On Mon, Aug 03, 2020 at 09:22:53AM -0700, Suren Baghdasaryan wrote:
> > On Mon, Aug 3, 2020 at 9:12 AM Matthew Wilcox wrote:
> > >
> > > On Mon, Aug 03, 2020 at 09:00:00AM -0700, Suren Baghdasaryan wrote:
> > > > On Mon, Aug 3, 2020 at 8:41 AM Ma
when get_unused_fd_flags returns error, ctx will be freed by
userfaultfd's release function, which is indirectly called by fput().
Also, if anon_inode_getfile_secure() returns an error, then
userfaultfd_ctx_put() is called, which calls mmdrop() and frees ctx.
Also, the O_CLOEXEC was inadvertently
On Tue, Aug 04, 2020 at 10:57:35AM +0200, Remi Bernon wrote:
SNIP
> +
> +int dso__load_bfd_symbols(struct dso *dso, const char *debugfile)
> +{
> + int err = -1;
> + long symbols_size, symbols_count;
> + asection *section;
> + asymbol **symbols, *sym;
> + struct symbol *symbol
On 8/4/20 2:53 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.192 release.
There are 47 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 8/4/20 2:53 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.137 release.
There are 52 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On Tue, 4 Aug 2020, Sumera Priyadarsini wrote:
> This patch adds chain mode to the list of available modes in coccinelle.
Thanks for the commit. In the log message, could you change "coccinelle"
o "coccicheck"? Actually, the modes are not something that are built into
Coccinelle. They are j
On Tue, 4 Aug 2020 12:04:18 +0200 Jiri Pirko wrote:
> Mon, Aug 03, 2020 at 10:57:03PM CEST, k...@kernel.org wrote:
> >I was trying to avoid having to provide a Cartesian product of
> >operation and system disruption level, if any other action can
> >be done "live" at some point.
> >
> >But no stron
Sven,
Sven Schnelle writes:
> --- /dev/null
> +++ b/arch/s390/include/asm/vdso/data.h
> @@ -0,0 +1,13 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#ifndef __S390_ASM_VDSO_DATA_H
> +#define __S390_ASM_VDSO_DATA_H
> +
> +#include
> +#include
I don't think this header needs vdso/datapage.h
>
On Tue, Aug 04, 2020 at 07:27:24PM +0100, Al Viro wrote:
> On Tue, Aug 04, 2020 at 03:44:51PM +, Kalesh Singh wrote:
>
> > Hi Al. Thank you for the comments. Ultimately what we need is to identify
> > processes
> > that hold a file reference to the dma-buf. Unfortunately we can't use only
> >
On Tue, Aug 04, 2020 at 01:31:55PM -0700, Lokesh Gidra wrote:
> when get_unused_fd_flags returns error, ctx will be freed by
> userfaultfd's release function, which is indirectly called by fput().
> Also, if anon_inode_getfile_secure() returns an error, then
> userfaultfd_ctx_put() is called, which
On Tue, Aug 4, 2020 at 9:57 PM Daniel Gutson wrote:
> On Tue, Aug 4, 2020 at 4:06 PM Arnd Bergmann wrote:
> > On Tue, Aug 4, 2020 at 5:49 PM Daniel Gutson wrote:
> > > On Tue, Aug 4, 2020 at 12:21 PM Arnd Bergmann wrote:
> > >> On Tue, Aug 4, 2020 at 3:58 PM Daniel Gutson
> > >> wrote:
> > >
>
On Tue, Aug 04, 2020 at 01:23:50PM +0900, Stafford Horne wrote:
> The OpenRISC user access functions put_user(), get_user() and
> clear_user() were missing proper sparse annotations. This generated
> warnings like the below.
>
> This patch adds the annotations to fix the warnings.
>
> Example wa
Applied the series. Thanks!
Alex
On Tue, Aug 4, 2020 at 4:08 PM Rikard Falkeborn
wrote:
>
> Constify a couple of instances of resource_funcs that are never
> modified to allow the compiler to put it in read-only memory.
>
> The other drivers in drivers/gpu/drm/amd/display/dc already have
> thes
## TL;DR
This patchset adds a centralized executor to dispatch tests rather than
relying on late_initcall to schedule each test suite separately along
with a couple of new features that depend on it.
## What am I trying to do?
Conceptually, I am trying to provide a mechanism by which test suites
TAP 14 allows an optional test plan to be emitted before the start of
the start of testing[1]; this is valuable because it makes it possible
for a test harness to detect whether the number of tests run matches the
number of tests expected to be run, ensuring that no tests silently
failed.
Link[1]:
Add a linker section where KUnit can put references to its test suites.
This patch is the first step in transitioning to dispatching all KUnit
tests from a centralized executor rather than having each as its own
separate late_initcall.
Co-developed-by: Iurii Zaikin
Signed-off-by: Iurii Zaikin
Si
On Tue, Aug 04, 2020 at 01:23:51PM +0900, Stafford Horne wrote:
> As suggested by Linus when reviewing commit 9cb2feb4d21d
> ("arch/openrisc: Fix issues with access_ok()") last year; making
> __range_ok an inline function also fixes the used twice issue that the
> commit was fixing. I agree it's a
Add a brief blurb saying how and when the kunit_test_suite() macro
works to the usage documentation.
Signed-off-by: Brendan Higgins
---
Documentation/dev-tools/kunit/usage.rst | 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/dev-tools/kunit/usage.rst
b/Documentation/dev-to
From: Alan Maguire
Add a centralized executor to dispatch tests rather than relying on
late_initcall to schedule each test suite separately. Centralized
execution is for built-in tests only; modules will execute tests when
loaded.
Signed-off-by: Alan Maguire
Co-developed-by: Iurii Zaikin
Signe
Although we have not seen any actual examples where KUnit doesn't work
because it runs in the late init phase of the kernel, it has been a
concern for some time that this could potentially be an issue in the
future. So, remove KUnit from init calls entirely, instead call directly
from kernel_init()
On Tue, Aug 4, 2020 at 1:45 PM Eric Biggers wrote:
>
> On Tue, Aug 04, 2020 at 01:31:55PM -0700, Lokesh Gidra wrote:
> > when get_unused_fd_flags returns error, ctx will be freed by
> > userfaultfd's release function, which is indirectly called by fput().
> > Also, if anon_inode_getfile_secure() r
On Tue, Aug 04, 2020 at 01:23:54PM +0900, Stafford Horne wrote:
> Now that __user annotations are fixed for openrisc uaccess api's we can
> add checking to the access_ok macro. This patch adds the __chk_user_ptr
> check, on normal builds the added check is a nop.
>
> Signed-off-by: Stafford Horne
From: Wei Yang
Static defined trace_event->type stops at (__TRACE_LAST_TYPE - 1) and
dynamic trace_event->type starts from (__TRACE_LAST_TYPE + 1).
To save one trace_event->type index, let's use __TRACE_LAST_TYPE.
Link:
https://lkml.kernel.org/r/20200703020612.12930-3-richard.weiy...@linux.ali
From: Kevin Hao
We have set 'current_mask' to '&save_cpumask' in its declaration,
so there is no need to assign again.
Link: https://lkml.kernel.org/r/20200730082318.42584-1-haoke...@gmail.com
Signed-off-by: Kevin Hao
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/trace_hwlat.c | 1
From: Wei Yang
The value to be used and compared in trace_search_list() is "last + 1".
Let's just define next to be "last + 1" instead of doing the addition
each time.
Link:
https://lkml.kernel.org/r/20200703020612.12930-2-richard.weiy...@linux.alibaba.com
Signed-off-by: Wei Yang
Signed-off-b
From: Chengming Zhou
When inserting a module, we find all ftrace_ops referencing it on the
ftrace_ops_list. But FTRACE_OPS_FL_DIRECT and FTRACE_OPS_FL_IPMODIFY
flags are special, and should not be set automatically. So warn and
skip ftrace_ops that have these two flags set and adding new code.
Al
From: Josef Bacik
I was attempting to use pid filtering with function_graph, but it wasn't
allowing anything to make it through. Turns out ftrace_trace_task
returns false if ftrace_ignore_pid is not-empty, which isn't correct
anymore. We're now setting it to FTRACE_PID_IGNORE if we need to igno
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: c58b46cba71750c6e969625abb1cf3ddabb15e06
Chengming Zhou (2):
ftrace: Setup correct FTRACE_FL_REGS flags for module
ftrace: Do not let direct or IPMODIFY ftrace_ops be added to module and
set
From: Nick Desaulniers
Just a small cleanup while I was touching this header.
compiler_attributes.h does feature detection of these __attributes__(())
and provides more concise ways to invoke them.
Link: https://lkml.kernel.org/r/20200730224555.2142154-3-ndesaulni...@google.com
Acked-by: Miguel
From: Kevin Hao
In calculation of the cpu mask for the hwlat kernel thread, the wrong
cpu mask is used instead of the tracing_cpumask, this causes the
tracing/tracing_cpumask useless for hwlat tracer. Fixes it.
Link: https://lkml.kernel.org/r/20200730082318.42584-2-haoke...@gmail.com
Cc: Ingo M
Hi Linus,
Please pull the Kunit update for Linux 5.9-rc1.
This Kunit update for Linux 5.9-rc1 consists of:
- Adds a generic kunit_resource API extending it to support
resources that are passed in to kunit in addition kunit
allocated resources. In addition, KUnit resources are now
refcount
On Tue, 4 Aug 2020 11:52:13 +0900
Masami Hiramatsu wrote:
> Since the parse_args() stops parsing at '--', bootconfig_params()
> will never get the '--' as param and initargs_found never be true.
> In the result, if we pass some init arguments via the bootconfig,
> those are always appended to th
From: Peng Fan
In the function trace_uprobe_register(), the statement "return 0;"
out of switch case is dead code, remove it.
Link:
https://lkml.kernel.org/r/1595561064-29186-1-git-send-email-fanp...@loongson.cn
Signed-off-by: Peng Fan
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace
On Tue, Aug 04, 2020 at 01:49:30PM -0700, Lokesh Gidra wrote:
> On Tue, Aug 4, 2020 at 1:45 PM Eric Biggers wrote:
> >
> > On Tue, Aug 04, 2020 at 01:31:55PM -0700, Lokesh Gidra wrote:
> > > when get_unused_fd_flags returns error, ctx will be freed by
> > > userfaultfd's release function, which is
From: Masami Hiramatsu
Remove show_registers() function prototype because this function
has been renamed by commit 57da8b960b9a ("x86: Avoid double stack
traces with show_regs()"), and commit 80006dbee674 ("kprobes/x86:
Remove jprobe implementation") has removed the caller in kprobes.
So this doe
From: Masami Hiramatsu
Add some testcases and examples for value override operator.
Link:
https://lkml.kernel.org/r/159482883824.126704.2166030493721357163.stgit@devnote2
Signed-off-by: Masami Hiramatsu
Signed-off-by: Steven Rostedt (VMware)
---
tools/bootconfig/samples/bad-override.bconf
701 - 800 of 1162 matches
Mail list logo