From: Maurizio
If PCRs 8 - 9 are set (i.e. not all-zeros), cal_bootaggr should include
them into the digest.
Signed-off-by: Maurizio Drocco
---
src/evmctl.c | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/src/evmctl.c b/src/evmctl.c
index 1d065ce..554571e
On Thu, Jun 18, 2020 at 05:49:19AM +, Sargun Dhillon wrote:
> On Wed, Jun 17, 2020 at 03:03:23PM -0700, Kees Cook wrote:
> > [...]
> > static inline int fd_install_received_user(struct file *file, int __user
> > *ufd,
> >unsigned int o_flags)
> > {
>
> On Jun 18, 2020, at 2:09 AM, Athira Rajeev
> wrote:
>
>
>
>> On 02-May-2020, at 5:51 AM, Song Liu wrote:
>>
>> This patch tries to enable PMU sharing. When multiple perf_events are
>> counting the same metric, they can share the hardware PMU counter. We
>> call these events as
IMA is not considering TPM registers 8-9 when calculating the boot
aggregate. When registers 8-9 are used to store measurements of the
kernel and its command line (e.g., grub2 bootloader with tpm module
enabled), IMA should include them in the boot aggregate.
Signed-off-by: Maurizio Drocco
---
Hi,
On Thu, Jun 18, 2020 at 11:05 AM Stephen Boyd wrote:
>
> Quoting Douglas Anderson (2020-06-18 08:06:26)
> > @@ -126,20 +120,23 @@ static void handle_fifo_timeout(struct spi_master
> > *spi,
> > struct geni_se *se = >se;
> >
> > spin_lock_irq(>lock);
> > -
On 6/18/2020 11:33 AM, Rob Herring wrote:
> On Wed, Jun 17, 2020 at 12:02 PM Wesley Cheng wrote:
>
> You are duplicating everything in usb-connector.yaml. You should have
> a $ref to it.
>
Hi Rob,
Sure, I will add a reference to that doc.
>
> This is wrong. The connector binding says port
On Thu, Jun 18, 2020 at 12:10:38PM +0200, Vlastimil Babka wrote:
>
> On 6/17/20 7:49 PM, Kees Cook wrote:
> > On Wed, Jun 10, 2020 at 06:31:35PM +0200, Vlastimil Babka wrote:
> >> The function cache_from_obj() was added by commit b9ce5ef49f00 ("sl[au]b:
> >> always get the cache from its page in
On Thu, Jun 18, 2020 at 10:56:14AM +0200, Christian Brauner wrote:
> On Mon, Jun 15, 2020 at 08:25:15PM -0700, Kees Cook wrote:
> > In preparation for users of the "install a received file" logic outside
> > of net/ (pidfd and seccomp), relocate and rename __scm_install_fd() from
> >
the below-mentioned commit moved headers to inlucde/linux/soc/mmp. MAINTAINERS
was updated, but include/ was omitted.
Fixes: 32adcaa010 ("ARM: mmp: move cputype.h to include/linux/soc/")
Signed-off-by: Ralf Ramsauer
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Wed, Jun 17, 2020 at 09:18:34AM +0200, Geert Uytterhoeven wrote:
> Hi Thierry,
>
> On Mon, Jun 15, 2020 at 4:17 PM Thierry Reding
> wrote:
> > The PWM core will soon change the duty cycle and period of PWMs to 64
> > bits to allow for a broader range of values. Use a 64-bit format
> >
On 18/06/2020 21.21, Kanchan Joshi wrote:
On Thu, Jun 18, 2020 at 10:04:32AM +0200, Matias Bjørling wrote:
On 17/06/2020 19.23, Kanchan Joshi wrote:
This patchset enables issuing zone-append using aio and io-uring
direct-io interface.
For aio, this introduces opcode IOCB_CMD_ZONE_APPEND.
On Thu, Jun 18, 2020 at 10:35:27AM -0700, Matthew Wilcox wrote:
> On Thu, Jun 18, 2020 at 07:30:49PM +0200, Uladzislau Rezki wrote:
> > > I'd suggest:
> > >
> > > rcu_lock_acquire(_callback_map);
> > > trace_rcu_invoke_kfree_bulk_callback(rcu_state.name,
> > >
Make the nvme code more uniform by initializing struct members at
declaration time. This change is done both in drivers/nvme/host/ and
drivers/nvme/target/.
This is how the design pattern was in nvme, before workarounds for a gcc
bug were introduced in commit e44ac588cd61
Workarounds for gcc issues with initializers and anon unions was first
introduced in commit e44ac588cd61 ("drivers/block/nvme-core.c: fix build
with gcc-4.4.4").
The gcc bug in question has been fixed since gcc 4.6.0:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10676
The minimum gcc version for
Workarounds for gcc issues with initializers and anon unions was first
introduced in commit e44ac588cd61 ("drivers/block/nvme-core.c: fix build
with gcc-4.4.4").
The gcc bug in question has been fixed since gcc 4.6.0:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10676
The minimum gcc version for
Cyril Hrubis writes:
> What is does is to write:
>
> (void*)1 to u_debugreg[0]
> (void*)1 to u_debugreg[7]
> do_debug addr to u_debugreg[0]
>
> Looking at the kernel code the write to register 7 enables the breakpoints and
> what we attempt here is to change an invalid address
Hi,
my test box won't boot 5.8-rc1 all the way but stops at
...
fb0: switching to nouveaufb from EFI VGA
<-- EOF
I've bisected it to the commit in $Subject, see below. Unfortunately, it
doesn't revert cleanly so I can't really do the final test of reverting
it ontop of 5.8-rc1 to confirm that
On 6/18/20 12:50 PM, Eugeniy Paltsev wrote:
> Hi Vineet,
>
> could you also peek this patch to for-curr as we don't have any disagreement
> about it?
>
> I'll respin the rest of the patches later. Thanks.
> ---
> Eugeniy Paltsev
Added !
-Vineet
On Thu, Jun 18, 2020 at 05:29:00PM +, Chaitanya Kulkarni wrote:
> I'm not against the code cleanup and it always welcome.
> Please also have a look at other comment.
>
> >> What is the issue with existing code that we need this patch for ?
> >>
> >
> > Hello Chaitanya,
> >
> > This is just
From: Maciej Żenczykowski
This is a 5.8-rc1 regression.
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Fixes: 2c78ee898d8f ("bpf: Implement CAP_BPF")
Signed-off-by: Maciej Żenczykowski
---
kernel/bpf/syscall.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Mon, Jun 15, 2020 at 11:47 PM David Gow wrote:
>
> When separating out different phases of running tests[1]
> (build/exec/parse/etc), the format of the KunitResult tuple changed
> (adding an elapsed_time variable). This is not populated during a build
> failure, causing kunit.py to crash.
>
>
On Thu, Jun 18, 2020 at 12:10:38PM +0200, Vlastimil Babka wrote:
>
> On 6/17/20 7:49 PM, Kees Cook wrote:
> > On Wed, Jun 10, 2020 at 06:31:35PM +0200, Vlastimil Babka wrote:
> >> The function cache_from_obj() was added by commit b9ce5ef49f00 ("sl[au]b:
> >> always get the cache from its page in
No functional change, avoid non-inclusive naming schemes.
Signed-off-by: Alex Williamson
---
drivers/vfio/vfio.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
index 580099afeaff..833da937b7fc 100644
---
On Thu, 18 Jun 2020, Kees Cook wrote:
> On Wed, Jun 17, 2020 at 08:54:03PM +0200, Julia Lawall wrote:
> >
> >
> > On Wed, 17 Jun 2020, Kees Cook wrote:
> >
> > > On Mon, Jun 15, 2020 at 01:20:45PM +0300, Denis Efremov wrote:
> > > > +@as@
> > > > +expression E1, E2;
> > > > +@@
> > > > +
> > >
On Thu, Jun 18, 2020 at 10:37:07AM +0200, Vlastimil Babka wrote:
> On 6/10/20 6:31 PM, Vlastimil Babka wrote:
> > There are few places that call kmem_cache_debug(s) (which tests if any of
> > debug
> > flags are enabled for a cache) immediatelly followed by a test for a
> > specific
> > flag.
This series attempts to address the report that uclamp logic could be expensive
sometimes and shows a regression in netperf UDP_STREAM under certain
conditions.
The first patch is a fix for how struct uclamp_rq is initialized which is
required by the 2nd patch which contains the real 'fix'.
There is a report that when uclamp is enabled, a netperf UDP test
regresses compared to a kernel compiled without uclamp.
https://lore.kernel.org/lkml/20200529100806.ga3...@suse.de/
While investigating the root cause, there were no sign that the uclamp
code is doing anything particularly
struct uclamp_rq was zeroed out entirely in assumption that in the first
call to uclamp_rq_inc() they'd be initialized correctly in accordance to
default settings.
But when next patch introduces a static key to skip
uclamp_rq_{inc,dec}() until userspace opts in to use uclamp, schedutil
will fail
On Thu, Jun 18, 2020 at 10:37:07AM +0200, Vlastimil Babka wrote:
> On 6/10/20 6:31 PM, Vlastimil Babka wrote:
> > There are few places that call kmem_cache_debug(s) (which tests if any of
> > debug
> > flags are enabled for a cache) immediatelly followed by a test for a
> > specific
> > flag.
On Thu, Jun 18, 2020 at 09:33:08AM +0200, Vlastimil Babka wrote:
> On 6/18/20 2:35 AM, Roman Gushchin wrote:
> > On Wed, Jun 17, 2020 at 04:35:28PM -0700, Andrew Morton wrote:
> >> On Mon, 8 Jun 2020 16:06:52 -0700 Roman Gushchin wrote:
> >>
> >> > Instead of having two sets of kmem_caches: one
On Wed, Jun 17, 2020 at 08:54:03PM +0200, Julia Lawall wrote:
>
>
> On Wed, 17 Jun 2020, Kees Cook wrote:
>
> > On Mon, Jun 15, 2020 at 01:20:45PM +0300, Denis Efremov wrote:
> > > +@as@
> > > +expression E1, E2;
> > > +@@
> > > +
> > > +array_size(E1, E2)
> >
> > BTW, is there a way yet in
On Thu, Jun 18, 2020 at 07:55:35AM -0700, Shakeel Butt wrote:
> Not sure if my email went through, so, re-sending.
No, I've got it, jut was busy with the other stuff.
>
> On Mon, Jun 8, 2020 at 4:07 PM Roman Gushchin wrote:
> >
> > From: Johannes Weiner
> >
> [...]
> > @@ -3003,13 +3004,16 @@
Hi Vineet,
could you also peek this patch to for-curr as we don't have any disagreement
about it?
I'll respin the rest of the patches later. Thanks.
---
Eugeniy Paltsev
From: Eugeniy Paltsev
Sent: Thursday, June 4, 2020 20:39
To:
[ Explicitly added architecture lists and developers to the cc to make
this more visible ]
On Wed, Jun 17, 2020 at 12:38 AM Christoph Hellwig wrote:
>
> Andrew and I decided to drop the patches implementing your suggested
> rename of the probe_kernel_* and probe_user_* helpers from -mm as there
This set looks good to me.
Reviewed-by : Tom Rix
Tom
On 6/18/20 8:25 AM, Xu Yilun wrote:
> Updated the regmap & indirect access support for spi-altera.
>
> Patch #1, #2, #3 is already applied.
> Patch #4 is an 1:1 replacement of of readl/writel with regmap_read/write
> Patch #5 introduced a
IMA_APPRAISE_BOOTPARAM has been marked as dependent on !IMA_ARCH_POLICY in
compile time, enforcing the appraisal whenever the kernel had the arch
policy option enabled.
However it breaks systems where the option is actually set but the system
wasn't booted in a "secure boot" platform. In this
On 6/18/20 3:11 PM, jim.cro...@gmail.com wrote:
> On Thu, Jun 18, 2020 at 12:17 PM Jason Baron wrote:
>>
>>
>>
>> On 6/18/20 1:40 PM, Petr Mladek wrote:
>>> On Thu 2020-06-18 18:19:12, Petr Mladek wrote:
On Wed 2020-06-17 10:25:35, Jim Cromie wrote:
> 1. Add a user-flag [u] which
On Thu, Jun 18, 2020 at 10:08 PM Dominique Martinet
wrote:
>
> Alexander Kapshuk wrote on Thu, Jun 18, 2020:
> > Address sparse nonderef rcu warnings:
> > net/9p/client.c:790:17: warning: incorrect type in argument 1 (different
> > address spaces)
> > net/9p/client.c:790:17:expected struct
On 18/06/2020 11:57, Dinghao Liu wrote:
> pm_runtime_get_sync() increments the runtime PM usage counter even
> when it returns an error code. Thus a pairing decrement is needed on
> the error handling path to keep the counter balanced.
>
> Signed-off-by: Dinghao Liu
> ---
>
> Changelog:
>
>
> On Jun 18, 2020, at 12:02 PM, Peter Zijlstra wrote:
>
> On Thu, Jun 18, 2020 at 11:36:53AM -0700, Andy Lutomirski wrote:
>
>> I wasn't imagining going far down the rabbit hole at all -- I think
>> that, at most, we should cover the path for when the fault wasn't a
>> BUG/WARN in the first
Hi Linus
Please consider pulling,
Best regards,
- Arnaldo
The following changes since commit 69119673bd50b176ded34032fadd41530fb5af21:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2020-06-16
17:44:54 -0700)
are available in the Git repository at:
On Thu, Jun 18, 2020 at 10:09 PM Dominique Martinet
wrote:
>
> Alexander Kapshuk wrote on Thu, Jun 18, 2020:
> > Address sparse endian warning:
> > net/9p/trans_fd.c:932:28: warning: incorrect type in assignment (different
> > base types)
> > net/9p/trans_fd.c:932:28:expected restricted
On Thu, Jun 18, 2020 at 10:04:32AM +0200, Matias Bjørling wrote:
On 17/06/2020 19.23, Kanchan Joshi wrote:
This patchset enables issuing zone-append using aio and io-uring direct-io
interface.
For aio, this introduces opcode IOCB_CMD_ZONE_APPEND. Application uses start LBA
of the zone to
On Thu, 2020-06-18 at 10:42 +0530, Sumit Garg wrote:
> On Thu, 18 Jun 2020 at 10:29, Sumit Garg
> wrote:
[...]
> > > typedef struct
> > > {
> > > uint32_t timeLow;
> > > uint16_t timeMid;
> > > uint16_t timeHiAndVersion;
> > > uint8_t clockSeqAndNode[8];
> > > }
Make use of the struct_size() helper instead of an open-coded version
in order to avoid any potential type mistakes.
This code was detected with the help of Coccinelle and, audited and
fixed manually.
Signed-off-by: Gustavo A. R. Silva
---
drivers/vfio/vfio_iommu_type1.c | 2 +-
1 file
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 1b5044021070efa3259f3e9548dc35d1eb6aa844
commit: 57430471e2fa60a412e220fa3014567e792aaa6f drm/amdgpu: Add support for
USBC PD FW download
date: 4 months ago
config: riscv-randconfig-s032-20200618
ID 1 is already used by the IOVA range capability, use ID 2.
Reported-by: Liu Yi L
Cc: Kirti Wankhede
Fixes: ad721705d09c ("vfio iommu: Add migration capability to report supported
features")
Signed-off-by: Alex Williamson
---
include/uapi/linux/vfio.h |2 +-
1 file changed, 1
On Thu, Jun 18, 2020 at 12:17 PM Jason Baron wrote:
>
>
>
> On 6/18/20 1:40 PM, Petr Mladek wrote:
> > On Thu 2020-06-18 18:19:12, Petr Mladek wrote:
> >> On Wed 2020-06-17 10:25:35, Jim Cromie wrote:
> >>> 1. Add a user-flag [u] which works like the [pfmlt] flags, but has no
> >>> effect on
Alexander Kapshuk wrote on Thu, Jun 18, 2020:
> Address sparse endian warning:
> net/9p/trans_fd.c:932:28: warning: incorrect type in assignment (different
> base types)
> net/9p/trans_fd.c:932:28:expected restricted __be32 [addressable]
> [assigned] [usertype] s_addr
>
Alexander Kapshuk wrote on Thu, Jun 18, 2020:
> Address sparse nonderef rcu warnings:
> net/9p/client.c:790:17: warning: incorrect type in argument 1 (different
> address spaces)
> net/9p/client.c:790:17:expected struct spinlock [usertype] *lock
> net/9p/client.c:790:17:got struct
Commit
bf2c59fce4074 ("sched/core: Fix illegal RCU from offline CPUs")
introduced a definition for mmdrop() but a a few lines above there is
already mmdrop() defined as static inline.
Remove the newly introduced mmdrop() definition.
Signed-off-by: Sebastian Andrzej Siewior
---
On Thu, Jun 18, 2020 at 01:57:33PM -0400, Steven Rostedt wrote:
> On Tue, Jun 09, 2020 at 02:25:09PM -0700, Guenter Roeck wrote:
> > >
> > > Still occurring on Linus' tree. This needs to be fixed. (And not by
> > > removing
> > > support for randstruct; that's not a "fix"...)
> > >
> >
> >
Currently there is no method to know the correct order of the colors for
a test image generated by tpg. Write a function that returns a string of
colors' order given a tpg. It returns a NULL pointer in case of test
patterns which do not have a well defined colors' order. Hence add a
NULL check for
This patchset aims to add a method to display the correct order of
colors for a test image generated. It does so by adding a function
which returns a string of correct order of the colors for a test
pattern. It then adds a control in vimc which displays the string
over test image. It also
Add a control in VIMC to display information such as the correct oder of
colors for a given test pattern, brightness, hue, saturation, contrast
and, width and height at sensor over test image; and display that
information.
Signed-off-by: Kaaira Gupta
---
drivers/media/test-drivers/vimc/Kconfig
On Thu, Jun 18, 2020 at 08:34:48PM +0200, Uladzislau Rezki wrote:
> > > >
> > > > I suspect that he would like to keep the tracing.
> > > >
> > > > It might be worth trying the branches, given that they would be constant
> > > > and indexed by "i". The compiler might well remove the
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: 56ce93700eb630a8d894f5a578f166888ae8cba6
Gitweb:
https://git.kernel.org/tip/56ce93700eb630a8d894f5a578f166888ae8cba6
Author:Benjamin Thiel
AuthorDate:Sat, 06 Jun 2020 14:37:43 +02:00
On Thu, Jun 18, 2020 at 11:36:53AM -0700, Andy Lutomirski wrote:
> I wasn't imagining going far down the rabbit hole at all -- I think
> that, at most, we should cover the path for when the fault wasn't a
> BUG/WARN in the first place. I admit that, for #UD in particular,
> this isn't a big
> -->If fail, need to free previous malloc memory
I suggest to improve this change description.
How does the proposed addition of the function call “macvlan_flush_sources”
fit to this information?
Regards,
Markus
Hi Heikki and Rob,
(trimming text):
On Mon, Jun 15, 2020 at 04:22:07PM +0300, Heikki Krogerus wrote:
> On Fri, Jun 12, 2020 at 10:34:06AM -0700, Prashant Malani wrote:
> > Hi Rob,
> > > Yes, but let's stop calling it a mux. It's a "USB Type C signal routing
> > > blob".
> >
> > Ack.
> >
> >
On Thu, Jun 18, 2020 at 09:59:05AM -0700, Linus Torvalds wrote:
>
> The new warnings don't seem to be due to the kernel test robot having
> an old version of sparse, but just because the error strings changed,
> and presumably the kernel test robot has some "ignore old sparse
> warnings" logic.
>
On Thu, Jun 18, 2020 at 11:37:51AM -0700, Matthew Wilcox wrote:
> On Thu, Jun 18, 2020 at 08:23:33PM +0200, Uladzislau Rezki wrote:
> > > +void vfree_bulk(size_t count, void **addrs)
> > > +{
> > > + unsigned int i;
> > > +
> > > + BUG_ON(in_nmi());
> > > + might_sleep_if(!in_interrupt());
> > > +
On Thu, Jun 18, 2020 at 10:23:38AM -0700, Rajat Jain wrote:
> Thanks Greg and Andy for your continued inputs, and thanks Ashok for chiming
> in.
>
> On Thu, Jun 18, 2020 at 9:23 AM Raj, Ashok wrote:
> >
> > Hi Greg,
> >
> >
> > On Thu, Jun 18, 2020 at 06:02:12PM +0200, Greg Kroah-Hartman wrote:
Hi Niklas,
I love your patch! Yet something to improve:
[auto build test ERROR on block/for-next]
[also build test ERROR on linus/master v5.8-rc1 next-20200618]
[cannot apply to hch-configfs/for-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting
On Wed, 17 Jun 2020 07:51:13 -0700, Douglas Anderson wrote:
> From: Ravi Kumar Bokka
>
> This switches the bindings over from txt to yaml.
>
> Signed-off-by: Ravi Kumar Bokka
> Signed-off-by: Douglas Anderson
> ---
>
> Changes in v3:
> - Split conversion to yaml into separate patch new in
David Heidelberg writes:
> is there chance to get this patch included or could be this issue
> solved with different approach?
Included into what? This patch is incorrect as I pointed out in review
here:
On Thu, Jun 18, 2020 at 07:16:19AM +, Damien Le Moal wrote:
On 2020/06/18 2:27, Kanchan Joshi wrote:
From: Selvakumar S
Introduce IOCB_ZONE_APPEND flag, which is set in kiocb->ki_flags for
zone-append. Direct I/O submission path uses this flag to send bio with
append op. And completion
On Thu, Jun 18, 2020 at 08:23:33PM +0200, Uladzislau Rezki wrote:
> > +void vfree_bulk(size_t count, void **addrs)
> > +{
> > + unsigned int i;
> > +
> > + BUG_ON(in_nmi());
> > + might_sleep_if(!in_interrupt());
> > +
> > + for (i = 0; i < count; i++) {
> > + void *addr =
On Thu, Jun 18, 2020 at 8:50 AM Peter Zijlstra wrote:
>
> On Thu, Jun 18, 2020 at 07:57:35AM -0700, Andy Lutomirski wrote:
> >
> >
> > > On Jun 18, 2020, at 7:50 AM, Peter Zijlstra wrote:
> > >
> > > vmlinux.o: warning: objtool: exc_invalid_op()+0x47: call to
> > > probe_kernel_read() leaves
On Mon, 15 Jun 2020 09:58:35 +0200, Flavio Suligoi wrote:
> Fix typo: "triger" --> "trigger"
>
> Signed-off-by: Flavio Suligoi
> Acked-by: Guo Ren
> ---
>
> v1: add Acked-by: Guo Ren
>
> Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt | 2 +-
>
From: Andrea Parri (Microsoft) Sent: Wednesday, June
17, 2020 9:47 AM
>
> The spinlock is (now) *not used to protect test-and-set accesses
> to attributes of the structure or sc_list operations.
>
> There is, AFAICT, a distinct lack of {WRITE,READ}_ONCE()s in the
> handling of channel->state,
From: Andrea Parri (Microsoft) Sent: Wednesday, June
17, 2020 9:47 AM
>
> storvsc uses the spinlock of the hv_device's primary channel to
> serialize modifications of stor_chns[] performed by storvsc_do_io()
> and storvsc_change_target_cpu(), when it could/should use a (per-)
> storvsc_device
> > >
> > > I suspect that he would like to keep the tracing.
> > >
> > > It might be worth trying the branches, given that they would be constant
> > > and indexed by "i". The compiler might well remove the indirection.
> > >
> > > The compiler guys brag about doing so, which of course might
Address sparse endian warning:
net/9p/trans_fd.c:932:28: warning: incorrect type in assignment (different base
types)
net/9p/trans_fd.c:932:28:expected restricted __be32 [addressable]
[assigned] [usertype] s_addr
net/9p/trans_fd.c:932:28:got unsigned long
Signed-off-by: Alexander
Address sparse nonderef rcu warnings:
net/9p/client.c:790:17: warning: incorrect type in argument 1 (different
address spaces)
net/9p/client.c:790:17:expected struct spinlock [usertype] *lock
net/9p/client.c:790:17:got struct spinlock [noderef] *
net/9p/client.c:792:48: warning:
On Wed, Jun 17, 2020 at 12:02 PM Wesley Cheng wrote:
>
> Introduce the dt-binding for enabling USB type C orientation and role
> detection using the PM8150B. The driver will be responsible for receiving
> the interrupt at a state change on the CC lines, reading the orientation/role,
> and
On Thu, Jun 18, 2020 at 05:25:24PM +, Song Liu wrote:
> PID: 80430 TASK: 888d92c62a80 CPU: 24 COMMAND: "25_scheduler"
> #0 [fe4cfd88] machine_kexec at 8104a646
> #1 [fe4cfdd8] __crash_kexec at 8114a82f
> #2 [fe4cfea0] panic at 810ba99c
>
From: Andrea Parri (Microsoft) Sent: Wednesday, June
17, 2020 9:47 AM
>
> None of the readers/updaters of sc_list rely on channel->lock for
> synchronization.
>
> Signed-off-by: Andrea Parri (Microsoft)
> ---
> drivers/hv/channel_mgmt.c | 25 ++---
> 1 file changed, 6
From: Andrea Parri (Microsoft) Sent: Wednesday, June
17, 2020 9:47 AM
>
> The primitive currently uses channel->lock to protect the loop over
> sc_list w.r.t. list additions/deletions but it doesn't protect the
> target_cpu(s) loads w.r.t. a concurrent target_cpu_store(): while the
> data races
The BeagleBoard.org PocketBeagle has P1 and P2 headers [0] which expose
many of the TI AM3358 SoC balls to stacking expansion boards called
"capes", or to other external connections like jumper wires connected
to a breadboard.
Note: the AM3358 die is actually embedded inside of the OSD335x-SM
Hi John,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linux/master]
[also build test WARNING on linus/master v5.8-rc1 next-20200618]
[cannot apply to pmladek/for-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
Andy Lutomirski writes:
> Is there a plan to deal with:
>
> /*
> * This function has some ABI oddities.
> *
> * A 32-bit ptracer probably expects that writing FS or GS will change
> * FSBASE or GSBASE respectively. In the absence of FSGSBASE support,
>
Signed-off-by: kernel test robot
---
printk.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 7642ef634956f..d812ada06735f 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -434,7 +434,7 @@ static
On Thu, Jun 18, 2020 at 11:15:41AM -0700, Matthew Wilcox wrote:
> On Thu, Jun 18, 2020 at 07:56:23PM +0200, Uladzislau Rezki wrote:
> > If we mix pointers, then we can do free per pointer only. I mean in that
> > case we will not be able to use kfree_bulk() interface for freeing SLAB
> > memory
On Wed, Jun 17, 2020 at 6:17 AM Cyril Hrubis wrote:
>
> Hi!
> > > >> FYI, we noticed the following commit (built with gcc-9):
> > > >>
> > > >> commit: 2bbc68f8373c0631ebf137f376fbea00e8086be7 ("x86/entry: Convert
> > > >> Debug exception to IDTENTRY_DB")
> > > >>
Hi Shiju,
On 15/06/2020 10:53, Shiju Jose wrote:
> Add support to notify the vendor specific non-fatal HW errors
> to the drivers for the error recovery.
This doesn't apply cleanly to v5.8-rc1... thanks for waiting for the merge
window to
finish, but please rebase onto the latest and greatest
On 6/18/20 1:40 PM, Petr Mladek wrote:
> On Thu 2020-06-18 18:19:12, Petr Mladek wrote:
>> On Wed 2020-06-17 10:25:35, Jim Cromie wrote:
>>> 1. Add a user-flag [u] which works like the [pfmlt] flags, but has no
>>> effect on callsite behavior; it allows incremental marking of
>>> arbitrary sets
On Wed, Jun 17, 2020 at 10:08:03PM +0800, Jing Xiangfeng wrote:
> The callers pass the pointer '' or 'private_data' to
> srpt_cm_req_recv(), and 'private_data' is initialized in srp_send_req().
> 'sdev' is allocated and stored in srpt_add_one(). It's easy to show that
> sdev and req are always
On Thu, Jun 18, 2020 at 10:19 AM Petr Mladek wrote:
>
> On Wed 2020-06-17 10:25:35, Jim Cromie wrote:
OK.
Please tell me how this chunk of prose fails to explain a use case for
the u-flag
we can differ on how useful it looks.
if u-flag is useful, then filtering on flags is also needed,
to use
On Thu, Jun 18, 2020 at 07:56:23PM +0200, Uladzislau Rezki wrote:
> If we mix pointers, then we can do free per pointer only. I mean in that
> case we will not be able to use kfree_bulk() interface for freeing SLAB
> memory and the code would converted to something like:
>
>
> while
On Thu, 18 Jun 2020, Steven French wrote:
> Wasn't this fixed last year by:
It looks like it. I received the message today from kbuild, but I didn't
look further than that. Perhaps it is an old tree somehow.
julia
>
> commit 8bd3754cff3aa6e80e73cb56042cdc6f76d6510e
> Author: Dan Carpenter
On Thu, 2020-06-18 at 11:05 -0700, Lakshmi Ramasubramanian wrote:
> On 6/18/20 10:41 AM, Mimi Zohar wrote:
>
> >
> > For the reasons that I mentioned previously, unless others are willing
> > to add their Reviewed-by tag not for the audit aspect in particular,
> > but IMA itself, I'm not
On Thu, Jun 18, 2020 at 7:18 AM Thomas Gleixner wrote:
>
> Sasha,
>
> Sasha Levin writes:
> > Changes from v12:
> > - Reformat the series to be closer to the reverted codebase for easier
> >review.
> > - Drop a few of the changes introduced in v8 and v9.
>
> I've pushed the lot out to
>
>
On Wed, Jun 17, 2020 at 11:47 PM Luca Ceresoli wrote:
>
> Hi Rob, Moritz,
>
> On 18/06/20 00:39, Rob Herring wrote:
> > On Thu, Jun 11, 2020 at 11:11:43PM +0200, Luca Ceresoli wrote:
> >> The INIT_B is used by the 6 and 7 series to report the programming status,
> >> providing more control and
On Thu, Jun 18, 2020 at 02:25:05PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky
>
> Hi,
>
> The following two fixes are user-visible one. The first patch is needed
> to continue to use RAW_PACKET QPs after PR [1] is merged and new FW will
> be released. The second patch fixes wrongly
Quoting Douglas Anderson (2020-06-18 08:06:26)
> @@ -126,20 +120,23 @@ static void handle_fifo_timeout(struct spi_master *spi,
> struct geni_se *se = >se;
>
> spin_lock_irq(>lock);
> - reinit_completion(>xfer_done);
> - mas->cur_mcmd = CMD_CANCEL;
> -
On 6/18/20 10:41 AM, Mimi Zohar wrote:
For the reasons that I mentioned previously, unless others are willing
to add their Reviewed-by tag not for the audit aspect in particular,
but IMA itself, I'm not comfortable making this change all at once.
Previously I suggested making the existing
On Thu, Jun 18, 2020 at 10:03:45AM -0700, Tony Lindgren wrote:
> * Drew Fustini [200617 17:10]:
> > Tony - does this look ok for 5.9?
>
> Yes looks OK to me.
>
> Just wondering, are the line with "NA" not used internally either?
> If the "NA" lines are used internally, we should probably use
>
On Thu, Jun 18, 2020 at 6:42 PM Steven Rostedt wrote:
>
> On Thu, 18 Jun 2020 01:12:37 +0200
> Jann Horn wrote:
>
> > static ftrace_func_t ftrace_ops_get_list_func(struct ftrace_ops *ops)
> > +static ftrace_asm_func_t ftrace_ops_get_list_func(struct ftrace_ops *ops)
> > {
> > +#if
On Thu, Jun 18, 2020 at 07:35:20PM +0200, Uladzislau Rezki wrote:
> > >
> > > I don't think that replacing direct function calls with indirect function
> > > calls is a great suggestion with the current state of play around branch
> > > prediction.
> > >
> > > I'd suggest:
> > >
> > >
401 - 500 of 1319 matches
Mail list logo
