We should free the initrd reserved memblock in an aligned manner,
because the initrd reserves the memblock in an aligned manner
in arm64_memblock_init().
Otherwise there are some fragments in memblock_reserved regions
after free_initrd_mem(). e.g.:
/sys/kernel/debug/memblock # cat reserved
0
Friendly ping ...
On 2019/7/3 10:09, Zhiqiang Liu wrote:
> From: Zhiqiang Liu
>
> Users can call ref_module func in their modules to construct
> relationships with other modules. However, the holders
> '/sys/module//holders' of the target module donot include
> the users` module. So lsmod comman
On Sat, Jul 06, 2019 at 12:28:01AM -0400, Theodore Ts'o wrote:
> On Fri, Jul 05, 2019 at 12:10:55PM -0700, Paul E. McKenney wrote:
> >
> > Exactly, so although my patch might help for CONFIG_PREEMPT=n, it won't
> > help in your scenario. But looking at the dmesg from your URL above,
> > I see the
Two iscsi fixes. One for an oops in the client which can be triggered
by the server authentication protocol and the other in the target code
which causes data corruption.
The patch is available here:
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
The short changelog is:
> Unless you use an upstream coccinelle script or you share the one you
> are using, this is not a useful information.
How do you think about to extend a software development discussion
on a topic like “Pretty-printing of code for ternary operators?”?
https://systeme.lip6.fr/pipermail/cocci/2019-J
Fix typo in the comment on top of __irq_domain_add().
Signed-off-by: Zenghui Yu
---
kernel/irq/irqdomain.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
index a453e22..db7b713 100644
--- a/kernel/irq/irqdomain.c
+++ b/kernel/i
On Fri, Jul 05, 2019 at 12:10:55PM -0700, Paul E. McKenney wrote:
>
> Exactly, so although my patch might help for CONFIG_PREEMPT=n, it won't
> help in your scenario. But looking at the dmesg from your URL above,
> I see the following:
I just tested with CONFIG_PREEMPT=n
% grep CONFIG_PREEMPT /
The phy_dn variable is still being used in of_phy_connect() after the
of_node_put() call, which may result in use-after-free.
Fixes: 1dd2d06c0459 ("net: Rework pasemi_mac driver to use of_mdio
infrastructure")
Signed-off-by: Wen Yang
Cc: "David S. Miller"
Cc: Thomas Gleixner
Cc: Luis Chamberla
This worked fine in next-20190618, but in next-20190701 I'm seeing dmesg
entries at boot:
dmesg | grep -i x.509
[8.345699] Loading compiled-in X.509 certificates
[8.366137] Problem loading in-kernel X.509 certificate (-13)
[8.507348] cfg80211: Loading compiled-in X.509 certificates for
There is a possible use-after-free issue in the axienet_probe():
1701: np = of_parse_phandle(pdev->dev.of_node, "axistream-connected", 0);
1702: if (np) {
...
1787: of_node_put(np); ---> released here
1788: lp->eth_irq = platform_get_irq(pdev, 0);
1789: } else {
...
1801:
The gpr_np variable is still being used in dev_dbg() after the
of_node_put() call, which may result in use-after-free.
Fixes: de3578c198c6 ("can: flexcan: add self wakeup support")
Signed-off-by: Wen Yang
Cc: Wolfgang Grandegger
Cc: Marc Kleine-Budde
Cc: "David S. Miller"
Cc: linux-...@vger.ke
$(obj) is not used in the top Makefile at all. $(src) is used in
3 sites, but they can be replaced with $(srctree).
Signed-off-by: Masahiro Yamada
---
Makefile | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/Makefile b/Makefile
index 014390e32b0e..a5615edf2196 10064
In old days, Kbuild always used an absolute path for $(srctree).
Since commit 890676c65d69 ("kbuild: Use relative path when building in
the source tree"), $(srctree) is '.' when not using O=.
Yet, using absolute paths is useful in some cases even without O=, for
instance, to create a cscope file
Commit 25b146c5b8ce ("kbuild: allow Kbuild to start from any directory")
deprecated KBUILD_SRCTREE.
It is only used in tools/testing/selftest/ to distinguish out-of-tree
build. Replace it with a new boolean flag, building_out_of_srctree.
I also replaced the conditional ($(srctree),.) because the
That thing should not be turned on by default, especially since
it's not quiet in case it finds no problems. Geert has sent the obvious
fix quite a few times, but it fell through the cracks.
The following changes since commit 570d7a98e7d6d5d8706d94ffd2d40adeaa318332:
vfs: move_mount: r
On Fri, Jul 5, 2019 at 4:03 PM Jan Kara wrote:
>
> Yeah, I guess revert of 5fd4ca2d84b2 at this point is probably the best we
> can do. Let's CC Linus, Andrew, and Greg (Linus is travelling AFAIK so I'm
> not sure whether Greg won't do release for him).
I'm back home now, although possibly jetlag
The pull request you sent on Fri, 5 Jul 2019 13:40:37 -0400:
> git://linux-nfs.org/~bfields/linux.git tags/nfsd-5.2-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a8f46b5afe1c0a83c3013a339e6aeccc2f37342d
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.k
The pull request you sent on Fri, 5 Jul 2019 22:29:30 +0200:
> https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9fdb86c8cf9ae201d97334ecc2d1918800cac424
Thank you!
--
Deet-doot-dot, I am a bot.
https://ko
The pull request you sent on Fri, 5 Jul 2019 21:21:29 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-current
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/881ed91f7db58fcbe8fdca056907991c3c9d8f2d
Thank you!
--
Deet-doot-dot, I am a bot
On Fri, Jul 5, 2019 at 3:10 PM Alan Stern wrote:
>
> On Thu, 4 Jul 2019, Ryan Kennedy wrote:
>
> > usb_amd_find_chipset_info() is used for chipset detection for
> > several quirks. It is strange that its return value indicates
> > the need for the PLL quirk, which means it is often ignored.
> > Th
From: Wanpeng Li
Dedicated instances are currently disturbed by unnecessary jitter due
to the emulated lapic timers fire on the same pCPUs which vCPUs resident.
There is no hardware virtual timer on Intel for guest like ARM. Both
programming timer in guest and the emulated timer fires incur vme
Dedicated instances are currently disturbed by unnecessary jitter due
to the emulated lapic timers fire on the same pCPUs which vCPUs resident.
There is no hardware virtual timer on Intel for guest like ARM. Both
programming timer in guest and the emulated timer fires incur vmexits.
This patchset
From: Wanpeng Li
Commit 61abdbe0bcc2 ("kvm: x86: make lapic hrtimer pinned") pinned the
lapic timer to avoid to wait until the next kvm exit for the guest to
see KVM_REQ_PENDING_TIMER set. There is another solution to give a kick
after setting the KVM_REQ_PENDING_TIMER bit, make lapic timer unpin
Hi Michael,
On Sat, Jul 6, 2019 at 9:05 AM Michael Kelley wrote:
>
> From: Stephen Rothwell Sent: Friday, July 5, 2019
> 1:31 AM
> >
> > After merging the kbuild tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> >
> > In file included from :
> > include/clocksource/
I need your help
From: Al Viro
make unhash_mnt() return the mountpoint to be dropped, let callers
deal with it.
Signed-off-by: Al Viro
---
fs/namespace.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/fs/namespace.c b/fs/namespace.c
index 746e3fd1f430..b7059a4f07e3 100644
--- a/
From: Al Viro
We used to need rather convoluted ordering trickery to guarantee
that dput() of ex-mountpoints happens before the final mntput()
of the same. Since we don't need that anymore, there's no point
playing with fs_pin for that.
Signed-off-by: Al Viro
---
fs/fs_pin.c| 10 +
From: Al Viro
Signed-off-by: Al Viro
---
fs/mount.h | 1 -
fs/namespace.c | 66 +-
2 files changed, 28 insertions(+), 39 deletions(-)
diff --git a/fs/mount.h b/fs/mount.h
index 6250de544760..84aa8cdf4971 100644
--- a/fs/mount.h
+++ b
From: Al Viro
... not since 1e9c75fb9c47 ("mnt: fix __detach_mounts infinite loop")
Signed-off-by: Al Viro
---
fs/namespace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/namespace.c b/fs/namespace.c
index 6fbc9126367a..746e3fd1f430 100644
--- a/fs/namespace.c
+++ b/f
From: Al Viro
Currently, running into a shrink list that contains dentries from different
filesystems can cause several unpleasant things for shrink_dcache_parent()
and for umount(2).
The first problem is that there's a window during shrink_dentry_list() between
__dentry_kill() takes a victim ou
From: Al Viro
Lift getting the original mount (dentry is actually not needed at all)
of the mountpoint into the callers - to do_move_mount() and pivot_root()
level. That simplifies the cleanup in those and allows to get saner
arguments for attach_mnt_recursive().
Signed-off-by: Al Viro
---
fs
Currently, we handle mountpoint dentry lifetime in a very convoluted
way.
* each struct mount attached to a mount tree contributes to ->d_count
of mountpoint dentry (pointed to by ->mnt_mountpoint).
* permanently detaching a mount from a mount tree moves the reference
into -
Nice to meet you
From: Stephen Rothwell Sent: Friday, July 5, 2019 1:31
AM
>
> After merging the kbuild tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> In file included from :
> include/clocksource/hyperv_timer.h:18:10: fatal error: asm/mshyperv.h: No
> such file or
> directory
>
In case if dma mapped packet needs to be sent, like with XDP
page pool, the "mapped" submit can be used. This patch adds dma
mapped submit based on regular one.
Signed-off-by: Ivan Khoronzhuk
---
v9..v8
- fix potential warnings on arm64 caused by typos in type casting
drivers/net/ethernet/ti/d
On Fri, 5 Jul 2019, Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 5 Jul 2019 17:11:37 +0200
>
> Avoid an extra function call
Not really. You've avoided an extra statement.
> by using a ternary operator instead of a conditional statement for a
> setting selection.
>
> This issu
On 7/5/19 8:12 AM, Grygorii Strashko wrote:
Hi Santosh,
This series is set of platform changes required to enable NETCP CPTS reference
clock selection and final patch to enable CPTS for Keystone 66AK2E/L/HK SoCs.
Those patches were posted already [1] together with driver's changes, so this
is r
Hi Dan,
On Fri, 5 Jul 2019 15:32:19 -0700 Dan Williams wrote:
>
> On Fri, Jul 5, 2019 at 12:20 AM Stephen Rothwell
> wrote:
> >
> > After merging the nvdimm tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > In file included from :32:
> > ./usr/include/linux/virt
On Wed, Jul 03, 2019 at 03:04:45AM +0300, Boaz Harrosh wrote:
> On 20/06/2019 01:37, Dave Chinner wrote:
> <>
> >
> > I'd prefer it doesn't get lifted to the VFS because I'm planning on
> > getting rid of it in XFS with range locks. i.e. the XFS_MMAPLOCK is
> > likely to go away in the near term b
On 7/4/19 10:44 PM, Daniel Drake wrote:
On Wed, Jul 3, 2019 at 8:59 PM Jes Sorensen wrote:
My point is this seems to be very dongle dependent :( We have to be
careful not breaking it for some users while fixing it for others.
Do you still have your device?
Once we get to the point when you a
From: Sebastian Andrzej Siewior
Date: Thu, 4 Jul 2019 17:38:02 +0200
> For spinlocks the type spinlock_t should be used instead of "struct
> spinlock".
>
> Use spinlock_t for spinlock's definition.
>
> Cc: Jakub Kicinski
> Cc: "David S. Miller"
> Cc: oss-driv...@netronome.com
> Cc: net...@vg
On Fri 05-07-19 20:19:48, Mikhail Gavrilov wrote:
> Hey folks.
> Excuse me, is anybody read my previous message?
> 5.2-rc7 is still affected by this issue [the logs in file
> dmesg-5.2rc7-0.1.tar.xz] and I worry that stable 5.2 would be released
> with this bug because there is almost no time left
Please Cc Andrew Morton on future follow
ups.
On Sat, Jul 06, 2019 at 12:19:16AM +0200, Radoslaw Burny wrote:
> On Fri, Jul 5, 2019 at 10:02 PM Luis Chamberlain wrote:
> >
> >
> > Please re-state the main fix in the commit log, not just the subject.
>
> Sure, I'll do this. Just to make sure - f
From: Huazhong Tan
Date: Thu, 4 Jul 2019 22:04:19 +0800
> This patch-set includes cleanups and bugfixes for
> the HNS3 ethernet controller driver.
>
> [patch 1/9] fixes VF's broadcast promisc mode not enabled after
> initializing.
>
> [patch 2/9] adds hints for fibre port not support flow contr
From: Hayes Wang
Date: Thu, 4 Jul 2019 17:36:32 +0800
> Set the flag of RTL8152_UNPLUG if and only if the device is unplugged.
> Some error codes sometimes don't mean the real disconnection of usb device.
> For those situations, set the flag of RTL8152_UNPLUG causes the driver skips
> some flows
On 05/07/2019 22:45:39+0200, Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 5 Jul 2019 22:37:58 +0200
>
> Avoid an extra function call by using a ternary operator instead of
> a conditional statement for a setting selection.
>
Please elaborate on why this is a good thing.
> This iss
On Fri, Jul 5, 2019 at 12:20 AM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the nvdimm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from :32:
> ./usr/include/linux/virtio_pmem.h:19:2: error: unknown type name 'uint64_t'
> uint64_t start;
On Fri, Jul 5, 2019 at 3:26 PM Olof Johansson via Linux.Kernel.Org
wrote:
This didn't work as I anticipated. Please ignore, apologies for the spam.
-Olof
On Fri, Jul 5, 2019 at 3:25 PM Olof Johansson via Linux.Kernel.Org
wrote:
Hmm, well, that didn't work like I expected to. Sorry for the noise.
-Olof
From: Hariprasad Kelam
Date: Thu, 4 Jul 2019 08:29:06 +0530
> Remove unneeded memset as alloc_etherdev is using kvzalloc which uses
> __GFP_ZERO flag
>
> Signed-off-by: Hariprasad Kelam
Applied.
se_sock'
>
>
> Full randconfig file is attached.
>
These build errors still happen in linux-next of 20190705...
--
~Randy
On Fri, Jul 5, 2019 at 10:02 PM Luis Chamberlain wrote:
>
>
> Please re-state the main fix in the commit log, not just the subject.
Sure, I'll do this. Just to make sure - for every iteration on the
commit message, I need to increment the patch "version" and resend the
whole patch, right?
>
> Al
On 07/05/2019 02:18 AM, Luke Nelson wrote:
> commit 66d0d5a854a6 ("riscv: bpf: eliminate zero extension code-gen")
> added the new zero-extension optimization for some BPF ALU operations.
>
> Since then, bugs in the JIT that have been fixed in the bpf tree require
> this optimization to be added t
Hello dear,
We are in the market for your products after meeting at your stand during last
expo.
Please kindly send us your latest catalog and price list so as to start a new
project/order as promised during the exhibition.
I would appreciate your response about the above details required
Hi Chris,
thanks for your patch!
On Thu, Jul 4, 2019 at 6:21 AM Chris Packham
wrote:
> desc->flags may already have values set by of_gpiochip_add() so make
> sure that this isn't undone when setting the initial direction.
>
> Fixes: 3edfb7bd76bd1cba ("gpiolib: Show correct direction from the be
On Wed, Jul 3, 2019 at 11:30 PM Chris Packham
wrote:
> The problem is caused by commit 3edfb7bd76bd1cba ("gpiolib: Show correct
> direction from the beginning"). I'll see if I can whip up a patch to fix it.
Oh. I think:
if (chip->get_direction && gpiochip_line_is_valid(chip, i))
On Fri, 5 Jul 2019 14:09:11 +0200, Maxime Chevallier wrote:
> Hello everyone,
>
> This series adds support for classification of the ETHER flow in the
> mvpp2 driver.
>
> The first patch allows detecting when a user specifies a flow_type that
> isn't supported by the driver, while the second add
Hi Linus,
Here's a set of minor changes for AFS for the next merge window:
(1) Remove an unnecessary check in afs_unlink().
(2) Add a tracepoint for tracking callback management.
(3) Add a tracepoint for afs_server object usage.
(4) Use struct_size().
(5) Add mappings for AFS UAE abort c
On Fri, Jul 5, 2019 at 12:35 PM wrote:
> For example, there is a button which drives level to be low when it is
> pushed, and drivers level to be high when it is released.
> We want to catch the event when the button is pushed.
>
> In user space we configure a line event with the following code:
On 07/05/2019 10:44 PM, Anton Protopopov wrote:
> Add a new API bpf_object__reuse_maps() which can be used to replace all maps
> in
> an object by maps pinned to a directory provided in the path argument.
> Namely,
> each map M in the object will be replaced by a map pinned to path/M.name.
>
>
On Thu, 4 Jul 2019, Thomas Gleixner wrote:
> apic->send_IPI_allbutself() takes a vector number as argument.
>
> APIC_DM_NMI is clearly not a vector number. It's defined to 0x400 which is
> outside the vector space.
>
> Use NMI_VECTOR instead as that's what it is intended to be.
>
> Fixes: 82da3
Hi Linus,
Here's my fourth block of keyrings changes for the next merge window. They
change the permissions model used by keys and keyrings to be based on an
internal ACL by the following means:
(1) Replace the permissions mask internally with an ACL that contains a
list of ACEs, each with
On 05/07/2019 17:35:46+0200, Frank Wunderlich wrote:
> Hi Alexander,
>
> thank you for the Review
>
> > Gesendet: Donnerstag, 04. Juli 2019 um 22:43 Uhr
> > Von: "Alexandre Belloni"
> > > - rtc->rtc_dev = devm_rtc_allocate_device(rtc->dev);
> > > - if (IS_ERR(rtc->rtc_dev))
> > > - retur
Cool !!
On 12:34 Fri 05 Jul , Steven Rostedt wrote:
Just after releasing 2.8, some bugs were found (isn't that always the
case?). Now we have 2.8.1 stable release:
http://trace-cmd.org
-- Steve
Short log here:
Greg Thelen (2):
trace-cmd: Always initialize write_record() len
trac
Here's my third block of keyrings changes for the next merge window.
These patches help make keys and keyrings more namespace aware. Firstly
some miscellaneous patches to make the process easier:
(1) Simplify key index_key handling so that the word-sized chunks
assoc_array requires don't h
On 05/07/2019 21:49, Paolo Bonzini wrote:
> On 05/07/19 22:25, Thomas Gleixner wrote:
>> In practice, this makes Linux vulnerable to CVE-2011-1898 / XSA-3, which
>> I'm disappointed to see wasn't shared with other software vendors at the
>> time.
> Oh, that brings back memories. At the time I was
Hi Linus,
Here's my second block of keyrings changes for the next merge window.
These are all request_key()-related, including a fix and some improvements:
(1) Fix the lack of a Link permission check on a key found by
request_key(), thereby enabling request_key() to link keys that don't
Hi Linus,
Here's my first block of keyrings changes for the next merge window. I've
divided up the set into four blocks, but they need to be applied in order
as they would otherwise conflict with each other.
These are some miscellaneous keyrings fixes and improvements:
(1) Fix a bunch of warni
On Fri, 5 Jul 2019, Thomas Gleixner wrote:
> On Fri, 5 Jul 2019, Mathieu Desnoyers wrote:
> > - On Jul 5, 2019, at 4:49 AM, Ingo Molnar mi...@kernel.org wrote:
> > > * Mathieu Desnoyers wrote:
> > >> The semantic I am looking for here is C11's relaxed atomics.
> > >
> > > What does this mean?
On Thu, 2019-06-06 at 17:07:55 UTC, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> The 1Gb Macronix chip can have a maximum of 20 bad blocks, while
> the 2Gb version has twice as many blocks and therefore the maximum
> number of bad blocks is 40.
>
> The 4Gb GigaDevice GD5F4GQ4xA has twice
On Sat, 2019-06-29 at 01:22:48 UTC, Paul Cercueil wrote:
> If MTD_NAND_JZ4780 is y and MTD_NAND_JZ4780_BCH is m,
> which select CONFIG_MTD_NAND_INGENIC_ECC to m, building fails:
>
> drivers/mtd/nand/raw/ingenic/ingenic_nand.o: In function
> `ingenic_nand_remove':
> ingenic_nand.c:(.text+0x177): u
On Fri, Jul 05, 2019 at 08:47:20PM +0200, Arnd Bergmann wrote:
From: Kees Cook
Commit dbbb08f500d6146398b794fdc68a8e811366b451 upstream.
Adjust vdso_{start|end} to be char arrays to avoid compile-time analysis
that flags "too large" memcmp() calls with CONFIG_FORTIFY_SOURCE.
Cc: Jisheng Zhang
On Fri, 5 Jul 2019, Mathieu Desnoyers wrote:
> - On Jul 5, 2019, at 4:49 AM, Ingo Molnar mi...@kernel.org wrote:
> > * Mathieu Desnoyers wrote:
> >> The semantic I am looking for here is C11's relaxed atomics.
> >
> > What does this mean?
>
> C11 states:
>
> "Atomic operations specifying me
On 05/07/19 22:25, Thomas Gleixner wrote:
> In practice, this makes Linux vulnerable to CVE-2011-1898 / XSA-3, which
> I'm disappointed to see wasn't shared with other software vendors at the
> time.
Oh, that brings back memories. At the time I was working on Xen, so I
remember that CVE. IIRC th
On 05/07/2019 20:19, Nadav Amit wrote:
>> On Jul 5, 2019, at 8:47 AM, Andrew Cooper wrote:
>>
>> On 04/07/2019 16:51, Thomas Gleixner wrote:
>>> 2) The loop termination logic is interesting at best.
>>>
>>> If the machine has no TSC or cpu_khz is not known yet it tries 1
>>> million times
On Fri, Jul 5, 2019 at 12:10 PM Matthew Wilcox wrote:
>
> On Thu, Jul 04, 2019 at 04:27:14PM -0700, Dan Williams wrote:
> > On Thu, Jul 4, 2019 at 12:14 PM Matthew Wilcox wrote:
> > >
> > > On Thu, Jul 04, 2019 at 06:54:50PM +0200, Jan Kara wrote:
> > > > On Wed 03-07-19 20:27:28, Matthew Wilcox
From: Markus Elfring
Date: Fri, 5 Jul 2019 22:37:58 +0200
Avoid an extra function call by using a ternary operator instead of
a conditional statement for a setting selection.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/rtc/rtc-zynqmp.c |
Add a new API bpf_object__reuse_maps() which can be used to replace all maps in
an object by maps pinned to a directory provided in the path argument. Namely,
each map M in the object will be replaced by a map pinned to path/M.name.
Signed-off-by: Anton Protopopov
---
tools/lib/bpf/libbpf.c |
Add a new pinned_maps_path member to the bpf_prog_load_attr structure and
extend the bpf_prog_load_xattr() function to pass this pointer to the new
bpf_object__reuse_maps() helper. This change provides users with a simple
way to use existing pinned maps when (re)loading BPF programs.
Signed-off-by
The following two patches add an option for users to reuse existing maps when
loading a program using the bpf_prog_load_xattr function. A user can specify a
directory containing pinned maps inside the bpf_prog_load_attr structure, and in
this case the bpf_prog_load_xattr function will replace (bpf
On Fri, Jul 5, 2019 at 1:36 PM Thomas Gleixner wrote:
>
> On Fri, 5 Jul 2019, Andy Lutomirski wrote:
> > On Fri, Jul 5, 2019 at 8:47 AM Andrew Cooper
> > wrote:
> > > Because TPR is 0, an incoming IPI can trigger #AC, #CP, #VC or #SX
> > > without an error code on the stack, which results in a c
On Fri, Jul 5, 2019 at 1:25 PM Thomas Gleixner wrote:
>
> Andrew,
>
> >
> > These can be addressed by setting TPR to 0x10, which will inhibit
>
> Right, that's easy and obvious.
>
This boots:
diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
index 177aa8ef2afa..5257c40bde6c
On Fri, 5 Jul 2019, Andy Lutomirski wrote:
> On Fri, Jul 5, 2019 at 8:47 AM Andrew Cooper
> wrote:
> > Because TPR is 0, an incoming IPI can trigger #AC, #CP, #VC or #SX
> > without an error code on the stack, which results in a corrupt pt_regs
> > in the exception handler, and a stack underflow
Linus,
The following changes since commit 6fbc7275c7a9ba97877050335f290341a1fd8dbf:
Linux 5.2-rc7 (2019-06-30 11:25:36 +0800)
are available in the git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to e644fa18e2ffc8895ca30dade503ae
Andrew,
On Fri, 5 Jul 2019, Andrew Cooper wrote:
> On 04/07/2019 16:51, Thomas Gleixner wrote:
> > 2) The loop termination logic is interesting at best.
> >
> > If the machine has no TSC or cpu_khz is not known yet it tries 1
> > million times to ack stale IRR/ISR bits. What?
> >
> >
On Mon 2019-07-01 17:26:02, Jean-Jacques Hiblot wrote:
> The driver parses the device-tree to identify which LED should be handled.
> Since the information about the device node is known at this time, we can
> provide the LED core with it. It may be useful later.
>
> Signed-off-by: Jean-Jacques Hi
On Thu 2019-07-04 16:57:42, Joe Perches wrote:
> Probable cut&paste typo - use the correct field size.
>
> Signed-off-by: Joe Perches
Ack.
Pavel
> ---
> drivers/leds/leds-as3645a.c | 2 +-
> 1 file changed, 1 insertion(+),
If CONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT is not set, the dummy version of
the function should be static.
Fixes: 1e2c3f0f1e93 ("ACPI: PM: Make acpi_sleep_state_supported() non-static")
Signed-off-by: Dexuan Cui
Reported-by: kbuild test robot
---
Sorry for not doing it right in the previous p
On 05/07/2019 20:06, Andy Lutomirski wrote:
> On Fri, Jul 5, 2019 at 8:47 AM Andrew Cooper
> wrote:
>> On 04/07/2019 16:51, Thomas Gleixner wrote:
>>> 2) The loop termination logic is interesting at best.
>>>
>>> If the machine has no TSC or cpu_khz is not known yet it tries 1
>>> mil
From: Markus Elfring
Date: Fri, 5 Jul 2019 22:10:10 +0200
Avoid an extra function call by using a ternary operator instead of
a conditional statement.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/rtc/rtc-stm32.c | 6 +-
1 file changed
On Fri, Jul 05, 2019 at 12:40:26AM +0530, Hariprasad Kelam wrote:
> Add IRQF_ONESHOT to ensure "Interrupt is not reenabled after the hardirq
> handler finished".
>
> fixes below issue reported by coccicheck
>
> sound/soc/codecs/wcd9335.c:4068:8-33: ERROR: Threaded IRQ with no
> primary handler re
Please re-state the main fix in the commit log, not just the subject.
Also, this does not explain why the current values are and the impact to
systems / users. This would help in determine and evaluating if this
deserves to be a stable fix.
On Fri, Jul 05, 2019 at 06:30:21PM +0200, Radoslaw Bur
On Fri, Jul 05, 2019 at 08:09:32AM -0700, Paul E. McKenney wrote:
> On Fri, Jul 05, 2019 at 08:24:50AM -0400, Joel Fernandes wrote:
> > On Fri, Jul 05, 2019 at 12:52:31PM +0900, Byungchul Park wrote:
> > > On Thu, Jul 04, 2019 at 10:40:44AM -0700, Paul E. McKenney wrote:
> > > > On Thu, Jul 04, 201
On Fri, 5 Jul 2019 02:40:28 +, Xue Chaojing wrote:
> This patch adds firmware version query in ethtool -i.
>
> Signed-off-by: Xue Chaojing
Reviewed-by: Jakub Kicinski
Buona giornata
Ho una proposta commerciale reciproca, che si riferisce al trasferimento di
una grande quantità di denaro su un conto all'estero, con il tuo aiuto come
partner straniero come beneficiario dei fondi. Tutto su questa transazione sarà
legale senza alcun ponte di autorità finanzia
On 7/5/19 1:15 PM, Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 5 Jul 2019 21:08:12 +0200
>
> Avoid an extra function call by using a ternary operator instead of
> a conditional statement.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfri
Hi Ivan,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Ivan-Khoronzhuk/xdp-allow-same-allocator-usage/20190706-003850
config: arm64-allmodconfig (attached as .config)
compiler: aarch64-linux-g
Linus,
I2C has a MAINTAINERS update which will be benfitial for developers, so
let's add it right away.
Please pull.
Thanks,
Wolfram
The following changes since commit 6fbc7275c7a9ba97877050335f290341a1fd8dbf:
Linux 5.2-rc7 (2019-06-30 11:25:36 +0800)
are available in the Git repositor
> On Jul 5, 2019, at 8:47 AM, Andrew Cooper wrote:
>
> On 04/07/2019 16:51, Thomas Gleixner wrote:
>> 2) The loop termination logic is interesting at best.
>>
>> If the machine has no TSC or cpu_khz is not known yet it tries 1
>> million times to ack stale IRR/ISR bits. What?
>>
>>
From: Markus Elfring
Date: Fri, 5 Jul 2019 21:08:12 +0200
Avoid an extra function call by using a ternary operator instead of
a conditional statement.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/nvme/host/core.c | 5 +
1 file changed
1 - 100 of 556 matches
Mail list logo
