From: Andrea Arcangeli
Accurate userfaultfd WP tracking is possible by tracking exactly which
virtual memory ranges were writeprotected by userland. We can't relay
only on the RW bit of the mapped pagetable because that information is
destroyed by fork() or KSM or swap. If we were to relay on
The idea comes from the upstream discussion between Linus and Andrea:
https://lkml.org/lkml/2017/10/30/560
A summary to the issue: there was a special path in handle_userfault()
in the past that we'll return a VM_FAULT_NOPAGE when we detected
non-fatal signals when waiting for userfault
This is the gup counterpart of the change that allows the VM_FAULT_RETRY
to happen for more than once.
Reviewed-by: Jerome Glisse
Signed-off-by: Peter Xu
---
mm/gup.c | 17 +
mm/hugetlb.c | 6 --
2 files changed, 17 insertions(+), 6 deletions(-)
diff --git a/mm/gup.c
The idea comes from a discussion between Linus and Andrea [1].
Before this patch we only allow a page fault to retry once. We
achieved this by clearing the FAULT_FLAG_ALLOW_RETRY flag when doing
handle_mm_fault() the second time. This was majorly used to avoid
unexpected starvation of the
The idea comes from the upstream discussion between Linus and Andrea:
https://lkml.org/lkml/2017/10/30/560
A summary to the issue: there was a special path in handle_userfault()
in the past that we'll return a VM_FAULT_NOPAGE when we detected
non-fatal signals when waiting for userfault
There's plenty of places around __get_user_pages() that has a parameter
"nonblocking" which does not really mean that "it won't block" (because
it can really block) but instead it shows whether the mmap_sem is
released by up_read() during the page fault handling mostly when
VM_FAULT_RETRY is
syzbot has found a reproducer for the following crash on:
HEAD commit:9939f56e usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=135e29faa0
kernel config:
This series implements initial write protection support for
userfaultfd. Currently both shmem and hugetlbfs are not supported
yet, but only anonymous memory. This is the 4nd version of it.
The latest code can also be found at:
https://github.com/xzpeter/linux/tree/uffd-wp-merged
v5
Hi Christophe,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on powerpc/next]
[also build test ERROR on v5.2-rc5 next-20190619]
[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
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/infiniband/hw/nes/nes.c
between commit:
2d3c72ed5041 ("rdma: Remove nes")
from the rdma tree and commit:
2638eb8b50cf ("net: ipv4: provide __rcu annotation for ifa_list")
from the net-next tree.
I fixed
Hi all,
Today's linux-next merge of the rdma tree got conflicts in:
drivers/infiniband/hw/nes/Kconfig
drivers/infiniband/hw/nes/Makefile
between commit:
ec8f24b7faaf ("treewide: Add SPDX license identifier - Makefile/Kconfig")
from Linus' tree and commit:
2d3c72ed5041 ("rdma: Remove
Hi all,
Today's linux-next merge of the rdma tree got a conflict in:
include/rdma/ib_verbs.h
between commit:
dc1435c00fcd ("RDMA/srp: Rename SRP sysfs name after IB device rename
trigger")
from Linus' tree and commit:
0e2d00eb6fd4 ("RDMA: Add NLDEV_GET_CHARDEV to allow char dev
When loading a module with rodata=n, it causes an executing
NX-protected page BUG.
[ 32.379191] kernel tried to execute NX-protected page - exploit attempt?
(uid: 0)
[ 32.382917] BUG: unable to handle page fault for address: c0005000
[ 32.385947] #PF: supervisor instruction fetch
Hi Pavel,
On 2019/6/19 20:32, Pavel Machek wrote:
> Hi!
>
>> When we traverse xattr entries via __find_xattr(),
>> if the raw filesystem content is faked or any hardware failure occurs,
>> out-of-bound error can be detected by KASAN.
>> Fix the issue by introducing boundary check.
>
> Ok, so
FYI, we noticed the following commit (built with gcc-7):
commit: 286b15db78dc9741a47d082016dfc5fbcc31bd46 ("x86/hpet: Use channel for
legacy clockevent storage")
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git WIP.x86/hpet
in testcase: locktorture
with following parameters:
On 19/06/2019 17:28, Christoph Hellwig wrote:
> On Wed, Jun 19, 2019 at 10:34:54AM +1000, Alexey Kardashevskiy wrote:
>>
>>
>> On 23/05/2019 17:49, Christoph Hellwig wrote:
>>> None of these routines were ever used since they were added to the
>>> kernel.
>>
>>
>> It is still being used exactly
Today, if an application needs to wait for a very short duration
they have to have spinloops. Spinloops consume more power and continue
to use execution resources that could hurt its thread siblings in a core
with hyperthreads. New instructions umonitor, umwait and tpause allow
a low power
umwait or tpause allows processor to enter a light-weight
power/performance optimized state (C0.1 state) or an improved
power/performance optimized state (C0.2 state) for a period
specified by the instruction or until the system time limit or until
a store to the monitored address range in umwait.
IA32_UMWAIT_CONTROL[31:2] determines the maximum time in TSC-quanta
that processor can stay in C0.1 or C0.2. A zero value means no maximum
time.
Each instruction sets its own deadline in the instruction's implicit
input EDX:EAX value. The instruction wakes up if the time-stamp counter
reaches or
Since two new sysfs interface files are created for umwait control, add
an ABI document entry for the files:
/sys/devices/system/cpu/umwait_control/enable_c02
/sys/devices/system/cpu/umwait_control/max_time
Signed-off-by: Fenghua Yu
Reviewed-by: Ashok Raj
---
C0.2 state in umwait and tpause instructions can be enabled or disabled
on a processor through IA32_UMWAIT_CONTROL MSR register.
By default, C0.2 is enabled and the user wait instructions result in
lower power consumption with slower wakeup time.
But in real time systems which require faster
umonitor, umwait, and tpause are a set of user wait instructions.
umonitor arms address monitoring hardware using an address. The
address range is determined by using CPUID.0x5. A store to
an address within the specified address range triggers the
monitoring hardware to wake up the processor
1cd51b5d200d ("vgaswitcheroo: call fbcon_remap_all directly")
I have used the version of the fbdev tree from next-20190619 for today.
--
Cheers,
Stephen Rothwell
pgp34YO4wdmFl.pgp
Description: OpenPGP digital signature
On 6/13/19 3:45 PM, Thomas Gleixner wrote:
I noticed that Thomas' mailbox is filtering my mail because of some RBL and
have not figured out why that is yet so maybe he has not gotten any e-mails
from me. However, I already tried conacting using a different mail provider.
I got your mail from
Hi Colin,
On Wed, Jun 19, 2019 at 8:55 AM Colin Ian King wrote:
>
> On 19/06/2019 06:13, Martin Blumenstingl wrote:
> > Hi Colin,
> >
> >> Currently the call to device_property_read_u32_array is not error checked
> >> leading to potential garbage values in the delays array that are then used
>
Hi,
On Wed, Fri, 18 Mar 2016 Heiko Stuebner wrote:
>
> The panels need a bit of time to actually turn on. If this isn't
> observed, this results in problems when trying talk to the panels
> and thus produces detection errors. 100ms seem to be a safe value
> for the time being.
>
> Signed-off-by:
On Wed, 2019-06-19 at 12:47 -0600, Subash Abhinov Kasiviswanathan
wrote:
> > > There is a n:1 relationship between rmnet and IPA.
> > > rmnet does the de-muxing to multiple netdevs based on the mux id
> > > in the MAP header for RX packets and vice versa.
> >
> > Oh, so you mean that even though
Hi all,
Today's linux-next merge of the jc_docs tree got a conflict in:
Documentation/fb/fbcon.rst
between commit:
fce677d7e8f0 ("docs: fb: Add TER16x32 to the available font names")
from the char-misc.current tree and commit:
ab42b818954c ("docs: fb: convert docs to ReST and rename to
bpf/btf write_* functions need ff->ph->env.
With this missing, pipe-mode (perf record -o -) would crash like:
Program terminated with signal SIGSEGV, Segmentation fault.
This patch assign proper ph value to ff.
Cc: sta...@vger.kernel.org #v5.1+
Fixes: 606f972b1361 ("perf bpf: Save
In case of the last page containing bitflips (ret > 0),
spinand_mtd_read() will return that number of bitflips for the last
page. But to me it looks like it should instead return max_bitflips like
it does when the last page read returns with 0.
Signed-off-by: liaoweixiong
---
Hi Mathieu,
On Wed, Jun 19, 2019 at 11:49:44AM -0600, Mathieu Poirier wrote:
[...]
> > diff --git a/tools/perf/Makefile.config b/tools/perf/Makefile.config
> > index 51dd00f65709..4776c2c1fb6d 100644
> > --- a/tools/perf/Makefile.config
> > +++ b/tools/perf/Makefile.config
> > @@ -418,6 +418,30
Arm and arm64 architecture reserve some memory regions prior to the
symbol '_stext' and these memory regions later will be used by device
module and BPF jit. The current code misses to consider these memory
regions thus any address in the regions will be taken as user space
mode, but perf cannot
On Thu, 20 Jun 2019 at 05:04, Marcelo Tosatti wrote:
>
> Hi Li,
>
> On Wed, Jun 19, 2019 at 08:36:06AM +0800, Wanpeng Li wrote:
> > On Tue, 18 Jun 2019 at 21:36, Marcelo Tosatti wrote:
> > >
> > > On Mon, Jun 17, 2019 at 07:24:44PM +0800, Wanpeng Li wrote:
> > > > From: Wanpeng Li
> > > >
> > >
hi Boris Brezillon,
Sure, i will adjust the commit message and send again right now.
On 2019/6/20 AM12:18, Boris Brezillon wrote:
> On Wed, 19 Jun 2019 14:02:14 +
> Schrempf Frieder wrote:
>
>> On 19.06.19 15:46, Boris Brezillon wrote:
>>> Hi liaoweixiong,
>>>
>>> On Wed, 19 Jun 2019
Generated via:
$ ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- make defconfig
$ ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- make menuconfig
$ ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- make savedefconfig
$ mv defconfig arch/arm64/configs/defconfig
Removes explicit enablement of:
Add keyword support so that our mailing list gets cc'ed for clang/llvm
patches. We're pretty active on our mailing list so far as code review.
There are numerous Googlers like myself that are paid to support
building the Linux kernel with Clang and LLVM.
Signed-off-by: Nick Desaulniers
---
On Wed, Jun 19, 2019 at 02:56:12PM +0200, Michal Hocko wrote:
> On Mon 10-06-19 20:12:48, Minchan Kim wrote:
> > When a process expects no accesses to a certain memory range, it could
> > give a hint to kernel that the pages can be reclaimed when memory pressure
> > happens but data should be
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
head: 3ce5aceb5dee298b082adfa2baa0df5a447c1b0b
commit: faaeff98666c24376cebd0b106504d05a36881d1 [24/33] perf/x86/intel: Add
more Icelake CPUIDs
config: x86_64-rhel-7.6 (attached as .config)
compiler: gcc-7 (Debian
On 6/19/19 1:12 AM, Peter Zijlstra wrote:
> On Tue, Jun 18, 2019 at 04:16:20PM +, Vineet Gupta wrote:
>
>>> +/*
>>> + * To make atomic update of patched instruction available we need to
>>> guarantee
>>> + * that this instruction doesn't cross L1 cache line boundary.
>>> + *
> Oh urgh. Is
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
head: 3ce5aceb5dee298b082adfa2baa0df5a447c1b0b
commit: faaeff98666c24376cebd0b106504d05a36881d1 [24/33] perf/x86/intel: Add
more Icelake CPUIDs
config: x86_64-rhel-7.6 (attached as .config)
compiler: gcc-7 (Debian
Hi Waiman,
On Wed, Jun 19, 2019 at 10:16 AM Waiman Long wrote:
>
> There are concerns about memory leaks from extensive use of memory
> cgroups as each memory cgroup creates its own set of kmem caches. There
> is a possiblity that the memcg kmem caches may remain even after the
> memory cgroups
On Wed, Jun 19, 2019 at 02:27:50PM +0200, Michal Hocko wrote:
> On Mon 10-06-19 20:12:47, Minchan Kim wrote:
> > This patch is part of previous series:
> > https://lore.kernel.org/lkml/20190531064313.193437-1-minc...@kernel.org/T/#u
> > Originally, it was created for external madvise hinting
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
head: 3ce5aceb5dee298b082adfa2baa0df5a447c1b0b
commit: 2a538fda82824a7722e296be656bb5d11d91a9cb [23/33] perf/x86/intel: Add
Icelake desktop CPUID
config: x86_64-rhel-7.6 (attached as .config)
compiler: gcc-7 (Debian
Sorry for the late review... Ah!
On Tue, Jun 11, 2019 at 02:26:25PM +0200, Takashi Iwai wrote:
> @@ -354,7 +454,12 @@ module_param_string(path, fw_path_para,
> sizeof(fw_path_para), 0644);
> MODULE_PARM_DESC(path, "customized firmware image search path with a higher
> priority than default
Currently for CONFIG_SLUB, if a memcg kmem cache creation is failed and
the corresponding root kmem cache has SLAB_PANIC flag, the kernel will
be crashed. This is unnecessary as the kernel can handle the creation
failures of memcg kmem caches. Additionally CONFIG_SLAB does not
implement this
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On
> Behalf Of dann frazier
> Sent: Wednesday, May 22, 2019 4:23 PM
> To: Kirsher, Jeffrey T ; David S. Miller
> ; Shannon Nelson
> Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux-
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On
> Behalf Of Colin King
> Sent: Friday, June 7, 2019 11:19 AM
> To: Keller, Jacob E ; Kirsher, Jeffrey T
> ; David S . Miller ;
> intel-wired-...@lists.osuosl.org; net...@vger.kernel.org
> Cc:
On Wed, Jun 19, 2019 at 3:50 PM Dave Hansen wrote:
>
> I have a bit of a grievance to file. :)
>
> I'm seeing "Cannot create slab..." panic()s coming from
> kmem_cache_open() when trying to create memory cgroups on a Fedora
> system running 5.2-rc's. The panic()s happen when failing to create
>
On Wed, 2019-06-19 at 22:32 +, Tao Ren wrote:
> Thank you for the quick response, Brendan.
>
> Aspeed I2C bus frequency is defined by 3 parameters
> (base_clk_divisor, clk_high_width, clk_low_width), and I choose
> base_clk_divisor because it controls all the Aspeed I2C timings (such
> as
I have a bit of a grievance to file. :)
I'm seeing "Cannot create slab..." panic()s coming from
kmem_cache_open() when trying to create memory cgroups on a Fedora
system running 5.2-rc's. The panic()s happen when failing to create
memcg-specific slabs because the memcg code passes through the
On Wed, Jun 19, 2019 at 12:38:38PM +0200, Jan Kara wrote:
> On Tue 18-06-19 07:21:56, Amir Goldstein wrote:
> > > > Right, but regardless of the spec we have to consider that the
> > > > behaviour of XFS comes from it's Irix heritage (actually from EFS,
> > > > the predecessor of XFS from the late
From: Alexander Duyck
Add support for what I am referring to as "bubble hinting". Basically the
idea is to function very similar to how the balloon works in that we
basically end up madvising the page as not being used. However we don't
really need to bother with any deflate type logic since the
This series provides an asynchronous means of hinting to a hypervisor
that a guest page is no longer in use and can have the data associated
with it dropped. To do this I have implemented functionality that allows
for what I am referring to as waste page treatment.
I have based many of the terms
On 6/19/19 2:25 PM, Brendan Higgins wrote:
> On Wed, Jun 19, 2019 at 2:00 PM Tao Ren wrote:
>>
>> Some intermittent I2C transaction failures are observed on Facebook CMM and
>> Minipack (ast2500) BMC platforms, because slave devices (such as CPLD, BIC
>> and etc.) NACK the address byte sometimes.
From: Alexander Duyck
In order to pave the way for free page hinting in virtualized environments
we will need a way to get pages out of the free lists and identify those
pages after they have been returned. To accomplish this patch adds the
concept of an "aerated" flag, which is essentially
From: Alexander Duyck
In order to enable the use of the zone from the list manipulator functions
I will need access to the zone pointer. As it turns out most of the
accessors were always just being directly passed >free_area[order]
anyway so it would make sense to just fold that into the
From: Alexander Duyck
This patch is meant to move the head/tail adding logic out of the shuffle
code and into the __free_one_page function since ultimately that is where
it is really needed anyway. By doing this we should be able to reduce the
overhead and can consolidate all of the list
From: Alexander Duyck
Add a set of pointers we shall call "boundary" which represents the upper
boundary between the "raw" and "aerated" pages. The general idea is that in
order for a page to cross from one side of the boundary to the other it
will need to go through the aeration treatment.
By
From: Alexander Duyck
Add support for aerating memory using the hinting feature provided by
virtio-balloon. Hinting differs from the regular balloon functionality in
that is is much less durable than a standard memory balloon. Instead of
creating a list of pages that cannot be accessed the pages
From: Alexander Duyck
In order to support page aeration it will be necessary to store and
retrieve the migratetype of a page. To enable that I am moving the set and
get operations for pcppage_migratetype into the mmzone header so that they
can be used when adding or removing pages from the free
On Tue, Jun 11, 2019 at 4:40 PM Dan Williams wrote:
>
> For good reason, the standard device_lock() is marked
> lockdep_set_novalidate_class() because there is simply no sane way to
> describe the myriad ways the device_lock() ordered with other locks.
> However, that leaves subsystems that know
On Wed, 2019-06-19 at 14:58 -0700, Guenter Roeck wrote:
> On Tue, Jun 18, 2019 at 03:27:59PM +0100, Ben Hutchings wrote:
> > This is the start of the stable review cycle for the 3.16.69 release.
> > There are 10 patches in this series, which will be posted as responses
> > to this one. If anyone
On Tue, Jun 18, 2019 at 03:27:59PM +0100, Ben Hutchings wrote:
> This is the start of the stable review cycle for the 3.16.69 release.
> There are 10 patches in this series, which will be posted as responses
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
Add documentation for Spectre vulnerability and the mitigation mechanisms:
- Explain the problem and risks
- Document the mitigation mechanisms
- Document the command line controls
- Document the sysfs files
Co-developed-by: Andi Kleen
Signed-off-by: Andi Kleen
Co-developed-by: Tim Chen
19.06.2019 16:52, Dmitry Osipenko пишет:
> 19.06.2019 15:22, Jon Hunter пишет:
>>
>> On 19/06/2019 12:10, Dmitry Osipenko wrote:
>>> 19.06.2019 13:55, Jon Hunter пишет:
On 19/06/2019 11:27, Dmitry Osipenko wrote:
> 19.06.2019 13:04, Jon Hunter пишет:
>>
>> On 19/06/2019
[ add Andi ]
On Wed, Jun 19, 2019 at 6:00 AM Bjorn Helgaas wrote:
>
> On Tue, Jun 18, 2019 at 12:40 AM Nadav Amit wrote:
> >
> > > On Jun 17, 2019, at 10:33 PM, Nadav Amit wrote:
> > >
> > >> On Jun 17, 2019, at 9:57 PM, Andrew Morton
> > >> wrote:
> > >>
> > >> On Wed, 12 Jun 2019 21:59:03
On Wed, Jun 19, 2019 at 01:40:50PM +, Nicholas Johnson wrote:
> At least I have found out that git send-email uses terrible
> encoding and adds the patch as an attachment
This must be configurable somehow because many people use git
send-email to send plain-text patches.
> On Sat, Jun 15,
Convert the common panel bindings to DT schema consolidating scattered
definitions to a single schema file.
The 'simple-panel' binding just a collection of properties and not a
complete binding itself. All of the 'simple-panel' properties are
covered by the panel-common.txt binding with the
On 6/18/19 2:24 PM, Tim Chen wrote:
> +
> +_lab1:
> +
> +References on Spectre
> +-
Thomas,
I accidentally left a stray "_lab1:" label. Should be removed.
Sending you an updated v5 version separately.
Tim
On Wed, Jun 19, 2019 at 12:56:26PM -0600, Logan Gunthorpe wrote:
> Presently, there is no path to DMA map P2PDMA memory, so if a TLP
> targeting this memory hits the root complex and an IOMMU is present,
> the IOMMU will reject the transaction, even if the RC would support
> P2PDMA.
>
> So until
On Wed, Jun 19, 2019 at 07:31:40PM +0200, Borislav Petkov wrote:
> On Mon, Jun 17, 2019 at 11:00:16AM -0700, Fenghua Yu wrote:
> > AVX512 Vector Neural Network Instructions (VNNI) in Intel Deep Learning
> > Boost support BFLOAT16 format (BF16).
>
> That sentence is a mouthful and I have no clue
From: Martin Blumenstingl
Date: Tue, 18 Jun 2019 22:39:27 +0200
> Commit ce4ab73ab0c27c ("net: stmmac: drop the reset delays from struct
> stmmac_mdio_bus_data") moved the reset delay array from struct
> stmmac_mdio_bus_data to a stack variable.
> The values from the array inside struct
On Tue, 18 Jun, at 02:33:18PM, Peter Zijlstra wrote:
> On Tue, Jun 18, 2019 at 11:43:19AM +0100, Matt Fleming wrote:
> > This works for me under all my tests. Thoughts?
> >
> > --->8---
> >
> > diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
> > index
On Wed, Jun 19, 2019 at 07:36:28PM +0200, Borislav Petkov wrote:
> On Mon, Jun 17, 2019 at 11:00:15AM -0700, Fenghua Yu wrote:
> > @@ -832,33 +857,6 @@ void get_cpu_cap(struct cpuinfo_x86 *c)
> > c->x86_capability[CPUID_D_1_EAX] = eax;
> > - /* Additional Intel-defined flags: level
From: Matthias Kaehlcke
Date: Tue, 18 Jun 2019 14:14:40 -0700
> empty_child_inc/dec() use the ternary operator for conditional
> operations. The conditions involve the post/pre in/decrement
> operator and the operation is only performed when the condition
> is *not* true. This is hard to parse
On Wed, Jun 19, 2019 at 2:00 PM Tao Ren wrote:
>
> Some intermittent I2C transaction failures are observed on Facebook CMM and
> Minipack (ast2500) BMC platforms, because slave devices (such as CPLD, BIC
> and etc.) NACK the address byte sometimes. The issue can be resolved by
> increasing base
On Wed, Jun 19, 2019 at 10:42 PM Jason Gunthorpe wrote:
>
> On Wed, Jun 19, 2019 at 10:18:43PM +0200, Daniel Vetter wrote:
> > On Wed, Jun 19, 2019 at 10:13 PM Jason Gunthorpe wrote:
> > > On Wed, Jun 19, 2019 at 09:57:15PM +0200, Daniel Vetter wrote:
> > > > On Wed, Jun 19, 2019 at 6:50 PM
From: Nathan Huckleberry
Date: Wed, 19 Jun 2019 11:17:15 -0700
> There was an unused variable 'mvpp2_dbgfs_prs_pmap_fops'
> Added a usage consistent with other fops to dump pmap
> to userspace.
>
> Cc: clang-built-li...@googlegroups.com
> Link:
On 6/19/2019 4:07 PM, Vince Weaver wrote:
On Wed, 19 Jun 2019, syzbot wrote:
syzbot found the following crash on:
HEAD commit:0011572c Merge branch 'for-5.2-fixes' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12c38d66a0
From: Puranjay Mohan
Date: Wed, 19 Jun 2019 23:15:56 +0530
> Include the generic PCI definitions from include/uapi/linux/pci_regs.h
> change PCI_REV_ID to PCI_REVISION_ID to make it compatible with the
> generic define.
> This driver uses only one generic PCI define.
>
> Signed-off-by: Puranjay
On Wed, 2019-06-19 at 10:38 +0200, Amadeusz Sławiński wrote:
> On Tue, 18 Jun 2019 08:58:22 -0700
> Ranjani Sridharan wrote:
>
> > On Tue, 2019-06-18 at 13:00 +0200, Amadeusz Sławiński wrote:
> > > On Mon, 17 Jun 2019 13:51:42 -0700
> > > Ranjani Sridharan wrote:
> > >
> > > > On Mon,
b bb bb bb bb bb
>
> Padding (ptrval): 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
> 5a
> Padding (ptrval): 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
> 5a
> Padding (ptrval): 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5
From: "J. Bruce Fields"
Jeff's picking up more responsibilities elsewhere, and Chuck's agreed to
take over.
For now, as before, nothing's changing day-to-day, but I want to have a
co-maintainer if only for bus factor.
Acked-by: Jeff Layton
Signed-off-by: J. Bruce Fields
---
MAINTAINERS | 2
Hi Li,
On Wed, Jun 19, 2019 at 08:36:06AM +0800, Wanpeng Li wrote:
> On Tue, 18 Jun 2019 at 21:36, Marcelo Tosatti wrote:
> >
> > On Mon, Jun 17, 2019 at 07:24:44PM +0800, Wanpeng Li wrote:
> > > From: Wanpeng Li
> > >
> > > Dedicated instances are currently disturbed by unnecessary jitter due
On Tue, Jun 11, 2019 at 05:25:48PM +0200, Rafael J. Wysocki wrote:
On 6/8/2019 1:46 PM, Sasha Levin wrote:
From: "Rafael J. Wysocki"
[ Upstream commit d491f2b75237ef37d8867830ab7fad8d9659e853 ]
If a PCI driver leaves the device handled by it in D0 and calls
pci_save_state() on the device in
ZYNQMP_PM_CAPABILITY_POWER capability is not supported by firmware
and hence needs to be removed
Signed-off-by: Tejas Patel
Signed-off-by: Michal Simek
Signed-off-by: Jolly Shah
---
include/linux/firmware/xlnx-zynqmp.h | 1 -
1 file changed, 1 deletion(-)
diff --git
On Wed, Jun 19, 2019 at 10:07 PM Jason A. Donenfeld wrote:
>
> On Wed, Jun 19, 2019 at 10:02 PM Arnd Bergmann wrote:
> > > get_jiffies_boot_64 26
> > > ktime_get_coarse_boottime 26
> > > ktime_get_boot_fast_ns with tsc 70
> > > ktime_get_boot_fast_ns with hpet 4922
> > > ktime_get_boot_fast_ns
On Tue, 2019-06-18 at 23:06 +0200, Arnd Bergmann wrote:
> On Tue, Jun 18, 2019 at 10:39 PM Johannes Berg
> wrote:
> > On Tue, 2019-06-18 at 22:33 +0200, Arnd Bergmann wrote:
> > It seems to me though that this is far more complex than what I'm
> > proposing? What I'm proposing there doesn't even
ZZ
Padding (ptrval): 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
5a
Padding (ptrval): 5a 5a 5a 5a 5a 5a 5a 5a
CPU: 193 PID: 1557 Comm: kworker/193:1 Tainted: GB W
5.2.0-rc5-next-20190619+ #8
Hardware name: HPE Apollo 70 /C01_APACHE_MB
On Wed, Jun 19, 2019 at 4:41 PM 'Saravana Kannan' via kernel-team
wrote:
> > > On Wed, Jun 19, 2019, 11:55 AM 'Joel Fernandes' via kernel-team
> > > wrote:
> > >>
> > >> On Wed, Jun 19, 2019 at 2:35 PM Greg Kroah-Hartman
> > >> wrote:
> > >> >
> > >> > On Wed, Jun 19, 2019 at 02:01:36PM -0400,
On Wed, Jun 19, 2019 at 12:19 PM Chris Wilson wrote:
>
> > Do you have the oops itself at all?
>
> An example at
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6310/fi-kbl-x1275/dmesg0.log
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6310/fi-kbl-x1275/boot0.log
>
> The bug causing the
Missatge de Gwendal Grignou del dia dv., 14 de
juny 2019 a les 23:56:
>
> On Sat, May 18, 2019 at 2:53 AM Jonathan Cameron wrote:
> >
> > On Fri, 17 May 2019 16:38:56 -0700
> > Gwendal Grignou wrote:
> >
> > > Add a IIO driver that reports the angle between the lid and the base for
> > >
On Wed, Jun 19, 2019 at 11:17 AM 'Nathan Huckleberry' via Clang Built
Linux wrote:
>
> There was an unused variable 'mvpp2_dbgfs_prs_pmap_fops'
> Added a usage consistent with other fops to dump pmap
> to userspace.
> Changes from v1 -> v2
> * Fix typo
> * Change commit prefix to debugfs
Hi Steve,
>
> I have taken your previous patch, fixed the whitespace like we discussed
> and updated the commit message to add more details. Also, I have
> simplified your original patch slightly by using a single define in the
> include file instead of repeating the same value for each LDO[1-4].
On Wed, Jun 19, 2019 at 1:09 PM 'Joel Fernandes' via kernel-team
wrote:
>
> On Wed, Jun 19, 2019 at 3:59 PM 'Saravana Kannan' via kernel-team
> wrote:
> >
> >
> >
> > On Wed, Jun 19, 2019, 11:55 AM 'Joel Fernandes' via kernel-team
> > wrote:
> >>
> >> On Wed, Jun 19, 2019 at 2:35 PM Greg
> On Jun 19, 2019, at 6:00 AM, Bjorn Helgaas wrote:
>
> On Tue, Jun 18, 2019 at 12:40 AM Nadav Amit wrote:
>>> On Jun 17, 2019, at 10:33 PM, Nadav Amit wrote:
>>>
On Jun 17, 2019, at 9:57 PM, Andrew Morton
wrote:
On Wed, 12 Jun 2019 21:59:03 -0700 Nadav Amit wrote:
From: Krzysztof Kozlowski
Date: Tue, 18 Jun 2019 20:54:22 +0200
> Fix wrong indentation of goto return.
>
> Signed-off-by: Krzysztof Kozlowski
Applied, thanks.
While the DOC at the beginning of lib/bitmap.c explicitly states that
"The number of valid bits in a given bitmap does _not_ need to be an
exact multiple of BITS_PER_LONG.", some of the bitmap operations do
indeed access BITS_PER_LONG portions of the provided bitmap no matter
the size of the
On Wed, 19 Jun 2019, Bjorn Helgaas wrote:
> On Wed, Jun 19, 2019 at 04:27:52PM +, Kirill Smelkov wrote:
> > Hi Julia, everyone.
> >
> > On Wed, Jun 19, 2019 at 12:28:47PM +0200, Julia Lawall wrote:
> > > Hi,
> > >
> > > Can you forward this patch to the people below if you think it is
> >
On Wed, Jun 19, 2019 at 04:27:52PM +, Kirill Smelkov wrote:
> Hi Julia, everyone.
>
> On Wed, Jun 19, 2019 at 12:28:47PM +0200, Julia Lawall wrote:
> > Hi,
> >
> > Can you forward this patch to the people below if you think it is
> > appropriate?
>
> Yes, this patch is appropriate. It was
101 - 200 of 886 matches
Mail list logo
