From: Thomas Richter
The s390x CPU sampling and measurement facilities do not support perf
events of type PERF_TYPE_BREAKPOINT. The test cases are executed and
fail with -ENOENT due to missing hardware support.
Disable the execution of both test cases based on a
platform check. This is the same
From: Thomas Richter
Test case 21 (Number of exit events of a simple workload) fails on
s390x. The reason is the invalid sample frequency supplied for this
test. On s390x the minimum sample frequency is much higher (see output
of /proc/service_levels).
Supply a save sample frequency value for s3
From: Ingo Molnar
Remove this from check-headers.sh:
opts="--ignore-blank-lines --ignore-space-change"
as the easiest policy is to just follow the upstream UAPI header version 100%.
Pure space-only changes are comparatively rare.
Signed-off-by: Ingo Molnar
Cc: Adrian Hunter
Link: http://lk
These patches renames tools and cleanup messages
for x86 insn decoder according to Ingo's comment.
It is a kind of cleanup series of code. Just changes
meaningless command names to appropriate (or better)
one and does some cleanup including standarize
messages.
---
Masami Hiramatsu (3):
x86
Rename test_get_len test command to insn_decoder_test
as more meaningful name. This also changes some
comments in related files.
Note that this also removes the paragraph about
writing to the Free Software Foundation's mailing
address.
Signed-off-by: Masami Hiramatsu
---
arch/x86/tools/Makefile
Rename distill.awk to objdump_reformat.awk because
it actually re-format the output of objdump so that
insn_decoder_test can read it.
Signed-off-by: Masami Hiramatsu
---
arch/x86/tools/Makefile |4 +--
arch/x86/tools/distill.awk | 48 ---
Standardize warning, error, and success printout format
of insn_decode_test so that user can easily understand
which test tool caused the messages.
Signed-off-by: Masami Hiramatsu
---
arch/x86/tools/insn_decoder_test.c | 33 ++---
1 file changed, 22 insertions(+), 1
On Fri, Nov 24, 2017 at 02:49:34PM +0100, Vlastimil Babka wrote:
> On 11/24/2017 11:57 AM, Mel Gorman wrote:
> > On Thu, Nov 23, 2017 at 10:15:17PM +0100, Vlastimil Babka wrote:
> >> Hmm this really reads like about the migration scanner. That one is
> >> unchanged by this patch, there is still a l
On 11/21/2017, 04:08 PM, Ulf Hansson wrote:
> Subject: [PATCH] mmc: sdhci: Fix bounce buffer overflow
...
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
...
> @@ -3651,22 +3652,29 @@ int sdhci_setup_host(struct sdhci_host *host)
> spin_lock_init(&host->lock);
>
>
[ +Yonghong ]
On 11/24/2017 03:47 PM, Arnaldo Carvalho de Melo wrote:
> FYI, just noticed, recently updated clang to version 6, from its
> upstream git repo.
Do you recall what was your LLVM version prior to this where it was
working fine? (Wild guess from below would be the BPF inline asm
suppor
On 11/24/17 3:54 PM, Daniel Vetter wrote:
On Thu, Nov 23, 2017 at 03:24:38PM +0100, Tobias Klausmann wrote:
On 11/23/17 2:58 AM, Dave Airlie wrote:
On 23 November 2017 at 11:17, Laura Abbott wrote:
Hi,
Fedora QA testing reported a panic when booting up VMs
using qmeu vga drivers
(https://pa
On 24 November 2017 at 02:20, wrote:
> From: Rui Feng
>
> Because Realtek card reader drivers are pcie and usb drivers,
> and they bridge mmc subsystem and memstick subsystem, they are
> not mfd drivers. Greg and Lee Jones had a discussion about
> where to put the drivers, the result is that mis
On 24 November 2017 at 16:15, Jiri Slaby wrote:
> On 11/21/2017, 04:08 PM, Ulf Hansson wrote:
>> Subject: [PATCH] mmc: sdhci: Fix bounce buffer overflow
> ...
>> --- a/drivers/mmc/host/sdhci.c
>> +++ b/drivers/mmc/host/sdhci.c
> ...
>> @@ -3651,22 +3652,29 @@ int sdhci_setup_host(struct sdhci_host
On Fri, 24 Nov 2017, Ingo Molnar wrote:
> This is a linear series of patches of the latest entry-stack plus Kaiser
> bits from Andy Lutomirski (v3 series from today) and Dave Hansen
> (kaiser-414-tipwip-20171123 version), on top of latest tip:x86/urgent
> (12a78d43de76),
> plus fixes - for easier
Hi Lukasz,
Some minor comments below.
On 23 November 2017 at 20:39, Łukasz Stelmach wrote:
> Add support for True Random Number Generator found in Samsung Exynos
> 5250+ SoCs.
>
> Signed-off-by: Łukasz Stelmach
> ---
> MAINTAINERS | 7 +
> drivers/char/hw_random/Kcon
Hi Linus,
It doesn't seem useful to have the init_task in a header file rather than
in a normal source file. We could consolidate init_task handling instead.
Do want to do this? If so, this is probably something we'd want to do at
the end of the merge window, though not necessarily this one.
H
It's no longer necessary to have an INIT_TASK() macro, and this can be
unrolled into the one place it is now used.
Signed-off-by: David Howells
---
include/linux/init_task.h | 87 ++---
init/init_task.c | 85 ++
Construct the init thread stack in the linker script rather than doing it
by means of a union so that ia64's init_task.c can be got rid of.
The following symbols are then made available from INIT_TASK_DATA() linker
script macro:
init_thread_union
init_stack
INIT_TASK_DATA() also
Unroll various INIT_* macros into the single places they're used in
init/init_task.c.
Signed-off-by: David Howells
---
include/linux/ftrace.h| 12 -
include/linux/init_task.h | 112 -
include/linux/irqflags.h |2 -
include/linux/lockde
There doesn't seem to be any need to have the INIT_SIGNALS and INIT_SIGHAND
macros, so unroll them in their single places of use.
Signed-off-by: David Howells
---
include/linux/init_task.h | 43 ---
init/init_task.c | 30 +
Unroll INIT_STRUCT_PID in the single place that uses it. There doesn't
seem any point in the macro.
Signed-off-by: David Howells
---
include/linux/init_task.h | 15 ---
kernel/pid.c | 14 +-
2 files changed, 13 insertions(+), 16 deletions(-)
diff --git
Am 24.11.2017 um 16:17 schrieb Tobias Klausmann:
On 11/24/17 3:54 PM, Daniel Vetter wrote:
On Thu, Nov 23, 2017 at 03:24:38PM +0100, Tobias Klausmann wrote:
On 11/23/17 2:58 AM, Dave Airlie wrote:
On 23 November 2017 at 11:17, Laura Abbott wrote:
Hi,
Fedora QA testing reported a panic when
On Thu, 23 Nov 2017, Arnaldo Carvalho de Melo wrote:
Em Thu, Nov 23, 2017 at 12:09:48PM -0300, Arnaldo Carvalho de Melo escreveu:
Em Wed, Nov 22, 2017 at 06:25:28PM -0600, Kim Phillips escreveu:
> From: James Yang
>
> The "perf bench futex" benchmarks have a problem when not all CPUs in
> the
On Wed, Nov 22, 2017 at 08:38:30PM +0100, Stefano Manni wrote:
> sparse warning on lov_obd.c:
> warning: incorrect type in argument 3 (different signedness)
> expected int *res
> got unsigned int [usertype] *i
>
> sparse warning on lov_offset.c:
> warning: incorrect type in argument 4 (different s
2017-11-21 6:32 GMT+09:00 Jesse Chan :
> This change resolves a new compile-time warning
> when built as a loadable module:
>
> WARNING: modpost: missing MODULE_LICENSE() in
> drivers/mmc/host/renesas_sdhi_core.o
> see include/linux/module.h for more information
>
> This adds the license as "GPL v
On Mon, Oct 30, 2017 at 03:59:27PM +1100, NeilBrown wrote:
> Signed-off-by: NeilBrown
> ---
> drivers/staging/lustre/lustre/lov/lov_obd.c |6 ++
> 1 file changed, 2 insertions(+), 4 deletions(-)
I can't take patches with no changelog text at all, sorry.
greg k-h
On Fri 24-11-17 14:49:17, Andrea Reale wrote:
> Hi Rafael,
>
> On Fri 24 Nov 2017, 15:39, Rafael J. Wysocki wrote:
> > On Fri, Nov 24, 2017 at 11:22 AM, Andrea Reale
> > wrote:
> > > Resending the patch adding linux-acpi in CC, as suggested by Rafael.
> > > Everyone else: apologies for the noise
On 2017-11-24 14:54, Philippe CORNU wrote:
> Hi Peter,
>
> On 11/13/2017 11:40 AM, Philippe CORNU wrote:
>> Hi Peter,
>>
>> On 11/12/2017 01:31 PM, Peter Rosin wrote:
>>> On 2017-11-10 17:12, Philippe CORNU wrote:
Hi Peter,
On 11/07/2017 05:34 PM, Peter Rosin wrote:
> On 2017-11
On Mon, Oct 30, 2017 at 03:59:27PM +1100, NeilBrown wrote:
> There are mostly conversions of list_for_each() to
> list_for_each_entry() and similar. list_first_entry()
> also makes a few appearances.
I've taken the patches that had a changelog text.
thanks,
greg k-h
Hi Yury,
On Fri, Nov 24, 2017 at 3:30 PM, Yury Norov wrote:
> Below the updates proposed in this thread.
Thank you!
> From 959700bd7e7f586171c15a4130a9888acac02daf Mon Sep 17 00:00:00 2001
> From: Yury Norov
> Date: Wed, 22 Nov 2017 17:21:40 +0300
> Subject: [PATCH] improve lib/test_find_bit
>
On Fri, Nov 24, 2017 at 12:52 AM, Juergen Gross wrote:
> Sorry, Andy, forgot to Cc: you...
>
> On 24/11/17 09:42, Juergen Gross wrote:
>> Add early interrupt handlers activated by idt_setup_early_handler() to
>> the handlers supported by Xen pv guests. This will allow for early
>> WARN() calls not
Eric Biggers wrote:
> - construct_get_dest_keyring(&dest_keyring);
This will break. construct_get_dest_keyring() does other things than just
getting a ref on whatever dest_keyring points to.
David
On Sat, Nov 18, 2017 at 06:46:38PM +0100, Fabian Baumanis wrote:
> Removed uneccessary parantheses which were sorrounding two
> if-statements.
>
> Signed-off-by: Fabian Baumanis
> ---
> drivers/staging/comedi/drivers/adl_pci9118.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> di
On Wed 2017-11-08 10:27:23, Steven Rostedt wrote:
> Here's the design again:
>
> I added a "console_owner" which is set to a task that is actively
> writing to the consoles. It is *not* the same an the owner of the
> console_lock. It is only set when doing the calls to the console
> functions. It
On 24 November 2017 at 20:55, PrasannaKumar Muralidharan
wrote:
> Hi Lukasz,
>
> Some minor comments below.
>
> On 23 November 2017 at 20:39, Łukasz Stelmach wrote:
>> Add support for True Random Number Generator found in Samsung Exynos
>> 5250+ SoCs.
>>
>> Signed-off-by: Łukasz Stelmach
>> ---
On Fri 24 Nov 2017, 16:43, Michal Hocko wrote:
> On Fri 24-11-17 14:49:17, Andrea Reale wrote:
> > Hi Rafael,
> >
> > On Fri 24 Nov 2017, 15:39, Rafael J. Wysocki wrote:
> > > On Fri, Nov 24, 2017 at 11:22 AM, Andrea Reale
> > > wrote:
> > > > Resending the patch adding linux-acpi in CC, as sugg
On 11/24/2017 12:12 PM, Alessio Balsini wrote:
> Remove the adjective "relative" associated to the period of a periodic
> task, since the period is an absolute value.
>
> Rephrased the comment with the aim of making it even more clear.
>
> Signed-off-by: Alessio Balsini
> Cc: Ingo Molnar
> Cc:
On Fri 2017-11-24 16:54:16, Petr Mladek wrote:
> On Wed 2017-11-08 10:27:23, Steven Rostedt wrote:
> > If there is a waiter, then it breaks out of the loop, clears the waiter
> > flag (because that will release the waiter from its spin), and exits.
> > Note, it does *not* release the console semaph
On Wed, Nov 22, 2017 at 10:49:50AM +, Laurentiu Tudor wrote:
>
>
> On 11/22/2017 09:48 AM, Bharat Bhushan wrote:
> > As per APIs each mc-portal is of 64K size while currently
> > 16bits (type u16) is used to store size of mc-portal.
> > In these cases upper bit of portal size gets truncated.
Linus,
The following changes since commit cf9b0772f2e410645fece13b749bd56505b998b8:
Merge tag 'armsoc-drivers' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2017-11-16 16:05:01
-0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm tags/kv
Hi Greg,
> -Original Message-
> From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
> Sent: Friday, November 24, 2017 9:29 PM
> To: Laurentiu Tudor
> Cc: Bharat Bhushan ; Ruxandra Ioana Radulescu
> ; de...@driverdev.osuosl.org;
> stuyo...@gmail.com; Roy Pledge ; linux-
>
On Thu, Nov 23, 2017 at 02:38:12PM +, Charles Keepax wrote:
> On Fri, Nov 10, 2017 at 05:19:06PM +0530, Vinod Koul wrote:
> > MIPI Discovery And Configuration (DisCo) Specification for SoundWire
> > specifies properties to be implemented for SoundWire Masters and
> > Slaves. The DisCo spec doe
On Fri, Nov 24, 2017 at 5:47 AM, Peter Zijlstra wrote:
> On Fri, Nov 24, 2017 at 10:14:35AM +0100, Ingo Molnar wrote:
>> From: Dave Hansen
>>
>> There is some rather arcane code to help when an IRET returns
>> to 16-bit segments. It is referred to as the "espfix" code.
>> This consists of a few
On Fri, Nov 24, 2017 at 03:09:18PM +0100, Heiko Carstens wrote:
> On Fri, Nov 24, 2017 at 07:21:09AM +0200, Michael S. Tsirkin wrote:
> > The original intent of the virtio header relicensing
> > from 2008 was to make sure anyone can implement compatible
> > devices/drivers. The virtio-ccw was omitt
commit 7fb2b2d51 ("s390/virtio: remove the old KVM virtio transport")
dropped the transport support. We don't need to keep the header around.
Cc: Thomas Huth
Cc: Cornelia Huck
Cc: Halil Pasic
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Signed-off-by: Michael S. Tsirkin
---
No changes from v2
On Fri, Nov 24, 2017 at 10:09:54AM +0100, Cornelia Huck wrote:
> On Fri, 24 Nov 2017 07:21:09 +0200
> "Michael S. Tsirkin" wrote:
>
> > The original intent of the virtio header relicensing
> > from 2008 was to make sure anyone can implement compatible
> > devices/drivers. The virtio-ccw was omitt
The original intent of the virtio header relicensing
from 2008 was to make sure anyone can implement compatible
devices/drivers. The virtio-ccw was omitted by mistake.
We have an ack from the only contributor as well as the
maintainer from IBM, so it's not too late to fix that.
Make it dual-licen
I am working on this IP for Socionext SoCs.
I was hit by several issues, and noticed various
clean-up candidates.
- Fix and clean-up Kconfig
- Fix various card detection problems
- Move Renesas private data out of TMIO core
- Allow to perform platform-specific settings before MMC host starts
The TMIO mmc cannot detect the card insertion in native_hotplug mode
if the driver is probed without a card inserted.
The reason is obvious; all IRQs are disabled by tmio_mmc_host_probe(),
as follows:
tmio_mmc_disable_mmc_irqs(_host, TMIO_MASK_ALL);
The IRQs are first enabled by tmio_mmc_start
This driver was largely extended by Renesas, but actually used by
several SoC vendors. The current code does not work for UniPhier
SoCs at least.
The DMA mode for UniPhier SoCs failed with the following error message:
PIO IRQ in DMA mode!
For UniPhier SoCs, the TMIO_MASK_{READOP,WRITEOP} are a
Sane values for bus_shift are:
0 - for 16 bit bus
1 - for 32 bit bus
2 - for 64 bit bus
"unsigned long" is too much.
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Newly added
drivers/mmc/host/tmio_mmc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drive
struct tmio_mmc_dma looks like TMIO core data, but in fact, Renesas
private data. Move it to renesas_sdhi.h (probably, it is better to
rename it to renesas_sdhi_dma, or squash it into struct renesas_sdhi).
I also moved struct renesas_sdhi and host_to_priv() to that header
because they are necessa
TMIO_MASK_CMD is properly enabled in tmio_mmc_start_command().
We have no reason to set it up in tmio_mmc_host_probe(). (If we
really wanted to set it in the probe, we would have to do likewise
when resuming.)
Even worse, the following code is extremely confusing:
_host->sdcard_irq_mask &= ~i
On Fri, Nov 24, 2017 at 5:16 AM, Andrey Ryabinin
wrote:
>
>
> On 11/24/2017 07:32 AM, Andy Lutomirski wrote:
>> The cpu_entry_area will contain stacks. Make sure that KASAN has
>> appropriate shadow mappings for them.
>>
>> Cc: Andrey Ryabinin
>> Cc: Alexander Potapenko
>> Cc: Dmitry Vyukov
>>
mmc_of_parse() parses various DT properties and sets capability flags
accordingly. However, drivers have no chance to run platform init
code depending on such flags because mmc_of_parse() is called from
tmio_mmc_host_probe().
Move mmc_of_parse() to tmio_mmc_host_alloc() so that drivers can
handle
Drivers need to set up various struct members for tmio_mmc_host before
calling tmio_mmc_host_probe(). Do likewise for host->dma_ops instead
of passing it as a function argument.
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Newly added
drivers/mmc/host/renesas_sdhi_core.c | 3 ++-
dri
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
On 11/24/17 4:35 PM, Christian König wrote:
Am 24.11.2017 um 16:17 schrieb Tobias Klausmann:
On 11/24/17 3:54 PM, Daniel Vetter wrote:
On Thu, Nov 23, 2017 at 03:24:38PM +0100, Tobias Klausmann wrote:
On 11/23/17 2:58 AM, Dave Airlie wrote:
On 23 November 2017 at 11:17, Laura Abbott
wrote:
Hi Fengguang,
Fengguang Wu writes:
> It looks linus/master and linux-next still has this issue.
I sent a fix to net-next before it closes but it hasn't been picked.
Now that it's in the net tree, I'm sending an alternative fix right now.
Thank for the note!
Vivien
The clock is enabled in the tmio_mmc_host_probe(). It also prevents
drivers from performing platform-specific settings before mmc_add_host()
because the register access generally requires a clock.
Enable/disable the clock in drivers' probe/remove. Also, I passed
tmio_mmc_data to tmio_mmc_host_al
The register region is ioremap'ed in the tmio_mmc_host_probe(), i.e.
drivers cannot get access to the hardware before mmc_add_host().
Actually, renesas_sdhi_core.c reads out the CTL_VERSION register to
complete the platform-specific settings. However, at this point,
the MMC host is already runnin
struct tmio_mmc_host has "dma_dataend" and "dma_complete", but in fact,
they are Renesas private data. Move them to renesas_sdhi.h
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Newly added
drivers/mmc/host/renesas_sdhi.h | 2 ++
drivers/mmc/host/renesas_sdhi_internal_dm
struct tmio_mmc_host has "scc_tappos", but in fact, it is Renesas
private data. Move it to renesas_sdhi.h
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Newly added
drivers/mmc/host/renesas_sdhi.h | 1 +
drivers/mmc/host/renesas_sdhi_core.c | 4 ++--
drivers/mmc/host/tmio_mmc.h
renesas_sdhi_probe() always sets host->dma as follows:
host->dma = dma_priv;
!host->dma is always false.
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Newly added
drivers/mmc/host/renesas_sdhi_sys_dmac.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Currently, tmio_mmc_ops is static data and tmio_mmc_host_probe()
updates some hooks in the static data. This is a problem when
two or more instances call tmio_mmc_host_probe() and each of them
requests to use its own card_busy/start_signal_voltage_switch.
We can borrow a solution from sdhci_alloc
To use a GPIO line for card detection, TMIO_MMC_USE_GPIO_CD is set
by a legacy board (arch/sh/boards/mach-ecovec24).
For DT platforms, the "cd-gpios" property is a legitimate way for that
in case the IP-builtin card detection can not be used for some reason.
mmc_of_parse() calls mmc_gpiod_request_
A card detect GPIO is set up only for platforms with "cd-gpios"
DT property or TMIO_MMC_USE_GPIO_CD flag. However, the driver
core always uses mmc_gpio_get_cd, which just fails with -ENOSYS
if ctx->cd_gpio is unset.
The bit 5 of the status register provides the current signal level
of the CD line
The description in the Makefile is odd. Fix the CONFIG selection
in a cleaner way.
Signed-off-by: Masahiro Yamada
Acked-by: Wolfram Sang
---
Changes in v2:
- Fix a typo consilidate -> consolidate
drivers/mmc/host/Kconfig | 4 ++--
drivers/mmc/host/Makefile | 8 ++--
2 files changed, 4
ARCH_RENESAS is a stronger condition than (ARM || ARM64).
If ARCH_RENESAS is enabled, (ARM || ARM64) is met as well.
What is worse, the first depends on line prevents COMPILE_TEST from
enabling this driver. It should be removed.
Signed-off-by: Masahiro Yamada
Acked-by: Wolfram Sang
---
Change
The remove, suspend, resume hooks need to get tmio_mmc_host. It is
tedious to call mmc_priv() to convert mmc_host to tmio_mmc_host.
We can directly set tmio_mmc_host to driver data.
Signed-off-by: Masahiro Yamada
Acked-by: Wolfram Sang
---
Changes in v2: None
drivers/mmc/host/renesas_sdhi_co
Drivers can set any mmc_host_ops hooks between tmio_mmc_host_alloc()
and tmio_mmc_host_probe(). Remove duplicated hooks in tmio_mmc_host.
Signed-off-by: Masahiro Yamada
Reviewed-by: Wolfram Sang
Tested-by: Wolfram Sang
---
Changes in v2:
- Rename "mmc_host_ops" to "ops" per Wolfram Sang
d
The TMIO core misses to call request_mem_region().
devm_ioremap_resource() takes care of it and makes the code cleaner.
Signed-off-by: Masahiro Yamada
Reviewed-by: Wolfram Sang
Tested-by: Wolfram Sang
---
Changes in v2: None
drivers/mmc/host/tmio_mmc_core.c | 10 +++---
1 file changed, 3
"goto eprobe" does nothing. Return directly.
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Fix a typo : renesas_sdhc -> renesas_sdhi
- Restore the "ret" printout for devm_clk_get()
drivers/mmc/host/renesas_sdhi_core.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
Drivers do not need to call mmc_gpiod_request_cd_irq() explicitly
because mmc_start_host() calls it. To make it work, cd_gpio must
be set before mmc_add_host().
Signed-off-by: Masahiro Yamada
---
Changes in v2: None
drivers/mmc/host/tmio_mmc_core.c | 14 ++
1 file changed, 6 inser
On 11/24/2017 04:16 AM, Peter Zijlstra wrote:
> On Fri, Nov 24, 2017 at 10:14:30AM +0100, Ingo Molnar wrote:
>> +The minimalistic kernel portion of the user page tables try to
>> +map only what is needed to enter/exit the kernel such as the
>> +entry/exit functions themselves and the interrupt desc
Setting the refcount to 0 when allocating a tree to match the number of
switch devices it holds may cause an 'increment on 0; use-after-free',
if CONFIG_REFCOUNT_FULL is enabled.
To fix this, do not decrement the refcount of a newly allocated tree,
increment it when an already allocated tree is fo
Am 24.11.2017 um 17:29 schrieb Tobias Klausmann:
On 11/24/17 4:35 PM, Christian König wrote:
Am 24.11.2017 um 16:17 schrieb Tobias Klausmann:
On 11/24/17 3:54 PM, Daniel Vetter wrote:
On Thu, Nov 23, 2017 at 03:24:38PM +0100, Tobias Klausmann wrote:
On 11/23/17 2:58 AM, Dave Airlie wrote:
O
Hello Matthew.
Matthew Wilcox - 24.11.17, 02:16:
> ==
> XArray
> ==
>
> Overview
>
>
> The XArray is an array of ULONG_MAX entries. Each entry can be either
> a pointer, or an encoded value between 0 and LONG_MAX. It is efficient
> when the indices used are densely clustered;
> We checked old kernels, and old e2fsprogs, and didn't see any cases
> where fast (<= 60 chars) symlinks were created using external blocks.
> It seems that _something_ did create them, and it would be good to
> figure that out so we can determine if it is a widespread problem
I assume it was the
On Fri, Nov 24, 2017 at 06:21:11PM +0200, Michael S. Tsirkin wrote:
> On Fri, Nov 24, 2017 at 03:09:18PM +0100, Heiko Carstens wrote:
> > On Fri, Nov 24, 2017 at 07:21:09AM +0200, Michael S. Tsirkin wrote:
> > > The original intent of the virtio header relicensing
> > > from 2008 was to make sure a
This adds the partitions definition for the SPI NOR to provide
backward compatibility with the documented[1] layout used with
Boundary Devices BSP.
1. https://boundarydevices.com/boot-flash-access-linux/
It exports to Linux:
mtd0: bootloader
mtd1: env
mtd2: splash
Signed-off-by: Otavio Salva
Hi Linus,
Please pull a little more Kbuild updates for v4.15.
The reason for lateness is I hesitated to put some patches
in the last week pull requests due to big conflicts.
Also, I applied some fixes and trivial enough ones.
I hope you will pull this.
The following changes since commit 2ce079f
The platform_get_irq_byname() function returns -1 if an error occurs.
zero or positive number on success. platform_get_irq_byname() error
checking for zero is not correct.
Signed-off-by: Arvind Yadav
---
drivers/power/supply/cpcap-battery.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(
On Fri, Nov 24, 2017 at 05:53:01PM +0100, Heiko Carstens wrote:
> > > Is there any reason to add the whole BSD 3 clause license text? I'd prefer
> > > if it would be just the simple new SPDX-License-Identifier above.
I added it for consistency with other virtio headers.
--
MST
On Fri, Nov 24, 2017 at 05:50:41PM +0100, Martin Steigerwald wrote:
> Matthew Wilcox - 24.11.17, 02:16:
> > ==
> > XArray
> > ==
> >
> > Overview
> >
> >
> > The XArray is an array of ULONG_MAX entries. Each entry can be either
> > a pointer, or an encoded value between 0 and LO
On 11/22/17 5:30 PM, Solio Sarabia wrote:
> The netdevice gso_max_size is exposed to allow users fine-control on
> systems with multiple NICs with different GSO buffer sizes, and where
> the virtual devices like bridge and veth, need to be aware of the GSO
> size of the underlying devices.
>
> In
On Thu, Nov 23, 2017 at 09:30:21PM -0700, Andreas Dilger wrote:
> > Pointers to be stored in the XArray must have the bottom two bits clear
> > (ie must point to something which is 4-byte aligned). This includes all
> > objects allocated by calling :c:func:`kmalloc` and :c:func:`alloc_page`,
> > b
From: Andy Lutomirski
The cpu_entry_area will contain stacks. Make sure that KASAN has
appropriate shadow mappings for them.
Cc: Alexander Potapenko
Cc: Dmitry Vyukov
Cc: kasan-...@googlegroups.com
Signed-off-by: Andy Lutomirski
Signed-off-by: Andrey Ryabinin
---
arch/x86/mm/kasan_init_64.
On Fri, Nov 24, 2017 at 07:02:41PM +0200, Michael S. Tsirkin wrote:
> On Fri, Nov 24, 2017 at 05:53:01PM +0100, Heiko Carstens wrote:
> > > > Is there any reason to add the whole BSD 3 clause license text? I'd
> > > > prefer
> > > > if it would be just the simple new SPDX-License-Identifier above.
* Thomas Gleixner wrote:
> On Fri, 24 Nov 2017, Ingo Molnar wrote:
>
> > This is a linear series of patches of the latest entry-stack plus Kaiser
> > bits from Andy Lutomirski (v3 series from today) and Dave Hansen
> > (kaiser-414-tipwip-20171123 version), on top of latest tip:x86/urgent
> > (
On 11/24/2017 07:27 PM, Andy Lutomirski wrote:
>>> + cpu_entry_area_begin = (void
>>> *)(__fix_to_virt(FIX_CPU_ENTRY_AREA_BOTTOM));
>>> + cpu_entry_area_end = (void *)(__fix_to_virt(FIX_CPU_ENTRY_AREA_TOP) +
>>> PAGE_SIZE);
>>> +
>>> kasan_populate_zero_shadow(kasan_mem_to_shadow((
From: Andy Lutomirski
Historically, IDT entries from usermode have always gone directly
to the running task's kernel stack. Rearrange it so that we enter on
a percpu trampoline stack and then manually switch to the task's stack.
This touches a couple of extra cachelines, but it gives us a chance
From: Andy Lutomirski
That race has been fixed and code cleaned up for a while now.
Signed-off-by: Andy Lutomirski
Signed-off-by: Thomas Gleixner
Cc: Borislav Petkov
Cc: Brian Gerst
Cc: Dave Hansen
Cc: Josh Poimboeuf
Cc: Linus Torvalds
Cc: Peter Zijlstra
Link:
https://lkml.kernel.org/r/
This is a repost of the latest entry-stack plus Kaiser bits from Andy Lutomirski
(v3 series from today) and Dave Hansen (kaiser-414-tipwip-20171123 version),
on top of latest tip:x86/urgent (12a78d43de76).
This version is pretty well tested, at least on the usual x86 tree test systems.
It has a co
From: Andy Lutomirski
The existing code was a mess, mainly because C arrays are nasty.
Turn SYSENTER_stack into a struct, add a helper to find it, and do
all the obvious cleanups this enables.
Signed-off-by: Andy Lutomirski
Signed-off-by: Thomas Gleixner
Cc: Borislav Petkov
Cc: Brian Gerst
C
From: Dave Hansen
Normally, a process has a NULL mm->context.ldt. But, there is a
syscall for a process to set a new one. If a process does that,
the LDT be mapped into the user page tables, just like the
default copy.
The original KAISER patch missed this case.
Signed-off-by: Dave Hansen
Si
From: Dave Hansen
These patches are based on work from a team at Graz University of
Technology: https://github.com/IAIK/KAISER . This work would not have
been possible without their work as a starting point.
KAISER is a countermeasure against side channel attacks against kernel
virtual memory.
301 - 400 of 537 matches
Mail list logo
