On 13/11/2018 17:51, Bo Yan wrote:
> The function tegra_read_chipid is declared twice in fuse.h. Remove
> the redundant declaration.
>
> Signed-off-by: Bo Yan
> ---
> include/soc/tegra/fuse.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/soc/tegra/fuse.h
On 13/11/2018 17:51, Bo Yan wrote:
> The function tegra_read_chipid is declared twice in fuse.h. Remove
> the redundant declaration.
>
> Signed-off-by: Bo Yan
> ---
> include/soc/tegra/fuse.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/soc/tegra/fuse.h
Hi Vesa,
On 11/13/2018 08:10 AM, Vesa Jääskeläinen wrote:
> Hi Jacek,
>
> On 12/11/2018 18.02, Jacek Anaszewski wrote:
Support for RGB LEDs, or other variations of LED synchronization
have been approached several times, but without satisfying result
so far.
Generally the
Take a look at the patch I merged, and please follow up with any patch
to fixup any issue you find with it.
As mentioned in my original email, I tried to consolidate the two
versions, so a look-through and follow up with fixes would be
appreciated. Thanks!
-Olof
On Tue, Nov 13, 2018 at 2:17 AM
Hi Vesa,
On 11/13/2018 08:10 AM, Vesa Jääskeläinen wrote:
> Hi Jacek,
>
> On 12/11/2018 18.02, Jacek Anaszewski wrote:
Support for RGB LEDs, or other variations of LED synchronization
have been approached several times, but without satisfying result
so far.
Generally the
Take a look at the patch I merged, and please follow up with any patch
to fixup any issue you find with it.
As mentioned in my original email, I tried to consolidate the two
versions, so a look-through and follow up with fixes would be
appreciated. Thanks!
-Olof
On Tue, Nov 13, 2018 at 2:17 AM
On Tue, 2018-11-13 at 19:29 +0200, Andy Shevchenko wrote:
> On Tue, Nov 13, 2018 at 11:55:32AM -0500, Qian Cai wrote:
>
> +Cc Rasmus
>
> > Running the trinity fuzzer with a non-root user on an aarch64 server with
> > the
> > latest mainline (rc2) generated this. Is it just a false alarm to
On Tue, 2018-11-13 at 19:29 +0200, Andy Shevchenko wrote:
> On Tue, Nov 13, 2018 at 11:55:32AM -0500, Qian Cai wrote:
>
> +Cc Rasmus
>
> > Running the trinity fuzzer with a non-root user on an aarch64 server with
> > the
> > latest mainline (rc2) generated this. Is it just a false alarm to
On Mon, Nov 12, 2018 at 06:47:08AM +, Clark Wang wrote:
This looks fine so I'll apply it but it would have been easier to review
if it were split up a bit. There's mechanical changes like:
> -static int lpspi_prepare_xfer_hardware(struct spi_master *master)
> +static int
On Mon, Nov 12, 2018 at 06:47:08AM +, Clark Wang wrote:
This looks fine so I'll apply it but it would have been easier to review
if it were split up a bit. There's mechanical changes like:
> -static int lpspi_prepare_xfer_hardware(struct spi_master *master)
> +static int
On Tue, Nov 13, 2018 at 7:32 PM Takashi Iwai wrote:
> On Sun, 11 Nov 2018 20:02:45 +0100,
> Ayman Bagabas wrote:
> With that fix,
> Reviewed-by: Takashi Iwai
Ayman, please, send next version with requested changes and appended
tags. I will apply it.
--
With Best Regards,
Andy Shevchenko
On Tue, Nov 13, 2018 at 7:32 PM Takashi Iwai wrote:
> On Sun, 11 Nov 2018 20:02:45 +0100,
> Ayman Bagabas wrote:
> With that fix,
> Reviewed-by: Takashi Iwai
Ayman, please, send next version with requested changes and appended
tags. I will apply it.
--
With Best Regards,
Andy Shevchenko
On 11/11/2018 9:17 PM, Keerthy wrote:
Add PRCM int16 as the wake up source.
Signed-off-by: Keerthy
---
Looks good.
Tony, Would you able to pick this up ?
On 11/11/2018 9:17 PM, Keerthy wrote:
Add PRCM int16 as the wake up source.
Signed-off-by: Keerthy
---
Looks good.
Tony, Would you able to pick this up ?
Create a separate reset driver that uses the reset operations in
reset-simple. The reset driver for the SoCFPGA platform needs to
register early in order to be able bring online timers that needed
early in the kernel bootup.
We do not need this early reset driver for Stratix10, because on
arm64,
Create a separate reset driver that uses the reset operations in
reset-simple. The reset driver for the SoCFPGA platform needs to
register early in order to be able bring online timers that needed
early in the kernel bootup.
We do not need this early reset driver for Stratix10, because on
arm64,
From: Michal Hocko
Swap storage is restricted to max_swapfile_size (~16TB on x86_64)
whenever the system is deemed affected by L1TF vulnerability. Even
though the limit is quite high for most deployments it seems to be
too restrictive for deployments which are willing to live with the
mitigation
From: Michal Hocko
Swap storage is restricted to max_swapfile_size (~16TB on x86_64)
whenever the system is deemed affected by L1TF vulnerability. Even
though the limit is quite high for most deployments it seems to be
too restrictive for deployments which are willing to live with the
mitigation
On Mon, Nov 12, 2018 at 06:08:17PM -0800, Tejun Heo wrote:
> (cc'ing Linus, Andrew, Ingo for the addition of a new task state)
>
> Hello,
>
> On Mon, Nov 12, 2018 at 03:04:19PM -0800, Roman Gushchin wrote:
> > Cgroup v1 implements the freezer controller, which provides an ability
> > to stop the
On Mon, Nov 12, 2018 at 06:08:17PM -0800, Tejun Heo wrote:
> (cc'ing Linus, Andrew, Ingo for the addition of a new task state)
>
> Hello,
>
> On Mon, Nov 12, 2018 at 03:04:19PM -0800, Roman Gushchin wrote:
> > Cgroup v1 implements the freezer controller, which provides an ability
> > to stop the
Remove @flags from tpm_transmit() API. It is no longer used for
anything.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-chip.c | 32 ++---
drivers/char/tpm/tpm-dev-common.c | 2 +-
drivers/char/tpm/tpm-interface.c | 18
drivers/char/tpm/tpm-sysfs.c
Remove @flags from tpm_transmit() API. It is no longer used for
anything.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-chip.c | 32 ++---
drivers/char/tpm/tpm-dev-common.c | 2 +-
drivers/char/tpm/tpm-interface.c | 18
drivers/char/tpm/tpm-sysfs.c
Call tpm_chip_start() and tpm_chip_stop() in
* tpm_try_get_ops() and tpm_put_ops()
* tpm_chip_register()
* tpm2_del_space()
And remove these calls from tpm_transmit(). The core reason for this
change is that in tpm_vtpm_proxy a locality change requires a virtual
TPM command (a command made up
Use tpm_try_get_ops() in tpm-sysfs.c so that we can consider moving
other decorations (locking, localities, power management for example)
inside it. This direction can be of course taken only after other call
sites for tpm_transmit() have been treated in the same way.
Signed-off-by: Jarkko
Encapsulate power gating and locality functionality to tpm_chip_start()
and tpm_chip_stop() in order to clean up the branching mess in
tpm_transmit().
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-chip.c | 110 +++
drivers/char/tpm/tpm-interface.c |
Added locking as part of tpm_try_get_ops() and tpm_put_ops() as they are
anyway used in most of the call sites except in tpmrm_release() where we
take the locks manually.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-chip.c | 2 ++
drivers/char/tpm/tpm-dev-common.c | 4 +---
Call tpm_chip_start() and tpm_chip_stop() in
* tpm_try_get_ops() and tpm_put_ops()
* tpm_chip_register()
* tpm2_del_space()
And remove these calls from tpm_transmit(). The core reason for this
change is that in tpm_vtpm_proxy a locality change requires a virtual
TPM command (a command made up
Use tpm_try_get_ops() in tpm-sysfs.c so that we can consider moving
other decorations (locking, localities, power management for example)
inside it. This direction can be of course taken only after other call
sites for tpm_transmit() have been treated in the same way.
Signed-off-by: Jarkko
Encapsulate power gating and locality functionality to tpm_chip_start()
and tpm_chip_stop() in order to clean up the branching mess in
tpm_transmit().
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-chip.c | 110 +++
drivers/char/tpm/tpm-interface.c |
Added locking as part of tpm_try_get_ops() and tpm_put_ops() as they are
anyway used in most of the call sites except in tpmrm_release() where we
take the locks manually.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-chip.c | 2 ++
drivers/char/tpm/tpm-dev-common.c | 4 +---
Remove @space from tpm_transmit() API` in order to completely remove the
bound between low-level transmission functionality and TPM spaces. The
only real dependency existing is the amount of data saved before trying
to send a command to the TPM.
It doesn't really matter if we save always a bit
Prepare and commit TPM space before and after calling tpm_transmit()
instead of doing that inside tpm_transmit(). After this change we can
remove TPM_TRANSMIT_NESTED flag from tpm2_prepare_space() and
tpm2_commit_space() and replace it with TPM_TRANSMIT_UNLOCKED.
Cc: James Bottomley
Remove @space from tpm_transmit() API` in order to completely remove the
bound between low-level transmission functionality and TPM spaces. The
only real dependency existing is the amount of data saved before trying
to send a command to the TPM.
It doesn't really matter if we save always a bit
Prepare and commit TPM space before and after calling tpm_transmit()
instead of doing that inside tpm_transmit(). After this change we can
remove TPM_TRANSMIT_NESTED flag from tpm2_prepare_space() and
tpm2_commit_space() and replace it with TPM_TRANSMIT_UNLOCKED.
Cc: James Bottomley
Instead of accessing fields of the command header through offsets to
the raw buffer, it is a better idea to use the header struct pointer
that is already used elsewhere in the function.
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-interface.c | 4 ++--
1
Move tpm_validate_command() to tpm2-space.c and make it part of the
tpm2_prepare_space() flow. Make cc resolution as part of the TPM space
functionality in order to detach it from rest of the tpm_transmit()
flow.
Cc: James Bottomley
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
Instead of accessing fields of the command header through offsets to
the raw buffer, it is a better idea to use the header struct pointer
that is already used elsewhere in the function.
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-interface.c | 4 ++--
1
Move tpm_validate_command() to tpm2-space.c and make it part of the
tpm2_prepare_space() flow. Make cc resolution as part of the TPM space
functionality in order to detach it from rest of the tpm_transmit()
flow.
Cc: James Bottomley
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
Move locking, locality handling and power management to tpm_transmit()
in order to simplify the flow.
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-interface.c | 71
1 file changed, 35 insertions(+), 36 deletions(-)
diff
Always call tpm2_flush_space() on failure in tpm_try_transmit() so that
the volatile memory of the TPM gets cleared. If /dev/tpm0 does not have
sufficient permissions (usually it has), this could lead to the leakage
of TPM objects. Through /dev/tpmrm0 this issue does not raise any new
security
Encapsulate tpm_transmit() call pattern to tpm_dev_transmit() because it
is identically used from two places. Use unlocked version of
tpm_transmit() so that we are able to move the calls to
tpm2_prepare_space() and tpm2_commit_space() later on to this new
function.
Signed-off-by: Jarkko Sakkinen
Always call tpm2_flush_space() on failure in tpm_try_transmit() so that
the volatile memory of the TPM gets cleared. If /dev/tpm0 does not have
sufficient permissions (usually it has), this could lead to the leakage
of TPM objects. Through /dev/tpmrm0 this issue does not raise any new
security
Encapsulate tpm_transmit() call pattern to tpm_dev_transmit() because it
is identically used from two places. Use unlocked version of
tpm_transmit() so that we are able to move the calls to
tpm2_prepare_space() and tpm2_commit_space() later on to this new
function.
Signed-off-by: Jarkko Sakkinen
Move locking, locality handling and power management to tpm_transmit()
in order to simplify the flow.
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-interface.c | 71
1 file changed, 35 insertions(+), 36 deletions(-)
diff
Decleare struct tpm_header that replaces struct tpm_input_header and
struct tpm_output_header.
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-interface.c | 9 -
drivers/char/tpm/tpm.h| 27 ---
On Tue, Nov 13, 2018 at 10:33 AM Igor Stoppa wrote:
>
> I forgot one sentence :-(
>
> On 13/11/2018 20:31, Igor Stoppa wrote:
> > On 13/11/2018 19:47, Andy Lutomirski wrote:
> >
> >> For general rare-writish stuff, I don't think we want IRQs running
> >> with them mapped anywhere for write. For
The error logging for tpm2_commit_space() is in a wrong place. This
commit moves it inside that function.
Cc: James Bottomley
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-interface.c | 2 --
drivers/char/tpm/tpm2-space.c| 9 ++---
2 files changed,
Decleare struct tpm_header that replaces struct tpm_input_header and
struct tpm_output_header.
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-interface.c | 9 -
drivers/char/tpm/tpm.h| 27 ---
On Tue, Nov 13, 2018 at 10:33 AM Igor Stoppa wrote:
>
> I forgot one sentence :-(
>
> On 13/11/2018 20:31, Igor Stoppa wrote:
> > On 13/11/2018 19:47, Andy Lutomirski wrote:
> >
> >> For general rare-writish stuff, I don't think we want IRQs running
> >> with them mapped anywhere for write. For
The error logging for tpm2_commit_space() is in a wrong place. This
commit moves it inside that function.
Cc: James Bottomley
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-interface.c | 2 --
drivers/char/tpm/tpm2-space.c| 9 ++---
2 files changed,
Do not print partial list of PCRs when tpm1_pcr_read() fails but instead
return 0 from pcrs_show(). This is consistent behavior with other sysfs
functions.
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-sysfs.c | 13 ++---
1 file changed, 6
Do not print partial list of PCRs when tpm1_pcr_read() fails but instead
return 0 from pcrs_show(). This is consistent behavior with other sysfs
functions.
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-sysfs.c | 13 ++---
1 file changed, 6
[was Detach TPM space code out of the tpm_transmit() flow but the scope
expanded a bit.]
Make the changes necessary to detach TPM space code and TPM activation
code out of the tpm_transmit() flow because of both of these can cause
nested tpm_transmit() calls. The nesteds calls make the whole
[was Detach TPM space code out of the tpm_transmit() flow but the scope
expanded a bit.]
Make the changes necessary to detach TPM space code and TPM activation
code out of the tpm_transmit() flow because of both of these can cause
nested tpm_transmit() calls. The nesteds calls make the whole
Return zero when tpm_buf_init() fails as we do for other functions in
tpm-sysfs.c.
Fixes: da379f3c1db0c ("tpm: migrate pubek_show to struct tpm_buf")
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-sysfs.c | 5 ++---
1 file changed, 2 insertions(+), 3
Since we pass an initialized struct tpm_buf instance in every call site
now, it is cleaner to pass that directly to the tpm_transmit_cmd() as
the TPM command/response buffer.
Fine-tune a little bit tpm_transmit() and tpm_transmit_cmd() comments
while doing this.
Signed-off-by: Jarkko Sakkinen
Return zero when tpm_buf_init() fails as we do for other functions in
tpm-sysfs.c.
Fixes: da379f3c1db0c ("tpm: migrate pubek_show to struct tpm_buf")
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
---
drivers/char/tpm/tpm-sysfs.c | 5 ++---
1 file changed, 2 insertions(+), 3
Since we pass an initialized struct tpm_buf instance in every call site
now, it is cleaner to pass that directly to the tpm_transmit_cmd() as
the TPM command/response buffer.
Fine-tune a little bit tpm_transmit() and tpm_transmit_cmd() comments
while doing this.
Signed-off-by: Jarkko Sakkinen
The patch
spi: Deal with slaves that return from transfer_one() unfinished
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
spi: Deal with slaves that return from transfer_one() unfinished
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
On Mon, Nov 12, 2018 at 03:27:36PM +0100, Emil Renner Berthing wrote:
> I know the discussions about the sifive devicetree compatible
> strings haven't come to a conclusion, so I'm sending this as
> an RFC to get some feedback on the rest of the code.
I've not seen any of these discussions or
On Mon, Nov 12, 2018 at 03:27:36PM +0100, Emil Renner Berthing wrote:
> I know the discussions about the sifive devicetree compatible
> strings haven't come to a conclusion, so I'm sending this as
> an RFC to get some feedback on the rest of the code.
I've not seen any of these discussions or
The patch
spi: pxa2xx: Add ready signal
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the
The patch
spi: pxa2xx: Add ready signal
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the
The patch
spi: pxa2xx: dt-bindings: Add ready GPIO signal
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
spi: pxa2xx: dt-bindings: Add ready GPIO signal
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
From: Nadav Amit
Sent: November 13, 2018 at 5:55:34 PM GMT
> To: Ingo Molnar
> Cc: Ingo Molnar , Masahiro Yamada
> , Michal Marek ,
> Thomas Gleixner , Borislav Petkov , H.
> Peter Anvin , X86 ML , Linux Kbuild mailing
> list , LKML ,
> Logan Gunthorpe
> Subject: Re: [PATCH 1/2] Makefile:
From: Nadav Amit
Sent: November 13, 2018 at 5:55:34 PM GMT
> To: Ingo Molnar
> Cc: Ingo Molnar , Masahiro Yamada
> , Michal Marek ,
> Thomas Gleixner , Borislav Petkov , H.
> Peter Anvin , X86 ML , Linux Kbuild mailing
> list , LKML ,
> Logan Gunthorpe
> Subject: Re: [PATCH 1/2] Makefile:
Hi Alexander,
On Tue, Nov 13, 2018 at 12:36 AM Alexander Kapshuk
wrote:
>
> On Tue, Nov 13, 2018 at 2:09 AM Brian Norris wrote:
> >
> > On Mon, Nov 12, 2018 at 10:42:26AM +0200, Alexander Kapshuk wrote:
> > > An even simpler approach would be:
> > >
> > > {
> > > git --no-optional-locks
Hi Alexander,
On Tue, Nov 13, 2018 at 12:36 AM Alexander Kapshuk
wrote:
>
> On Tue, Nov 13, 2018 at 2:09 AM Brian Norris wrote:
> >
> > On Mon, Nov 12, 2018 at 10:42:26AM +0200, Alexander Kapshuk wrote:
> > > An even simpler approach would be:
> > >
> > > {
> > > git --no-optional-locks
The patch
ASoC: rockchip: add missing slave_config setting for I2S
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: rockchip: add missing slave_config setting for I2S
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: wm_adsp: Factor out common init code
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
ASoC: wm_adsp: Factor out common init code
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
ASoC: wm_adsp: Fix dma-unsafe read of scratch registers
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: wm_adsp: Fix dma-unsafe read of scratch registers
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
On 11/12/18 10:55 AM, David Laight wrote:
> From: Vlastimil Babka [mailto:vba...@suse.cz]
>> Sent: 09 November 2018 19:16
> ...
>> This? Not terribly elegant, but I don't see a nicer way right now...
>
> Maybe just have two copies of the function body?
>
> static __always_inline enum
On 13/11/2018 19:16, Andy Lutomirski wrote:
> On Tue, Nov 13, 2018 at 6:25 AM Igor Stoppa wrote:
[...]
>> How about having one mm_struct for each writer (core or thread)?
>>
>
> I don't think that helps anything. I think the mm_struct used for
> prmem (or rare_write or whatever you want to
On 11/12/18 10:55 AM, David Laight wrote:
> From: Vlastimil Babka [mailto:vba...@suse.cz]
>> Sent: 09 November 2018 19:16
> ...
>> This? Not terribly elegant, but I don't see a nicer way right now...
>
> Maybe just have two copies of the function body?
>
> static __always_inline enum
On 13/11/2018 19:16, Andy Lutomirski wrote:
> On Tue, Nov 13, 2018 at 6:25 AM Igor Stoppa wrote:
[...]
>> How about having one mm_struct for each writer (core or thread)?
>>
>
> I don't think that helps anything. I think the mm_struct used for
> prmem (or rare_write or whatever you want to
On Tue, 13 Nov 2018 00:08:48 +0300
Alexander Popov wrote:
> The stackleak_erase() function is called on the trampoline stack at the end
> of syscall. This stack is not big enough for ftrace and kprobes operations,
> e.g. it can be exhausted if we use kprobe_events for stackleak_erase().
>
> So
On Tue, 13 Nov 2018 00:08:48 +0300
Alexander Popov wrote:
> The stackleak_erase() function is called on the trampoline stack at the end
> of syscall. This stack is not big enough for ftrace and kprobes operations,
> e.g. it can be exhausted if we use kprobe_events for stackleak_erase().
>
> So
On Mon, 12 Nov 2018 12:21:48 -0500
Steven Rostedt wrote:
> On Mon, 12 Nov 2018 19:51:00 +0300
> Alexander Popov wrote:
>
> > By the way, are there any other tracing/instrumentation mechanisms that
> > should
> > be disabled?
>
> ftrace and kprobes are pretty much the only ones that currently
On Mon, 12 Nov 2018 12:21:48 -0500
Steven Rostedt wrote:
> On Mon, 12 Nov 2018 19:51:00 +0300
> Alexander Popov wrote:
>
> > By the way, are there any other tracing/instrumentation mechanisms that
> > should
> > be disabled?
>
> ftrace and kprobes are pretty much the only ones that currently
On Mon, Nov 12, 2018 at 04:15:09PM +0100, Johan Hovold wrote:
> On Fri, Nov 09, 2018 at 01:17:41PM +0530, Nishad Kamdar wrote:
> > Convert the GPIO driver to use the GPIO irqchip library
> > GPIOLIB_IRQCHIP instead of reimplementing the same.
>
> Thanks for picking this up. Linus W took a stab at
вт, 13 нояб. 2018 г. в 20:59, Pavel Tatashin :
>
> On 18-11-13 15:23:50, Oleksandr Natalenko wrote:
> > Hi.
> >
> > > Yep. However, so far, it requires an application to explicitly opt in
> > > to this behavior, so it's not all that bad. Your patch would remove
> > > the requirement for
On Mon, Nov 12, 2018 at 04:15:09PM +0100, Johan Hovold wrote:
> On Fri, Nov 09, 2018 at 01:17:41PM +0530, Nishad Kamdar wrote:
> > Convert the GPIO driver to use the GPIO irqchip library
> > GPIOLIB_IRQCHIP instead of reimplementing the same.
>
> Thanks for picking this up. Linus W took a stab at
вт, 13 нояб. 2018 г. в 20:59, Pavel Tatashin :
>
> On 18-11-13 15:23:50, Oleksandr Natalenko wrote:
> > Hi.
> >
> > > Yep. However, so far, it requires an application to explicitly opt in
> > > to this behavior, so it's not all that bad. Your patch would remove
> > > the requirement for
On Tue, Nov 13, 2018 at 7:37 PM Joe Perches wrote:
>
> On Tue, 2018-11-13 at 19:17 +0200, Andy Shevchenko wrote:
> > There are users which print time and date represented by content of
> > struct rtc_time in human readable format.
> >
> > Instead of open coding that each time introduce
On Tue, Nov 13, 2018 at 7:37 PM Joe Perches wrote:
>
> On Tue, 2018-11-13 at 19:17 +0200, Andy Shevchenko wrote:
> > There are users which print time and date represented by content of
> > struct rtc_time in human readable format.
> >
> > Instead of open coding that each time introduce
On Sun, 11 Nov 2018 19:19:16 -0800
"Paul E. McKenney" wrote:
> On Mon, Nov 12, 2018 at 12:00:48PM +0900, Masami Hiramatsu wrote:
> > On Sun, 11 Nov 2018 11:43:49 -0800
> > "Paul E. McKenney" wrote:
> >
> > > Now that synchronize_rcu() waits for preempt-disable regions of code
> > > as well as
On Sun, 11 Nov 2018 19:19:16 -0800
"Paul E. McKenney" wrote:
> On Mon, Nov 12, 2018 at 12:00:48PM +0900, Masami Hiramatsu wrote:
> > On Sun, 11 Nov 2018 11:43:49 -0800
> > "Paul E. McKenney" wrote:
> >
> > > Now that synchronize_rcu() waits for preempt-disable regions of code
> > > as well as
On Tue, Nov 13, 2018 at 07:17:27PM +0200, Andy Shevchenko wrote:
> Use %ptR instead of open coded variant to print content of
> struct rtc_time in human readable format.
>
> Cc: Dmitry Torokhov
> Signed-off-by: Andy Shevchenko
Acked-by: Dmitry Torokhov
Please feel free to merge with the rest
On Tue, Nov 13, 2018 at 07:17:27PM +0200, Andy Shevchenko wrote:
> Use %ptR instead of open coded variant to print content of
> struct rtc_time in human readable format.
>
> Cc: Dmitry Torokhov
> Signed-off-by: Andy Shevchenko
Acked-by: Dmitry Torokhov
Please feel free to merge with the rest
Hi
* Belisko Marek [180703 18:34]:
> Hi Tony,
>
> On Tue, Jul 3, 2018 at 10:45 AM Tony Lindgren wrote:
> >
> > * Belisko Marek [180620 09:40]:
> > > Hello,
> > >
> > > I'm trying to fix warning (for omap5 board) produced by recent change
> > > to avoid using IRQ_TYPE_NONE like:
> > > [
From: Andy Lutomirski
Sent: November 13, 2018 at 5:47:16 PM GMT
> To: Nadav Amit
> Cc: Igor Stoppa , Kees Cook ,
> Peter Zijlstra , Mimi Zohar ,
> Matthew Wilcox , Dave Chinner ,
> James Morris , Michal Hocko , Kernel
> Hardening , linux-integrity
> , LSM List
> , Igor Stoppa
> , Dave
Hi
* Belisko Marek [180703 18:34]:
> Hi Tony,
>
> On Tue, Jul 3, 2018 at 10:45 AM Tony Lindgren wrote:
> >
> > * Belisko Marek [180620 09:40]:
> > > Hello,
> > >
> > > I'm trying to fix warning (for omap5 board) produced by recent change
> > > to avoid using IRQ_TYPE_NONE like:
> > > [
From: Andy Lutomirski
Sent: November 13, 2018 at 5:47:16 PM GMT
> To: Nadav Amit
> Cc: Igor Stoppa , Kees Cook ,
> Peter Zijlstra , Mimi Zohar ,
> Matthew Wilcox , Dave Chinner ,
> James Morris , Michal Hocko , Kernel
> Hardening , linux-integrity
> , LSM List
> , Igor Stoppa
> , Dave
From: Richard Gong
This is the 11th submission of Intel Stratix10 service layer and FPGA
manager driver patches. Starting from 10th submission Stratix10 service
layer driver .c file is moved to drivers/firmware, header files is moved
to include/linux/firmware/intel. And other firmware interface
From: Richard Gong
This is the 11th submission of Intel Stratix10 service layer and FPGA
manager driver patches. Starting from 10th submission Stratix10 service
layer driver .c file is moved to drivers/firmware, header files is moved
to include/linux/firmware/intel. And other firmware interface
501 - 600 of 1256 matches
Mail list logo
