On Tuesday 13 February 2018 18:12:21 Ville Syrjälä wrote:
> On Tue, Feb 13, 2018 at 05:04:37PM +0100, Pali Rohár wrote:
> > $ cat /sys/kernel/debug/dri/0/i915_gem_stolen
> > Stolen:
> >8b55bf17e080:g16KiB 40 40 [ 0 0 0 0 ] 0 LLC dirty
> > (pinned x 1) (ggtt offset: 00083000, s
On Mon, Feb 12, 2018 at 10:35:50AM +0100, Philippe Ombredanne wrote:
> Jerry,
>
> On Mon, Feb 12, 2018 at 6:21 AM, Jerry Hoemann wrote:
> > Minor white space changes and some name clean up.
> >
> > Signed-off-by: Jerry Hoemann
> > ---
> > drivers/watchdog/hpwdt.c | 49
> > +
Baoquan He writes:
> Hi Eric,
>
> On 02/11/18 at 09:08pm, Eric W. Biederman wrote:
>> Baoquan He writes:
>>
>> > This is a regression fix.
>> >
>> > Before, to fix erratum AVR31, commit 522e66464467 ("x86/apic: Disable
>> > I/O APIC before shutdown of the local APIC") moved lapic_shutdown()
>>
On Tue, Feb 13, 2018 at 07:18:08PM +0200, Andy Shevchenko wrote:
> On Tue, Feb 13, 2018 at 7:11 PM, Alexey Dobriyan wrote:
> > On Tue, Feb 13, 2018 at 06:02:27PM +0200, Andy Shevchenko wrote:
> >> On Sat, Feb 10, 2018 at 11:11 PM, Alexey Dobriyan
> >> wrote:
> >> > Once upon a time module parame
On Tue, Feb 13, 2018 at 06:43:41PM +0100, Pali Rohár wrote:
> On Tuesday 13 February 2018 18:12:21 Ville Syrjälä wrote:
> > On Tue, Feb 13, 2018 at 05:04:37PM +0100, Pali Rohár wrote:
> > > $ cat /sys/kernel/debug/dri/0/i915_gem_stolen
> > > Stolen:
> > >8b55bf17e080:g16KiB 40 4
Add suffix ULL to constant 1000 in order to give the compiler complete
information about the proper arithmetic to use. Notice that this
constant is used in a context that expects an expression of type
u64 (64 bits, unsigned).
The expression 1000 * sampling_us is currently being evaluated
using 32-
From: Kieran Bingham
The r8a7792 Wheat board has two ADV7513 devices sharing a single I2C
bus, however in low power mode the ADV7513 will reset it's slave maps to
use the hardware defined default addresses.
The ADV7511 driver was adapted to allow the two devices to be registered
correctly - but
From: Kieran Bingham
Back in 2014, Jean-Michel provided patches [0] to implement a means of
describing software defined I2C addresses for devices through the DT nodes.
The patch to implement the function "i2c_new_secondary_device()" was integrated,
but the corresponding driver update didn't get
From: Jean-Michel Hautbois
The ADV7604 has thirteen 256-byte maps that can be accessed via the main
I2C ports. Each map has it own I2C address and acts as a standard slave
device on the I2C bus.
Extend the device tree node bindings to be able to override the default
addresses so that address con
From: Kieran Bingham
The ADV7511 has four 256-byte maps that can be accessed via the main I2C
ports. Each map has it own I2C address and acts as a standard slave
device on the I2C bus.
Allow a device tree node to override the default addresses so that
address conflicts with other devices on the
On Sun, Feb 11, 2018 at 10:21:05PM -0700, Jerry Hoemann wrote:
> Update Module Author and permission on parameters so that the
> parameters show up in sysfs.
>
Does it really add value to see the module parameters in sysfs ?
You would get both in standardized form by enabling WATCHDOG_SYSFS.
> S
On Tue, 2018-02-13 at 11:34 -0600, Dennis Zhou wrote:
> Hi Eric,
>
> On Tue, Feb 13, 2018 at 05:35:26AM -0800, Eric Dumazet wrote:
> >
> > Also I would consider using this fix as I had warnings of cpus being
> > stuck there for more than 50 ms :
> >
> >
> > diff --git a/mm/percpu-vm.c b/mm/perc
From: Jean-Michel Hautbois
The ADV7604 has thirteen 256-byte maps that can be accessed via the main
I2C ports. Each map has it own I2C address and acts as a standard slave
device on the I2C bus.
Allow a device tree node to override the default addresses so that
address conflicts with other devic
From: Kieran Bingham
The ADV7511 has four 256-byte maps that can be accessed via the main I2C
ports. Each map has it own I2C address and acts as a standard slave
device on the I2C bus.
Extend the device tree node bindings to be able to override the default
addresses so that address conflicts wit
There is a permission discrepancy when consulting shm ipc
object metadata between /proc/sysvipc/shm (0444) and the
SHM_STAT shmctl command. The later does permission checks
for the object vs S_IRUGO. As such there can be cases where
EACCESS is returned via syscall but the info is displayed
anyways
On Tue, Feb 13, 2018 at 7:00 PM, Mika Westerberg
wrote:
> From: Radion Mirchevsky
>
> This is needed by the new ICM interface to find xdomains by route string
> instead of link and depth.
> + xd = switch_find_xdomain(tb->root_switch, &lookup);
> + if (xd) {
> + get_dev
There is a permission discrepancy when consulting shm ipc
object metadata between /proc/sysvipc/sem (0444) and the
SEM_STAT semctl command. The later does permission checks
for the object vs S_IRUGO. As such there can be cases where
EACCESS is returned via syscall but the info is displayed
anyways
There is a permission discrepancy when consulting msq ipc
object metadata between /proc/sysvipc/msg (0444) and the
MSG_STAT shmctl command. The later does permission checks
for the object vs S_IRUGO. As such there can be cases where
EACCESS is returned via syscall but the info is displayed
anyways
Hi,
The following patches adds the discussed[1] new command for shm
as well as for sems and msq as they are subject to the same discrepancies
for ipc object permission checks between the syscall and via procfs.
These new commands are justified in that (1) we are stuck with this
semantics as changi
We support normal mode, TDM mode and pm.
Changes since v3: [addressed Mark's comments]
* use C++ comments for SPDX identifier
* removed some unused widgets and controls (channel enable MUXes, TDM, DSD
related stuff)
* removed set_dai_mute, set_bias_level, set_dai_sysclk as they are not used.
* r
On Thu, Feb 08, 2018 at 02:46:32PM +0100, Marek Szyprowski wrote:
> Hi Krzysztof,
>
> On 2018-01-30 22:18, Krzysztof Kozlowski wrote:
> > Hi,
> >
> > Changes since v1:
> > 1. New patch (1/4) calling devm_of_platform_populate() in PMU driver,
> > following Rob's advice.
> > 2. The DTS patches
AK5558 is a 32-bit, 768 kHZ sampling, differential input ADC
for digital audio systems.
Datasheet is available at:
https://www.akm.com/akm/en/file/datasheet/AK5558VN.pdf
Initial patch includes support for normal and TDM modes.
Reviewed-by: Andy Shevchenko
Reviewed-by: Fabio Estevam
Signed-off
Document the bindings for AK5558 ADC.
Reviewed-by: Rob Herring
Signed-off-by: Daniel Baluta
---
Documentation/devicetree/bindings/sound/ak5558.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/ak5558.txt
diff --git a/D
2018-02-13 17:17 GMT+00:00 Ingo Molnar :
>
> * Andrei Vagin wrote:
>
>> On Tue, Feb 13, 2018 at 12:02:49PM +0300, Kirill A. Shutemov wrote:
>> > On Tue, Feb 13, 2018 at 12:41:22AM -0800, Andrei Vagin wrote:
>> > > On Tue, Feb 13, 2018 at 11:08:16AM +0300, Kirill A. Shutemov wrote:
>> > > > On Mon,
On Tue, 2018-02-13 at 18:21 +0200, Andy Shevchenko wrote:
> +Cc: Authors and correct ML
>
> On Mon, Feb 12, 2018 at 11:09 AM, kitestramuort
> wrote:
> > don't know if this is intended. In 4.15.2 i have:
>
> AFAIU the driver now binds to the hardcoded value of a PA of the
> device. So, you still
On Tue, Feb 13, 2018 at 4:10 AM, Tomasz Figa wrote:
> Hi Vivek,
>
> Thanks for the patch. Please see my comments inline.
>
> On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam
> wrote:
>> While handling the concerned iommu, there should not be a
>> need to power control the drm devices from iommu inter
On 02/13/2018 08:08 AM, Jiri Olsa wrote:
On Mon, Feb 12, 2018 at 02:22:30PM -0800, Raghavendra Rao Ananta wrote:
On 02/12/2018 01:21 PM, Jiri Olsa wrote:
On Mon, Feb 12, 2018 at 10:04:42PM +0100, Jiri Olsa wrote:
On Mon, Feb 12, 2018 at 09:42:05AM -0800, Raghavendra Rao Ananta wrote:
Hi J
When the linux kernel is build with (typical kernel ship with Debian
installer):
CONFIG_FB=y
CONFIG_FB_OF=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_FB_RADEON=m
The offb driver takes precedence over module radeonfb. It is then
impossible to load the module, error reported is:
[ 96.551486] radeonf
On Tue, Feb 13, 2018 at 1:05 PM, Bartlomiej Zolnierkiewicz
wrote:
> On Saturday, February 10, 2018 01:48:55 PM Mathieu Malaterre wrote:
>> Hi,
>>
>> On Thu, Feb 8, 2018 at 2:28 PM, Bartlomiej Zolnierkiewicz
>> wrote:
>> > On Wednesday, January 31, 2018 08:51:23 PM Mathieu Malaterre wrote:
>> >>
On Sun, Feb 11, 2018 at 10:21:07PM -0700, Jerry Hoemann wrote:
> Update Kconfig file to show that hpwdt now selects WATCHDOG_CORE.
>
> Signed-off-by: Jerry Hoemann
Please merge with previous patch to preserve bisectability.
> ---
> drivers/watchdog/Kconfig | 1 +
> 1 file changed, 1 insertion(
On Mon, Feb 12, 2018 at 10:06:21AM +0100, Marcus Folkesson wrote:
> Hi Jerry,
>
> On Sun, Feb 11, 2018 at 10:21:06PM -0700, Jerry Hoemann wrote:
> > Follow Documentation/watchdog/convert_drivers_to_kernel_api.txt to
> > convert hpwdt from legacy watchdog driver to use the watchdog core.
> >
> > R
* Dmitry Safonov <0x7f454...@gmail.com> wrote:
> 2018-02-13 17:17 GMT+00:00 Ingo Molnar :
> >
> > * Andrei Vagin wrote:
> >
> >> On Tue, Feb 13, 2018 at 12:02:49PM +0300, Kirill A. Shutemov wrote:
> >> > On Tue, Feb 13, 2018 at 12:41:22AM -0800, Andrei Vagin wrote:
> >> > > On Tue, Feb 13, 2018
* Jia-Ju Bai wrote:
> The function kzalloc here is not called in atomic context.
> If nonblocking in efi_query_variable_store is true,
> namely it is in atomic context, efi_query_variable_store will return before
> this kzalloc is called.
> Thus GFP_ATOMIC is not necessary, and it can be replac
The function offb_destroy did not deallocate the color map leaving some
memory around after destruction. Call the color map deallocate function to
remove the memory leak.
Handle another case where color map should have been deallocated during an
error code path.
Fix memory leaks reported by kmeml
On 02/13/2018 07:20 AM, Igor Stoppa wrote:
Why alterations of page properties are not considered a risk and the physmap is?
And how would it be easier (i suppose) to attack the latter?
Alterations are certainly a risk but with the physmap the
mapping is already there. Find the address and you h
On Tue, Feb 13, 2018 at 09:49:27AM -0800, Eric Dumazet wrote:
> On Tue, 2018-02-13 at 11:34 -0600, Dennis Zhou wrote:
> > Hi Eric,
> >
> > On Tue, Feb 13, 2018 at 05:35:26AM -0800, Eric Dumazet wrote:
> > >
> > > Also I would consider using this fix as I had warnings of cpus being
> > > stuck the
On Fri, Feb 09, 2018 at 02:28:01PM +0530, Viresh Kumar wrote:
> The "cooling-min-level" and "cooling-max-level" properties are not
> parsed by any part of the kernel currently and the max cooling state of
> a CPU cooling device is found by referring to the cpufreq table instead.
>
> Remove the unu
With the fix from yesterday, these look good. Thanks, Neil.
Reviewed-by: Patrick Farrell
- Patrick
On 2/12/18, 5:52 PM, "lustre-devel on behalf of NeilBrown"
wrote:
These macros are no longer used, so they can
be removed.
Reviewed-by: James Simmons
Signed-off-by: Neil
On Tue, Feb 13, 2018 at 7:00 PM, Mika Westerberg
wrote:
> Preboot ACL is a mechanism that allows connecting Thunderbolt devices
> boot time in more secure way than the legacy Thunderbolt boot support.
> As with the legacy boot option, this also needs to be enabled from the
> BIOS before booting is
On Sun, Feb 11, 2018 at 10:21:10PM -0700, Jerry Hoemann wrote:
> The intent of this parameter is unclear and it sets up a
> race between the reset of the system by ASR and crashdump.
>
> The length of time between receipt of the pretimeout NMI
> and the ASR reset of the system is fixed by hardware
Commit-ID: adf9ca9c69a2ad8a82953119c57d5c6586c7d48d
Gitweb: https://git.kernel.org/tip/adf9ca9c69a2ad8a82953119c57d5c6586c7d48d
Author: Kirill A. Shutemov
AuthorDate: Fri, 9 Feb 2018 17:22:28 +0300
Committer: Ingo Molnar
CommitDate: Tue, 13 Feb 2018 19:04:43 +0100
x86/boot/compressed/6
On 02/12/18 03:12 PM, Junaid Shahid wrote:
> Hi Dave,
>
>
> On 02/12/2018 11:51 AM, Dave Watson wrote:
>
> > +static int gcmaes_encrypt_sg(struct aead_request *req, unsigned int
> > assoclen,
> > + u8 *hash_subkey, u8 *iv, void *aes_ctx)
> >
> > +static int gcmaes_decrypt_sg
On 13/02/2018, Jason Vas Dias wrote:
> Good day -
>
> I'd much appreciate some advice as to why, on my Intel x86_64
> ( DisplayFamily_DisplayModel : 06_3CH ), running either Linux 4.12.10,
> or Linux 3.10.0, any attempt to count all of :
> PERF_COUNT_HW_BRANCH_INSTRUCTIONS
> (or raw
On Fri, Feb 09, 2018 at 03:07:00PM -0800, Raghavendra Rao Ananta wrote:
> Perf framework doesn't allow creation of hardware events if
> the requested CPU is offline. However, creation of an event
> is achievable if the event is attached to the PMU as soon
> as the CPU is online again.
>
> So, intr
Hi Enric,
On Tue, Feb 13, 2018 at 11:40:44AM +0100, Enric Balletbo i Serra wrote:
> On 12/02/18 23:13, Brian Norris wrote:
> > On Sat, Feb 10, 2018 at 07:09:05PM +0800, Jeffy Chen wrote:
> >> Add support for specifying event actions to trigger wakeup when using
> >> the gpio-keys input device as a
On Mon, 2018-02-12 at 07:59 +0100, Takashi Iwai wrote:
> On Sun, 11 Feb 2018 05:20:06 +0100,
> Ben Hutchings wrote:
> >
> > 3.2.99-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Takashi Iwai
> >
> > commit 8428a8ebde2db1e988e41a584
On Tue, Feb 13, 2018 at 6:59 PM, Gustavo A. R. Silva
wrote:
> Add suffix ULL to constant 1000 in order to give the compiler complete
> information about the proper arithmetic to use. Notice that this
> constant is used in a context that expects an expression of type
> u64 (64 bits, unsigned).
>
>
On Sun, Feb 11, 2018 at 04:19:38AM -0800, tip-bot for Kirill A. Shutemov wrote:
...
> diff --git a/arch/x86/boot/compressed/head_64.S
> b/arch/x86/boot/compressed/head_64.S
> index d598d65..af9ffbd 100644
> --- a/arch/x86/boot/compressed/head_64.S
> +++ b/arch/x86/boot/compressed/head_64.S
...
> @
On Tue, Feb 13, 2018 at 4:14 PM, Cosmin-Gabriel Samoila
wrote:
> We support Normal Mode, TDM Mode and PM.
>
Read the comments Mark and me gave against another [1] submission.
[1]: https://www.spinics.net/lists/alsa-devel/msg73471.html
> Changes since V1:
> - support only i2c
> - i2c probe / rem
From: Markus Elfring
Date: Tue, 13 Feb 2018 19:30:19 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation in add_card()
Adjust eight checks for null pointers
drivers/firewire/nosy.c
On Mon, Feb 05, 2018 at 05:45:53AM -0500, Suravee Suthikulpanit wrote:
> Currently, iommu_unmap, iommu_unmap_fast and iommu_map_sg return
> size_t. However, some of the return values are error codes (< 0),
> which can be misinterpreted as large size. Therefore, returning size 0
> instead to signif
On Mon, Feb 05, 2018 at 11:29:19PM +0530, Vivek Gautam wrote:
> Unmap returns a size_t all throughout the IOMMU framework.
> Make io-pgtable match this convention.
> Moreover, there isn't a need to have a signed int return type
> as we return 0 in case of failures.
>
> Signed-off-by: Vivek Gautam
From: Markus Elfring
Date: Tue, 13 Feb 2018 18:33:45 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/firewire/nosy.c | 1 -
1 file changed, 1 deletion(-)
diff --g
From: Markus Elfring
Date: Tue, 13 Feb 2018 19:20:26 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The script “checkpatch.pl” pointed information out like the following.
Comparison to NULL could be written !…
Thus fix the affected source code pl
From: Bartosz Golaszewski
The reset framework only supports device-tree. There are some platforms
however, which need to use it even in legacy, board-file based mode.
An example of such architecture is the DaVinci family of SoCs which
supports both device tree and legacy boot modes and we don't
On 13 February 2018 at 18:07, Ingo Molnar wrote:
>
> * Jia-Ju Bai wrote:
>
>> The function kzalloc here is not called in atomic context.
>> If nonblocking in efi_query_variable_store is true,
>> namely it is in atomic context, efi_query_variable_store will return before
>> this kzalloc is called.
On Tue, Feb 13, 2018 at 06:00:26PM +0100, SF Markus Elfring wrote:
> Omit an extra message for a memory allocation failure in this function.
[snip]
> --- a/drivers/firmware/efi/apple-properties.c
> +++ b/drivers/firmware/efi/apple-properties.c
> @@ -158,10 +158,8 @@ static int __init unmarshal_devi
Hi Abbott,
On 10/11/2017 01:22 AM, Abbott Liu wrote:
> Hi,all:
>These patches add arch specific code for kernel address sanitizer
> (see Documentation/kasan.txt).
>
>1/8 of kernel addresses reserved for shadow memory. There was no
> big enough hole for this, so virtual addresses for sh
On 02/13/18 08:42 AM, Stephan Mueller wrote:
> > +static int gcmaes_encrypt_sg(struct aead_request *req, unsigned int
> > assoclen, + u8 *hash_subkey, u8 *iv, void *aes_ctx)
> > +{
> > + struct crypto_aead *tfm = crypto_aead_reqtfm(req);
> > + unsigned long auth_tag_len = crypto
On Sun, Feb 11, 2018 at 11:04 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sun, 11 Feb 2018 21:56:42 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
Linus, same comment as previously.
Commit-ID: 384f1d86a8890fcf8118add0b6a0785ee35f5a65
Gitweb: https://git.kernel.org/tip/384f1d86a8890fcf8118add0b6a0785ee35f5a65
Author: Jessica Yu
AuthorDate: Wed, 10 Jan 2018 00:51:23 +0100
Committer: Ingo Molnar
CommitDate: Tue, 13 Feb 2018 18:20:00 +0100
kprobes: Propagate error fro
Commit-ID: cea1e51c8357feb0e98464a82e1ad3ca2d0382a6
Gitweb: https://git.kernel.org/tip/cea1e51c8357feb0e98464a82e1ad3ca2d0382a6
Author: Jessica Yu
AuthorDate: Wed, 10 Jan 2018 00:51:24 +0100
Committer: Ingo Molnar
CommitDate: Tue, 13 Feb 2018 18:20:00 +0100
kprobes: Propagate error fro
Commit-ID: d101567aec6653cc372af3b9b957299fee06cca8
Gitweb: https://git.kernel.org/tip/d101567aec6653cc372af3b9b957299fee06cca8
Author: Rui Wang
AuthorDate: Mon, 18 Dec 2017 16:34:10 +0800
Committer: Ingo Molnar
CommitDate: Tue, 13 Feb 2018 19:20:05 +0100
selftests/x86/mpx: Fix incorre
Commit-ID: 93cce6eeafb7c90b9175ffe01913c4930fc4
Gitweb: https://git.kernel.org/tip/93cce6eeafb7c90b9175ffe01913c4930fc4
Author: Jia Zhang
AuthorDate: Mon, 1 Jan 2018 09:52:10 +0800
Committer: Ingo Molnar
CommitDate: Tue, 13 Feb 2018 19:23:43 +0100
x86/cpu: Rename cpu_data.x86_m
On Wed, Jan 24, 2018 at 12:36:22AM +0800, John Garry wrote:
> From: Zhichang Yuan
>
> The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in
> I/O port addresses. This patch implements the LPC host controller driver
> which perform the I/O operations on the underlying hardwar
On Mon, Oct 30, 2017 at 7:41 PM, Cong Wang wrote:
> On Mon, Oct 30, 2017 at 8:34 AM, syzbot
>
> wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> 4dc12ffeaeac939097a3f55c881d3dc3523dff0c
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
>> compiler: gcc (GCC)
Herzlichen Glückwunsch, Sie haben € 650.000, - in den monatlichen Auslosungen
von Euro Millions / Google Promo am 10. Februar 2018 gewonnen.
Kontaktieren Sie unseren Schadenregulierungsbeauftragten mit den folgenden
Informationen
Vollständiger Name
Heimatadresse
Geschlecht
Alter
Besetzung
Telef
On Tue, 2018-02-13 at 19:40 +0100, Lukas Wunner wrote:
> On Tue, Feb 13, 2018 at 06:00:26PM +0100, SF Markus Elfring wrote:
> > --- a/drivers/firmware/efi/apple-properties.c
> You didn't cc me on your submission even though I'm the author of
> 99% of this file. Please make an effort prior to submi
On Tue, Nov 14, 2017 at 4:30 AM, Girish Moodalbail
wrote:
> On 11/7/17 12:28 PM, syzbot wrote:
>>
>> Hello,
>>
>> syzkaller hit the following crash on
>> 287683d027a3ff83feb6c7044430c79881664ecf
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
>> compiler: gcc (GCC) 7.1.1
On 02/12/2018 08:15 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180212:
>
> Non-merge commits (relative to Linus' tree): 963
> 1297 files changed, 63627 insertions(+), 31515 deletions(-)
>
>
on i386:
ar
Add documentation for two attributes - status and hrv in
Documentation/ABI/testing/sysfs-bus-acpi. Compiled from git logs and the
ACPI specification.
Signed-off-by: Aishwarya Pant
---
Documentation/ABI/testing/sysfs-bus-acpi | 36
1 file changed, 36 insertions(+)
On 07/02/2018 20:44, Mathieu Malaterre wrote:
> Remove the __init annotation from pmu_init() to avoid the
> following warning.
>
> WARNING: vmlinux.o(.data+0x4739c): Section mismatch in reference from the
> variable via_pmu_driver to the function .init.text:pmu_init()
> The variable via_pmu_drive
Commit d92a8cfcb37e ("locking/lockdep: Rework FS_RECLAIM annotation") removed
reclaim_fs lockdep STATE.
Reflect the change in documentation.
While we are at it, also clarify formula to calculate number of state
bits.
Signed-off-by: Juri Lelli
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Jonathan Co
Add section about annotations that can be used to perform additional runtime
checking of locking correctness: assert that certain locks are held and
prevent accidental unlocking.
Signed-off-by: Juri Lelli
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Jonathan Corbet
Cc: linux-kernel@vger.kernel.org
C
On Mon, Nov 6, 2017 at 11:34 AM, Dmitry Vyukov wrote:
> On Sun, Nov 5, 2017 at 5:00 PM, Trond Myklebust
> wrote:
>>
>>
>> On Sun, 2017-11-05 at 11:53 +0300, Dmitry Vyukov wrote:
>>> On Sun, Nov 5, 2017 at 11:41 AM, syzbot
>>> >> om>
>>> wrote:
>>> > Hello,
>>> >
>>> > syzkaller hit the following
Hi,
a couple of patches to lockdep docs.
First one is a small fix for that fact that Peter made documentation
stale (as usual :P).
Second one is an RFC. I thought that adding some info about lockdep
asserts might help spread adoption even wider (mostly regarding
lockdep_pin_lock stuff, which is
Switch the tx_lock to a spinlock we allow clients to use rpmsg_trysend()
from atomic context.
In order to allow clients to sleep while waiting for space in the FIFO
we release the lock temporarily around the delay; which should be
replaced by sending a READ_NOTIF and waiting for the remote to sign
By switching the tx_lock to a spinlock we allow clients to use
rpmsg_trysend() from atomic context.
The mutex was interruptable as it was previously held for the duration
of some client waiting for available space in the FIFO, but this was
recently changed to only be held temporarily - allowing us
On Tue, Feb 13, 2018 at 1:29 AM, Avi Fishman wrote:
> On Tue, Feb 13, 2018 at 10:30 AM, Arnd Bergmann wrote:
>> On Tue, Feb 6, 2018 at 12:57 AM, Brendan Higgins
>> wrote:
>>> Add a common device tree for all Nuvoton NPCM750 BMCs and a board
>>> specific device tree for the NPCM750 (Poleg) evalua
According to the Intel Software Developers' Manual, Vol. 4, Order No.
335592, these macros have been reversed since they were added.
Fixes: 889facbee3e6 ("tools/power turbostat: v3.0: monitor Watts and
Temperature")
Signed-off-by: Matt Turner
---
tools/power/x86/turbostat/turbostat.c | 4 ++--
According to the Intel Software Developers' Manual, Vol. 4, Order No.
335592, these macros have been reversed since they were added in the
initial turbostat commit. The reversed definitions were presumably
copied from turbostat.c to this file.
Fixes: 9c63a650bb10 ("tools/power/x86/turbostat: share
On Tue, Feb 13, 2018 at 03:36:45PM +0200, Andy Shevchenko wrote:
> On Sat, Feb 10, 2018 at 11:41 AM, Miguel Ojeda
> wrote:
> > On Sat, Feb 10, 2018 at 10:20 AM, Willy Tarreau wrote:
> >> On Sat, Feb 10, 2018 at 09:58:44AM +0100, Miguel Ojeda wrote:
> >>> On Sat, Feb 10, 2018 at 12:50 AM, Robert A
On Thu, Nov 30, 2017 at 4:46 PM, Al Viro wrote:
> On Thu, Nov 30, 2017 at 05:18:33AM -0800, Christoph Hellwig wrote:
>> On Thu, Nov 30, 2017 at 02:07:19AM +, Al Viro wrote:
>> > Incidentally, grepping for sys_close() shows another piece of fun in
>> > net/netfilter/xt_bpf.c. Folks, ONCE DESCR
On Tue, Feb 13, 2018 at 8:39 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> The reset framework only supports device-tree. There are some platforms
> however, which need to use it even in legacy, board-file based mode.
>
> An example of such architecture is the DaVinci family of S
Signed-off-by: Mario Leinweber
---
mm/gup.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/mm/gup.c b/mm/gup.c
index 1b46e6e74881..7e463042df4a 100644
--- a/mm/gup.c
+++ b/mm/gup.c
@@ -141,6 +141,7 @@ static struct page *follow_page_pte(struct vm_area_struct
*vma,
Currently, x86_cache_size is of type int, which makes no sense as we
will never have a valid cache size equal or less than 0. So instead of
initializing this variable to -1, it can perfectly be initialized to 0
and use it as an unsigned variable instead.
Addresses-Coverity-ID: 1464429
Suggested-by
On Tue, Feb 13, 2018 at 03:54:04PM +0100, Christoph Hellwig wrote:
> Looks good:
>
> Reviewed-by: Christoph Hellwig
>
> Can you wire up your test cases for blktests?
Is blktests really the right place for this test? This failure is highly
dependent on the configuration of the filesystem that i
On 2/13/2018 11:00 AM, Joerg Roedel wrote:
On Tue, Feb 13, 2018 at 10:47:55AM -0500, Hook, Gary wrote:
dev_err(&iommu->dev->dev, "ILLEGAL...
I think its more something like iommu->iommu->dev.
Without actually running a driver and getting some debug info, I'll just
say that my ex
Some other drivers may be waiting for our extcon to show-up, exiting their
probe methods with -EPROBE_DEFER until we show up.
These drivers will typically get the cable state directly after getting
the extcon, this commit changes the int3496 code to wait for the initial
processing of the id-pin to
On Tue, Feb 13, 2018 at 9:05 PM, Gustavo A. R. Silva
wrote:
> It seems to me that it makes no sense for threshold_ns to be of type u64,
> because the expression threshold_us * 1000 will never exceed the 32-bit
> limits. So if you agree I can send a patch to change its type to u32
> instead.
What
Hi Andy,
Quoting Andy Shevchenko :
On Tue, Feb 13, 2018 at 6:59 PM, Gustavo A. R. Silva
wrote:
Add suffix ULL to constant 1000 in order to give the compiler complete
information about the proper arithmetic to use. Notice that this
constant is used in a context that expects an expression of ty
From: Kieran Bingham
The FCPVB handles the interface between the VSPB and memory, while the
FCPVD handles the interface between the VSPD and memory.
Signed-off-by: Kieran Bingham
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 27 +++
1 file changed, 27 insertions(+)
diff
From: Kieran Bingham
The VSPD includes a CLUT on RPF2. Ensure that the register space is
mapped correctly to support this.
Signed-off-by: Kieran Bingham
---
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/re
From: Kieran Bingham
The VSPD includes a CLUT on RPF2. Ensure that the register space is
mapped correctly to support this.
Signed-off-by: Kieran Bingham
---
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/re
From: Kieran Bingham
The r8a77995 has a VSPBS to support image processing such as blending of
two input images, and has two VSPDs to handle display pipelines with a
DU.
Signed-off-by: Kieran Bingham
---
v2:
- Fix VSPD register map size
- Squash VSPBS and VSPD patches together
arch/arm64/bo
During boot we poison struct page memory in order to ensure that no one is
accessing this memory until the struct pages are initialized in
__init_single_page().
This patch adds more scrutiny to this checking, by making sure that flags
do not equal to poison pattern when the are accessed. The patte
Memory sections are combined into "memory block" chunks. These chunks are
the units upon which memory can be added and removed.
On x86, the new memory may be added after the end of the boot memory,
therefore, if block size does not align with end of boot memory, memory
hot-plugging/hot-removing ca
You should have a changelog.
On Tue, 2018-02-13 at 14:17 -0500, Mario Leinweber wrote:
[]
> diff --git a/mm/gup.c b/mm/gup.c
[]
> @@ -1635,7 +1640,7 @@ static int gup_pmd_range(pud_t pud, unsigned long addr,
> unsigned long end,
>PMD_SHIFT, next, write, pag
This patch was inspired by the discussion of this problem:
http://lkml.kernel.org/r/20180130083006.gb1...@in.ibm.com
Currently, during memory hotplugging we traverse struct pages several
times:
1. memset(0) in sparse_add_one_section()
2. loop in __add_section() to set do: set_page_node(page, nid)
801 - 900 of 1128 matches
Mail list logo
