bottom-up style is useless in x86_64 any longer, isolate it. Later, it may
be removed completely from x86.
Signed-off-by: Pingfan Liu
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Dave Hansen
Cc: Andy Lutomirski
Cc: Peter Zijlstra
Cc: "Rafael J. Wysocki"
Although kaslr-kernel can avoid to stain the movable node. [1] But the
pgtable can still stain the movable node. That is a probability problem,
although low, but exist. This patch tries to make it certainty by
allocating pgtable on unmovable node, instead of following kernel end.
There are two
This patch identifies the point where memblock alloc start. It has no
functional.
Signed-off-by: Pingfan Liu
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Dave Hansen
Cc: Andy Lutomirski
Cc: Peter Zijlstra
Cc: "Rafael J. Wysocki"
Cc: Len Brown
Cc:
During boot time, there is requirement to tell whether a series of func
call will consume memory or not. For some reason, a temporary memory
resource can be loan to those func through memblock allocator, but at a
check point, all of the loan memory should be turned back.
A typical using style:
Background
When kaslr kernel can be guaranteed to sit inside unmovable node
after [1]. But if kaslr kernel is located near the end of the movable node,
then bottom-up allocator may create pagetable which crosses the boundary
between unmovable node and movable node. It is a probability issue,
two
While debugging Skylake audio stuff, I came across a kernel oops
introduced by this commit.
It's quite late here and my brain is fried, submitting as is but my
money is on the use of link->platform->of_node which is quite unlikely
to work on ACPI platforms.
and btw you may want to fix the
From: Jacob Pan
VT-d Rev3.0 has made a few changes to the page request interface,
1. widened PRQ descriptor from 128 bits to 256 bits;
2. removed streaming response type;
3. introduced private data that requires page response even the
request is not last request in group (LPIG).
This is a
From: Praveen Kumar B
Add support for new version of pwm-kona.
Add support to make PWM changes configured and stable.
Signed-off-by: Praveen Kumar B
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
Signed-off-by: Sheetal Tigadoli
---
drivers/pwm/pwm-bcm-kona.c | 128
From: Praveen Kumar B
Add new compatible string for new version of pwm-kona
Signed-off-by: Praveen Kumar B
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
Signed-off-by: Sheetal Tigadoli
---
Documentation/devicetree/bindings/pwm/brcm,kona-pwm.txt | 2 +-
1 file changed, 1 insertion(+), 1
From: Praveen Kumar B
Change pwm compatible to new version of pwm-kona
Add new compatible to check pwm configure status
Signed-off-by: Praveen Kumar B
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
Signed-off-by: Sheetal Tigadoli
---
arch/arm/boot/dts/bcm-cygnus.dtsi | 2 +-
1 file
Hi,
This patchset contain support to make PWM changes configure
and stablize
Following are brief changes done
a. Add support for version2 compatible string
b. Change PWM config and stablize delay in PWM Kona
Praveen Kumar B (3):
dt-bindings: pwm: kona:
On Thu, Jan 10, 2019 at 07:24:13PM +0100, Greg Kroah-Hartman wrote:
> My tolerance for ZFS is pretty non-existant. Sun explicitly did not
> want their code to work on Linux, so why would we do extra work to get
> their code to work properly?
ZoL facilitates seamless r/w cross-mounting with
‐‐‐ Original Message ‐‐‐
On Thursday, January 10, 2019 11:52 PM, Qian Cai wrote:
> On 1/10/19 10:15 PM, Esme wrote:
>
> > > > [ 75.793150] RIP: 0010:rb_insert_color+0x189/0x1480
> > >
> > > What's in that line? Try,
> > > $ ./scripts/faddr2line vmlinux rb_insert_color+0x189/0x1480
> >
>
Linus Torvalds wrote on Thu, Jan 10, 2019:
> On Thu, Jan 10, 2019 at 4:25 AM Dominique Martinet
> wrote:
> > Linus Torvalds wrote on Thu, Jan 10, 2019:
> > > (Except, of course, if somebody actually notices outside of tests.
> > > Which may well happen and just force us to revert that commit. But
On 1/10/19 10:15 PM, Esme wrote:
>>> [ 75.793150] RIP: 0010:rb_insert_color+0x189/0x1480
>>
>> What's in that line? Try,
>>
>> $ ./scripts/faddr2line vmlinux rb_insert_color+0x189/0x1480
>
> rb_insert_color+0x189/0x1480:
> __rb_insert at /home/files/git/linux/lib/rbtree.c:131
> (inlined by)
Hi Tom,
On Wed, Jan 09, 2019 at 01:49:10PM -0600, Tom Zanussi wrote:
> From: Tom Zanussi
>
> Currently, the onmatch action data binds the onmatch action to data
> related to synthetic event generation. Since we want to allow the
> onmatch handler to potentially invoke a different action, and
On Thu, Jan 10, 2019 at 11:45 PM Cong Wang wrote:
>
> On Tue, Jan 8, 2019 at 1:30 AM Konstantin Khlebnikov
> wrote:
> > @@ -443,12 +444,14 @@ static struct neigh_hash_table
> > *neigh_hash_alloc(unsigned int shift)
> > ret = kmalloc(sizeof(*ret), GFP_ATOMIC);
> > if (!ret)
> >
On 1/10/19 4:26 PM, Vineet Gupta wrote:
> | > Also, set_mask_bits is used in fs quite a bit and we can possibly come up
> | > with a generic llsc based implementation (w/o the cmpxchg loop)
> |
> | May I also suggest changing the return value of set_mask_bits() to old.
> |
> | You can compute
On 1/10/19 4:26 PM, Vineet Gupta wrote:
> Cc: Alexander Viro
> Cc: Peter Zijlstra (Intel)
> Cc: linux-fsde...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Link: http://lkml.kernel.org/g/20150807115710.ga16...@redhat.com
> Acked-by: Oleg Nesterov
> Signed-off-by: Vineet Gupta
On 1/10/19 4:26 PM, Vineet Gupta wrote:
> It seems that 5f16f3225b0624 and 00a1a053ebe5, both with same commitlog
> ("ext4: atomically set inode->i_flags in ext4_set_inode_flags()")
> introduced the set_mask_bits API, but somehow missed not using it in
> ext4 in the end
>
> Also, set_mask_bits
On 2019/1/8 下午4:07, Zha Bin wrote:
The vsock core only supports 32bit CID, but the Virtio-vsock spec define
CID (dst_cid and src_cid) as u64 and the upper 32bits is reserved as
zero. This inconsistency causes one bug in vhost vsock driver. The
scenarios is:
0. A hash table
On 11/01/2019 14:08, Masahiro Yamada wrote:
> On Thu, Jan 10, 2019 at 2:44 PM Alexey Kardashevskiy wrote:
>>
>> c3ff2a519 "powerpc/32: add stack protector support" addes stack protector
>> support so now powerpc's "prepare" target depends on prepare0 (via
>> stack_protector_prepare target).
>>
> On Jan 10, 2019, at 8:04 PM, Dave Chinner wrote:
>
>> On Thu, Jan 10, 2019 at 06:18:16PM -0800, Linus Torvalds wrote:
>>> On Thu, Jan 10, 2019 at 6:03 PM Dave Chinner wrote:
>>>
On Thu, Jan 10, 2019 at 02:11:01PM -0800, Linus Torvalds wrote:
And we *can* do sane things about
On Thu, Jan 10, 2019 at 06:18:16PM -0800, Linus Torvalds wrote:
> On Thu, Jan 10, 2019 at 6:03 PM Dave Chinner wrote:
> >
> > On Thu, Jan 10, 2019 at 02:11:01PM -0800, Linus Torvalds wrote:
> > > And we *can* do sane things about RWF_NOWAIT. For example, we could
> > > start async IO on
Vhost dirty page logging API is designed to sync through GPA. But we
try to log GIOVA when device IOTLB is enabled. This is wrong and may
lead to missing data after migration.
To solve this issue, when logging with device IOTLB enabled, we will:
1) reuse the device IOTLB translation result of
On 2019/1/10 下午10:07, Michael S. Tsirkin wrote:
On Thu, Jan 10, 2019 at 08:37:17PM +0800, Jason Wang wrote:
On 2019/1/9 下午10:25, Michael S. Tsirkin wrote:
On Wed, Jan 09, 2019 at 03:29:47PM +0800, Jason Wang wrote:
Vhost dirty page logging API is designed to sync through GPA. But we
try to
Hi Shameer,
Patch looks OK to me, please feel free to add,
Reviewed-by: Ganapatrao Kulkarni
On Thu, Dec 13, 2018 at 5:25 PM Marc Zyngier wrote:
>
> On 13/12/2018 10:59, Shameer Kolothum wrote:
> > From: Shanker Donthineni
> >
> > The NUMA node information is visible to ITS driver but not
Hi all,
Commit
b19bce0335e2 ("net: ethernet: mediatek: fix warning in phy_start_aneg")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
pgpbjtPwb3cSd.pgp
Description: OpenPGP digital signature
On 10-01-19, 10:42, Matthias Kaehlcke wrote:
> Thanks for the pointer, there's always something new to learn!
>
> Ok, so the policy CPU and hence the CPU registered as cooling
> device may vary. I understand that this requires to list all possible
> cooling devices,
I won't say that I changed DT
Hi all,
Changes since 20190110:
New tree: cpufreq-arm
The vfs tree still had its build failure for which I applied a patch.
The drm-misc tree gained a conflict against Linus' tree.
The akpm-current tree gained conflicts against Linus' and the security
trees.
Non-merge commits (relative
As reported by Aravind:
I built f2fs tools from source (at tag v1.12.0) and was able to get this
backtrace in gdb:
Program received signal SIGSEGV, Segmentation fault.
0x77f8eb54 in f2fs_set_bit (nr=1041170432,
addr=0x7f621010 ) at libf2fs.c:312
312mask = 1 << (7 - (nr &
On 1/8/19 4:46 PM, Cao jin wrote:
> One more question: in compressed/, for mem*(), it seems we both use the
> macros of boot/string.h, and the functions of compressed/string.c. Is
> that what we want?
>
> compressed/ is compiled with -O2, so it cannot be told by objdump -d,
> but still can be
For dax pmd, pmd_trans_huge() returns false but pmd_huge() returns
true on x86. So the function works as long as hugetlb is configured.
However, dax doesn't depend on hugetlb.
Signed-off-by: Yu Zhao
---
mm/gup.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/mm/gup.c
On 2019-01-10 20:12, Paul Moore wrote:
> On Thu, Jan 10, 2019 at 5:59 PM Richard Guy Briggs wrote:
> > On 2019-01-03 15:11, Paul Moore wrote:
> > > On Wed, Oct 31, 2018 at 5:17 PM Richard Guy Briggs
> > > wrote:
> > > > On 2018-10-19 19:17, Paul Moore wrote:
> > > > > On Sun, Aug 5, 2018 at
On Thu, Jan 10, 2019 at 10:44:08PM +0300, Dan Carpenter wrote:
> On Thu, Jan 10, 2019 at 05:00:24PM +, Sidong Yang wrote:
> > I think you just point out that my code isn't obvious because the
> > function returns negative error codes. I agree with you. But what if
> > change my code like
Bus Clear feature of tegra i2c controller helps to recover from
bus hang when i2c master loses the bus arbitration due to the
slave device holding SDA LOW continuously for some unknown reasons.
Signed-off-by: Sowjanya Komatineni
---
drivers/i2c/busses/i2c-tegra.c | 66
On 10-01-19, 12:00, Matthias Kaehlcke wrote:
> Viresh helped me understand that we currently need to add cooling
> device entries for all CPUs to the DT, even though at most one will be
> active per freq domain at any time (I wonder if this could be changed
> though).
Actually we were only adding
On 2019/1/10 下午9:44, Joerg Roedel wrote:
Hi,
there is a problem with virtio-blk driven devices when
virtio-ring uses SWIOTLB through the DMA-API. This happens
for example in AMD-SEV enabled guests, where the guest RAM
is mostly encrypted and all emulated DMA has to happen
to/from the SWIOTLB
The same path -Iarch/$(ARCH) is passed to KBUILD_CPPFLAGS,
KBUILD_AFLAGS, and KBUILD_CFLAGS.
As you see in scripts/Makefile.lib, KBUILD_CPPFLAGS is passed
to c_flags and a_flags as well.
Passing it to KBUILD_CPPFLAGS is enough.
Signed-off-by: Masahiro Yamada
---
arch/powerpc/Makefile | 4
The header search path -I. in kernel Makefiles is very suspicious;
it allows the compiler to search for headers in the top of $(srctree),
where obviously no header file exists.
-Iinclude/math-emu seems unnecessary because all files include headers
in the form of #include .
I was able to build
I am trying to get rid of crappy magic from Kbuild core makefiles.
Before that, I want to drop as many useless paths as possible.
Actually, many Makefiles are adding around pointless options.
This series cleans some powerpc Makefiles.
(only compile-tested by 0day bot)
Masahiro Yamada (3):
The header search path -I. in kernel Makefiles is very suspicious;
it allows the compiler to search for headers in the top of $(srctree),
where obviously no header file exists.
Commit 46f43c6ee022 ("KVM: powerpc: convert marker probes to event
trace") first added these options, but they are
Hi, Daniel:
On Thu, 2019-01-10 at 21:02 +0100, Daniel Vetter wrote:
> On Thu, Jan 10, 2019 at 08:01:37PM +0100, Frank Wunderlich wrote:
> > Hi Daniel,
> >
> > > > Would be good to use the new generic fbdev emulation code here, for even
> > > > less code. Or at least know why this isn't possible
> Yes, the "GPL condom" attempt doesn't work at all. It's been shot down
> a long time ago in the courts.
SFLC maintains there is no kernel licensing issue[1].
As a side note, even Hellwig's suit against VMware was dismissed (he may
appeal)[2].
Debian and Canonical base their decision to ship
> On Thu, Jan 10, 2019 at 07:07:52PM +0100, Sebastian Andrzej Siewior wrote:
> > On 2019-01-10 17:32:58 [+], Hutter, Tony wrote:
> > > > But since when did out-of-tree modules use __kernel_fpu_begin?
It's an
> > > > x86-only thing, and shouldn't really be used by anyone, right?
> > >
> > >
On Fri, Dec 14, 2018 at 08:23:25AM +, Anson Huang wrote:
> This patch adds cpuidle support for i.MX7ULP, 3 cpuidle
> states supported as below:
>
> 1. WFI, just ARM wfi;
> 2. WAIT mode, mapped to SoC's partial stop mode #3;
> 3. STOP mode, mapped to SoC's partial stop mode #1.
>
> In WAIT
> > [ 75.793150] RIP: 0010:rb_insert_color+0x189/0x1480
>
> What's in that line? Try,
>
> $ ./scripts/faddr2line vmlinux rb_insert_color+0x189/0x1480
rb_insert_color+0x189/0x1480:
__rb_insert at /home/files/git/linux/lib/rbtree.c:131
(inlined by) rb_insert_color at
On Tue 08 Jan 03:18 PST 2019, Vivek Gautam wrote:
>
> On 1/8/2019 12:29 PM, Bjorn Andersson wrote:
> > On Thu 11 Oct 02:49 PDT 2018, Vivek Gautam wrote:
> >
> > > Add device node for arm,mmu-500 available on sdm845.
> > > This MMU-500 with single TCU and multiple TBU architecture
> > > is
On Tue, Jan 8, 2019 at 10:34 PM Michal Hocko wrote:
>
> On Thu 20-12-18 10:19:34, Michal Hocko wrote:
> > On Thu 20-12-18 15:19:39, Pingfan Liu wrote:
> > > Hi Michal,
> > >
> > > WIth this patch applied on the old one, I got the following message.
> > > Please get it from attachment.
> > [...]
>
Add CQE Support for Tegra186 and Tegra194 SDMMC4 controller
Signed-off-by: Sowjanya Komatineni
---
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 1 +
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra186.dtsi
On Thu, Jan 10, 2019 at 2:44 PM Alexey Kardashevskiy wrote:
>
> c3ff2a519 "powerpc/32: add stack protector support" addes stack protector
> support so now powerpc's "prepare" target depends on prepare0 (via
> stack_protector_prepare target).
>
> It works fine until we try build an external module
Add supports-cqe optional property for Tegra SDMMC.
Tegra186 and Tegra194 supports HW Command queue only
on SDMMC4 controller. This property is used to identify
command queue support controller in the tegra sdhci driver.
Signed-off-by: Sowjanya Komatineni
---
This patch adds HW Command Queue for supported Tegra SDMMC
controllers.
Signed-off-by: Sowjanya Komatineni
---
drivers/mmc/host/Kconfig | 1 +
drivers/mmc/host/sdhci-tegra.c | 117 +++--
drivers/mmc/host/sdhci.c | 9 +++-
Hi Todd,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.0-rc1 next-20190110]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
There still is a race window after the commit b027e2298bd588
("tty: fix data race between tty_init_dev and flush of buf"),
if receive_buf call comes before tty initialization completes
in n_tty_open and tty->driver_data may be NULL.
CPU0CPU1
On 1/3/19 6:44 AM, Jerome Glisse wrote:
> On Thu, Jan 03, 2019 at 10:26:54AM +0100, Jan Kara wrote:
>> On Wed 02-01-19 20:55:33, Jerome Glisse wrote:
>>> On Wed, Dec 19, 2018 at 12:08:56PM +0100, Jan Kara wrote:
On Tue 18-12-18 21:07:24, Jerome Glisse wrote:
> On Tue, Dec 18, 2018 at
The modalias is set by the MODULE_DEVICE_TABLE, thus remove redundant
MODULE_ALIAS.
Signed-off-by: Axel Lin
---
drivers/regulator/max14577-regulator.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/regulator/max14577-regulator.c
b/drivers/regulator/max14577-regulator.c
index
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
security/selinux/ss/services.c
between commit:
3d252529480c ("SELinux: Remove unused selinux_is_enabled")
from the security tree and commit:
dd4c293d6d4d ("selinux: convert to kvmalloc")
from the akpm-current
On Fri, Dec 14, 2018 at 08:20:22AM +, Anson Huang wrote:
> i.MX7ULP SoC revision info is inside the SIM mode's JTAG_ID
> register, add sim node to support SoC revision check.
>
> Signed-off-by: Anson Huang
> ---
> arch/arm/boot/dts/imx7ulp.dtsi | 13 +
> 1 file changed, 13
I accidentally dropped '*' in the previous renaming patch.
Revive it so that 'make mrproper' can clean the generated files.
Fixes: d86271af6460 ("kconfig: rename generated .*conf-cfg to *conf-cfg")
Signed-off-by: Masahiro Yamada
---
scripts/kconfig/Makefile | 2 +-
1 file changed, 1
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
mm/rmap.c
between commit:
ba422731316d ("mm/mmu_notifier: mm/rmap.c: Fix a mmu_notifier range bug in
try_to_unmap_one")
from Linus' tree and commit:
f955d5dda846 ("mm/mmu_notifier: contextual information for
On Thu, Jan 10, 2019 at 7:04 PM Martin K. Petersen
wrote:
> James,
>
> > Q1 - I'm hoping you can clarify how this should be interpreted.
> >
> > I originally took this to mean the number of bytes into the first
> > discard_granularity block that the partition resides at. i.e. If
> >
On Thu, Jan 10, 2019 at 01:43:01PM -0600, Li Yang wrote:
> On Sat, Dec 22, 2018 at 2:02 AM Nicholas Mc Guire wrote:
> >
> > On Fri, Dec 21, 2018 at 08:29:56PM -0600, Scott Wood wrote:
> > > On Fri, 2018-12-07 at 09:22 +0100, Nicholas Mc Guire wrote:
> > > > devm_kstrdup() may return NULL if
__setup() functions were removed in:
commit 4f81cbafcce2 ("x86/fpu: Fix early FPU command-line parsing")
caused that FPU parameter is passed as an argument to init, the dummy
__setup() functions can avoid this.
Signed-off-by: Haoyu Tang
---
arch/x86/kernel/fpu/init.c | 36
On Wed, Jan 9, 2019 at 10:25 PM Baoquan He wrote:
>
> On 01/08/19 at 05:48pm, Mike Rapoport wrote:
> > On Tue, Jan 08, 2019 at 05:01:38PM +0800, Baoquan He wrote:
> > > Hi Mike,
> > >
> > > On 01/08/19 at 10:05am, Mike Rapoport wrote:
> > > > I'm not thrilled by duplicating this code (yet again).
Hi Eduardo,
Do you have any more comments, will you take this serial?
Thanks.
Wei.
On 3/1/2019 6:12 PM, Wei Ni wrote:
> This series fixed some issues for Tegra soctherm,
> and add get_trend().
>
> Main changes from v6:
> 1. Per Eduardo's comment, we can remove the change:
> "thermal: tegra:
This argument was removed in 5f0ed774ed29.
Signed-off-by: Marcos Paulo de Souza
---
block/blk-core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/block/blk-core.c b/block/blk-core.c
index c78042975737..eba494f528cb 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -661,7 +661,6 @@
On Thu, Jan 10, 2019 at 3:57 PM Mike Rapoport wrote:
>
> Hi Pingfan,
>
> On Wed, Jan 09, 2019 at 09:02:41PM +0800, Pingfan Liu wrote:
> > On Tue, Jan 8, 2019 at 11:49 PM Mike Rapoport wrote:
> > >
> > > On Tue, Jan 08, 2019 at 05:01:38PM +0800, Baoquan He wrote:
> > > > Hi Mike,
> > > >
> > > >
The driver may sleep in an interrupt handler.
The function call path (from bottom to top) in the directory
"drivers/net/ethernet/huawei/hinic/" in Linux-4.17 is:
[FUNC] down
hinic_hw_mgmt.c, 324: down in msg_to_mgmt_async
hinic_hw_mgmt.c, 408: msg_to_mgmt_async in mgmt_recv_msg_handler
The driver may sleep while holding a RCU lock.
The function call path (from bottom to top) in Linux-4.17 is:
[FUNC] down
drivers/net/.../hinic/hinic_main.c, 775: down in hinic_get_stats64
net/core/dev.c, 8278: [FUNC_PTR]hinic_get_stats64 in dev_get_stats
net/core/net-sysfs.c, 568: dev_get_stats
On Thu, Jan 10, 2019 at 6:03 PM Dave Chinner wrote:
>
> On Thu, Jan 10, 2019 at 02:11:01PM -0800, Linus Torvalds wrote:
> > And we *can* do sane things about RWF_NOWAIT. For example, we could
> > start async IO on RWF_NOWAIT, and suddenly it would go from "probe the
> > page cache" to "probe and
ping?
On Sat, Dec 22, 2018 at 08:08:45AM -0200, Marcos Paulo de Souza wrote:
> bio_alloc_bioset return a bio pointer or NULL, so we can avoid storing
> the returned data into a new variable.
>
> Signed-off-by: Marcos Paulo de Souza
> ---
> drivers/md/md.c | 7 +--
> 1 file changed, 1
ping?
On Sat, Dec 22, 2018 at 08:03:54AM -0200, Marcos Paulo de Souza wrote:
> Instead of just using plain '1', as it improves readability.
>
> Signed-off-by: Marcos Paulo de Souza
> ---
> include/linux/blk_types.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On Fri, Jan 11, 2019 at 3:11 AM Paul Burton wrote:
>
> Hi Masahiro,
>
> On Thu, Jan 10, 2019 at 11:00:49AM +0900, Masahiro Yamada wrote:
> > On Thu, Jan 10, 2019 at 8:16 AM Paul Burton wrote:
> > > When building using GCC 4.7 or older, -ffunction-sections & the -pg flag
> > > used by ftrace are
On Thu, Jan 10, 2019, 6:21 PM NeilBrown
> On Thu, Jan 10 2019, thirtythreefo...@gmail.com wrote:
>
> > From: George Hilliard
> >
> > This is in preparation to allow it and the mt7621-dma drivers to be
> > built separately. They are completely independent pieces of software,
> > and the Kconfig
The driver may sleep while holding a RCU lock.
The function call path (from bottom to top) in Linux-4.17 is:
[FUNC] down
drivers/net/.../hinic/hinic_main.c, 775: down in hinic_get_stats64
net/core/dev.c, 8278: [FUNC_PTR]hinic_get_stats64 in dev_get_stats
net/core/net-sysfs.c, 568: dev_get_stats
Hi Linus,
Not a huge amount for rc2, assume the usual quiet period, and rc3 will
be most of it.
amdgpu:
- Powerplay fixes
- Virtual display pinning fixes
- Golden register updates for Vega
- Pitch and gem size validation fixes
- SR-IOV init error fix
- Pagetables in system RAM disable for some
Hello,
Sorry for being so late.
On Thu, Dec 27, 2018 at 05:35:17PM -0800, Florian Fainelli wrote:
> Le 12/27/18 à 2:55 AM, Namhyung Kim a écrit :
> > Hello,
> >
> > On Thu, Dec 20, 2018 at 07:43:35PM -0800, Florian Fainelli wrote:
> >> Hi all,
> >>
> >> I just painfully learned that perf would
Next step: 891dcc1072f1fa27a83da920d88daff6ca08fc02 (powerpc/dma: remove
dma_nommu_dma_supported)
git clone git://git.infradead.org/users/hch/misc.git -b powerpc-dma.6 a
git checkout 891dcc1072f1fa27a83da920d88daff6ca08fc02
Output:
Note: checking out
On Thu, 10 Jan 2019, Vlastimil Babka wrote:
>
> For the record, anyone backporting this to older kernels should make
> sure to also include 605ca5ede764 ("mm/huge_memory.c: reorder operations
> in __split_huge_page_tail()") or they are in for a lot of fun, like me.
Thanks a lot for alerting us
On Thu, Jan 10, 2019 at 02:11:01PM -0800, Linus Torvalds wrote:
> And we *can* do sane things about RWF_NOWAIT. For example, we could
> start async IO on RWF_NOWAIT, and suddenly it would go from "probe the
> page cache" to "probe and fill", and be much harder to use as an
> attack vector..
We
On Fri, 11 Jan 2019 12:13:35 +1100
Alexey Kardashevskiy wrote:
> > The words in TRACE_INCLUDE_PATH can be updated by C preprocessor defines.
> > For
> > example, if for some reason you had:
> >
> > #define pci special_pci
> >
> > The above would turn into:
> >
> >
On 1/11/19 9:46 AM, He Zhe wrote:
>
> On 1/11/19 1:27 AM, Konrad Rzeszutek Wilk wrote:
>> Let's skip it. There was another patch that would allocate a default 4MB
>> size if it there was an misue of swiotlb parameters.
> But this patch mainly fixes a crash. Could you please point me to the
On Wed, Jan 09, 2019 at 09:26:41PM -0800, Andy Lutomirski wrote:
> Since direct IO has been brought up, I have a question. I've wondered
> for years why direct IO works the way it does. If I were implementing
> it from scratch, my first inclination would be to use the page cache
> instead of
> On Jan 10, 2019, at 4:56 PM, Andy Lutomirski wrote:
>
> On Thu, Jan 10, 2019 at 3:02 PM Linus Torvalds
> wrote:
>> On Thu, Jan 10, 2019 at 12:52 PM Josh Poimboeuf wrote:
>>> Right, emulating a call instruction from the #BP handler is ugly,
>>> because you have to somehow grow the stack to
On 1/11/19 1:27 AM, Konrad Rzeszutek Wilk wrote:
> Let's skip it. There was another patch that would allocate a default 4MB size
> if it there was an misue of swiotlb parameters.
But this patch mainly fixes a crash. Could you please point me to the patch you
mentioned?
Thanks,
Zhe
>
>
>
>
On Fri, 11 Jan 2019 12:13:35 +1100
Alexey Kardashevskiy wrote:
> On 11/01/2019 01:47, Steven Rostedt wrote:
> > On Tue, Jan 08, 2019 at 12:08:03PM +0900, Masahiro Yamada wrote:
> >> ---
> >>
> >> drivers/vfio/pci/trace.h | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >>
On Thu, Jan 10, 2019 at 08:22:12PM +0530, Balakrishna Godavarthi wrote:
> Hi Johan,
>
> On 2019-01-10 20:09, Johan Hovold wrote:
> > On Thu, Jan 10, 2019 at 08:04:12PM +0530, Balakrishna Godavarthi wrote:
> > > Hi Johan,
> > >
> > > On 2019-01-09 20:22, Johan Hovold wrote:
> > > > On Thu, Dec
On Thu, Jan 10, 2019 at 04:59:55PM -0800, h...@zytor.com wrote:
> On January 10, 2019 9:42:57 AM PST, Sean Christopherson
> wrote:
> >On Thu, Jan 10, 2019 at 12:32:43PM -0500, Steven Rostedt wrote:
> >> On Thu, 10 Jan 2019 11:20:04 -0600
> >> Josh Poimboeuf wrote:
> >>
> >>
> >> > > While I
On Thu, Jan 10, 2019 at 04:30:06PM -0800, Andy Lutomirski wrote:
> On Thu, Jan 10, 2019 at 3:54 PM Sean Christopherson
> wrote:
> >
> > Sort of. A guest that is running under KVM (i.e. VMX) is much more
> > contained than a random userspace program. A rogue enclave in a VMX
> > guest can attack
Hi, Frank:
On Thu, 2019-01-10 at 20:01 +0100, Frank Wunderlich wrote:
> Hi Daniel,
>
> > > Would be good to use the new generic fbdev emulation code here, for even
> > > less code. Or at least know why this isn't possible to use for mtk (and
> > > maybe address that in the core code).
On 1/10/19 5:58 PM, Esme wrote:
> The console debug/stacks/info from just now. The previous config, current
> kernel from github.
> --
> Esme
>
> [ 75.783231] kasan: CONFIG_KASAN_INLINE enabled
> [ 75.785870] kasan: GPF could be caused by NULL-ptr deref or user memory
> access
> [
Hi Jirka,
On Thu, Jan 10, 2019 at 11:12:55AM +0100, Jiri Olsa wrote:
> hi,
> this patchset adds reader object to interface event
> processing for any data. It's defined as:
>
> struct reader {
> int fd;
> u64 data_size;
> u64 data_offset;
> };
>
> Now we can simply
On Thu, Jan 10, 2019 at 10:27:47PM +0100, Borislav Petkov wrote:
>On Mon, Jan 07, 2019 at 11:22:41AM +0800, Chao Fan wrote:
>> Memory information in SRAT table is necessary to fix the conflict
>> between KASLR and memory-hotremove. So RSDP and SRAT should be parsed.
>>
>> When booting form
Loys Ollivier writes:
> Commit 89a5e15bcba8 ("gpio/mmc/of: Respect polarity in the device tree")
> changed the behavior of "cd-inverted" to follow the device tree bindings
> specification.
> Lines specifying "cd-inverted" are now "active high".
>
> Fix the SD card for meson by setting the
On Wed, Jan 9, 2019 at 11:11 AM Stephen Smalley wrote:
> On Wed, 2019-01-09 at 07:41 -0800, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:a88cc8da0279 Merge branch 'akpm' (patches from
> > Andrew)
> > git tree: upstream
> > console output:
> >
On Thu, Jan 10, 2019 at 10:15:23PM +0100, Borislav Petkov wrote:
>On Mon, Jan 07, 2019 at 11:22:40AM +0800, Chao Fan wrote:
>> Memory information in SRAT is necessary to fix the conflict between
>> KASLR and memory-hotremove. So RSDP and SRAT should be parsed.
>>
>> When booting form
On Thu, Jan 10 2019, thirtythreefo...@gmail.com wrote:
> From: George Hilliard
>
> This is in preparation to allow it and the mt7621-dma drivers to be
> built separately. They are completely independent pieces of software,
> and the Kconfig specifies very different requirements.
>
> Cc:
On Thu, Jan 10, 2019 at 06:01:03PM +0100, Borislav Petkov wrote:
>On Mon, Jan 07, 2019 at 11:22:39AM +0800, Chao Fan wrote:
>> KASLR may randomly choose some positions which are located in movable
>> memory regions. This will make the movable memory chosen by KASLR
>> can't be removed.
>>
>>
On Thu, 2019-01-10 at 18:33 +0800, Long Cheng wrote:
fix spell error
> On Fri, 2019-01-04 at 22:49 +0530, Vinod Koul wrote:
> > On 02-01-19, 10:12, Long Cheng wrote:
> > > In DMA engine framework, add 8250 uart dma to support MediaTek uart.
> > > If MediaTek uart enabled(SERIAL_8250_MT6577), and
101 - 200 of 1151 matches
Mail list logo
