o
strncpy_from_{user,unsafe}) even if we're already about to
copy data into the middle of the dynamic area.
Fixes: 9178412ddf5a ("tracing: probeevent: Return consumed bytes of dynamic
area")
Signed-off-by: Andreas Ziegler
Acked-by: Masami Hiramatsu
---
v2: follow coding g
o
strncpy_from_{user,unsafe}) even if we're already about to
copy data into the middle of the dynamic area.
Fixes: 9178412ddf5a ("tracing: probeevent: Return consumed bytes of dynamic
area")
Signed-off-by: Andreas Ziegler
Acked-by: Masami Hiramatsu
---
v2: follow coding g
o
strncpy_from_{user,unsafe}) even if we're already about to
copy data into the middle of the dynamic area.
Fixes: 9178412ddf5a ("tracing: probeevent: Return consumed bytes of dynamic
area")
Signed-off-by: Andreas Ziegler
---
kernel/trace/trace_probe_tmpl.h | 4 +++-
1 file changed, 3
On 17. Jan 2019, at 15:51, Steven Rostedt wrote:
>
> On Thu, 17 Jan 2019 15:29:09 +0100
> Andreas Ziegler wrote:
>
>> From my side it's basically good to go, but I just realized that there
>> is no "Fixes: " tag in it but the problem it fixes goes ba
On 1/17/19 3:20 PM, Steven Rostedt wrote:
On Thu, 17 Jan 2019 16:58:07 +0900
Masami Hiramatsu wrote:
Ah, I got it.
Hmm, in that case, I have to update my patch in the previous mail.
Anyway,
Acked-by: Masami Hiramatsu
So this patch is good to go? If so, I'll pull it in and start testing
it.
Hi,
On 1/17/19 10:47 AM, Masami Hiramatsu wrote:
On Thu, 17 Jan 2019 09:08:41 +0100
Andreas Ziegler wrote:
On 17.01.19 09:00, Masami Hiramatsu wrote:
On Thu, 17 Jan 2019 15:13:09 +0900
Masami Hiramatsu wrote:
On Wed, 16 Jan 2019 11:16:07 +0100
Andreas Ziegler wrote:
I went into this
The subsystem-specific message prefix for uprobes was also
"trace_kprobe: " instead of "trace_uprobe: " as described in
the original commit message.
Fixes: 7257634135c24 ("tracing/probe: Show subsystem name in messages")
Signed-off-by: Andreas Ziegler
---
kernel/
On 17.01.19 09:00, Masami Hiramatsu wrote:
> On Thu, 17 Jan 2019 15:13:09 +0900
> Masami Hiramatsu wrote:
>
>> On Wed, 16 Jan 2019 11:16:07 +0100
>> Andreas Ziegler wrote:
>>
>>>
>>> I went into this a bit deeper today, and right now it is simply fa
On 17.01.19 07:01, Masami Hiramatsu wrote:
> On Wed, 16 Jan 2019 15:16:29 +0100
> Andreas Ziegler wrote:
>
>> When printing multiple uprobe arguments as strings the output for the
>> earlier arguments would also include all later string arguments.
>>
>> Thi
e first character of the current string, leading to the
"accumulation" of strings in earlier arguments in the output.
Fix this by incrementing the return value of strncpy_from_user() by
one if we did not hit the maximum buffer size.
Signed-off-by: Andreas Ziegler
---
v2: removed a wro
On 1/16/19 2:40 PM, Steven Rostedt wrote:
On Wed, 16 Jan 2019 10:41:12 +0100
Andreas Ziegler wrote:
When printing multiple uprobe arguments as strings the output for the
earlier arguments would also include all later string arguments.
This is best explained in an example:
Consider adding a
Hi,
thanks for your reply!
On 1/16/19 11:00 AM, Masami Hiramatsu wrote:
On Tue, 15 Jan 2019 14:36:48 +0100
Andreas Ziegler wrote:
Hi again,
On 1/14/19 1:38 PM, Andreas Ziegler wrote:
Hi,
I've been playing around with uprobes today and found the following weird
behaviour/output
e first character of the current string, leading to the
"accumulation" of strings in earlier arguments in the output.
Fix this by incrementing the return value of strncpy_from_user() by
one if we did not hit the maximum buffer size.
Signed-off-by: Andreas Ziegler
---
kernel/trace/tra
Hi again,
On 1/14/19 1:38 PM, Andreas Ziegler wrote:
Hi,
I've been playing around with uprobes today and found the following weird
behaviour/output when using more than one string argument (or using the $comm
argument). This was run on a v4.20 mainline build on Ubuntu 18.04.
root@ubunt
Hi,
I've been playing around with uprobes today and found the following weird
behaviour/output when using more than one string argument (or using the $comm
argument). This was run on a v4.20 mainline build on Ubuntu 18.04.
root@ubuntu1810:~# uname -a
Linux ubuntu1810 4.20.0-042000-generic #20
Hi Jonas,
I noticed your patch 'regmap: make LZO cache optional' as it recently showed up
in linux-next. In your patch, you modify drivers/base/regmap/regcache.c by
adding an #if IS_ENABLED() statement.
However, this statement contains a spelling error, as it references
REGCHACHE_COMPRESSED inste
Forgot to CC linux-kernel and linux-pm in my first message.
On 11/28/2016 10:28, Andreas Ziegler wrote:
> Hi Markus,
>
> your patch "cpufreq: brcmstb-cpufreq: CPUfreq driver for older Broadcom STB
> SoCs" showed up in linux-next today, and I noticed a small error in it.
&
Hi Akashi,
your patch "module: extend 'rodata=off' boot cmdline parameter to module
mappings" showed up in linux-next today, and I noticed a small error in it.
The first modified #ifdef is fine, the second one, however, has a spelling
mistake in it: the CONFIG_ variable should be CONFIG_DEBUG_SET
the newly introduced #ifdef is unnecessary.
Let's remove it to avoid confusion.
Signed-off-by: Andreas Ziegler
---
kernel/printk/printk.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index a5ef95c..a37fc8c 100644
--- a/kernel/printk/printk
Hi Naveen,
this patchset makes a change to arch/powerpc/net/Makefile in order to only
compile the previously existing bpf_jit_comp.c if !CONFIG_PPC64, and use
bpf_jit_comp64.c if CONFIG_PPC64 is enabled.
Inside arch/powerpc/net/bpf_jit_comp.c, however, there is still an #ifdef
CONFIG_PPC64 block
Hi Hendrik,
your patch "s390/crc32-vx: add crypto API module for optimized CRC-32
algorithms" showed up in linux-next today (next-20160615) as commit
364148e0b195.
The patch defines the Kconfig option CRYPTO_CRC32_S390 which 'select's CRC32C.
However, this should probably have been CRYPTO_CR
The CONFIG_ prefix should only be used for options which
can be configured through Kconfig and not for guarding headers.
Signed-off-by: Andreas Ziegler
---
drivers/net/wan/fsl_ucc_hdlc.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wan/fsl_ucc_hdlc.h b
The CONFIG_ prefix should only be used for options which
can be configured through Kconfig and not for guarding headers.
Signed-off-by: Andreas Ziegler
---
include/soc/fsl/qe/qe_tdm.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/soc/fsl/qe/qe_tdm.h b/include
Fix a typo in the help message for the -d parameter by removing one 'm'.
Signed-off-by: Andreas Ziegler
---
scripts/checkkconfigsymbols.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkkconfigsymbols.py b/scripts/checkkconfigsymbols.py
index d8f6c0
This change cleans up style issues in drivers/pci/pcie/Kconfig, in
particular all indentation is now done using tabs, not spaces, and
the definition of PCIEASPM_DEBUG is now separated from the definition
of PCIEASPM with a newline.
Signed-off-by: Andreas Ziegler
---
drivers/pci/pcie/Kconfig | 7
lue used outside its choice group
drivers/pci/pcie/Kconfig:74:warning: choice value used outside its choice group
This change updates the Kconfig file for ARC, dropping the now
unnecessary 'source' statement, which makes the warning disappear.
Signed-off-by: Andreas Ziegler
---
arch/arc
neffective now.
Signed-off-by: Andreas Ziegler
---
security/integrity/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/security/integrity/Kconfig b/security/integrity/Kconfig
index 979be65..da95658 100644
--- a/security/integrity/Kconfig
+++ b/security/integrity/Kconfig
@@ -35,7 +35,6 @@ co
Hi David,
your patch "akcipher: Move the RSA DER encoding check to the crypto
layer" showed up in linux-next today as commit d43de6c780a8 (that is,
next-20160304).
It removes the CONFIG_PUBLIC_KEY_ALGO_RSA option, but does leave one
reference to it in place inside security/integrity/Kconfig, in t
c/keys unconditional
if CONFIG_KEYS=y"). This patch removes the inoperative select.
Signed-off-by: Andreas Ziegler
---
security/integrity/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/security/integrity/Kconfig b/security/integrity/Kconfig
index 21d7568..7543398 100644
--- a/s
Hi Dmitry,
your commit f4dc37785e9b ("integrity: define '.evm' as a builtin
'trusted' keyring") introduces the INTEGRITY_TRUSTED_KEYRING Kconfig
option, which has a 'select' to KEYS_DEBUG_PROC_KEYS.
This option, however, has been removed over a year ago by commit
dabd39cc2fb1 ("KEYS: Make /proc/k
On 01/26/2016 16:08, Rosen, Rami wrote:
> Hi,
>
> --- a/include/linux/cgroup.h
> +++ b/include/linux/cgroup.h
> @@ -604,11 +604,11 @@ static inline struct cgroup *sock_cgroup_ptr(struct
> sock_cgroup_data *skcd)
> #endif
> }
>
> In this occasion, seems that maybe something else is also missin
Hi Rafał,
your commit 399500da18f7 ("ssb: pick PCMCIA host code support from b43
driver") removed the Kconfig option B43_PCMCIA from Kconfig, but left
one reference to it in b43/main.c, inside the b43_print_driverinfo()
function.
Can this #ifdef be removed, should it be replaced with an #ifdef us
Signed-off-by: Andreas Ziegler
---
include/linux/cgroup.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
index 2162dca..48ce12f 100644
--- a/include/linux/cgroup.h
+++ b/include/linux/cgroup.h
@@ -604,11 +604,11 @@ static inline
option
STOP_MACHINE from init/Kconfig and ensured that stop_machine()
universally works. Due to the order in which the patches were applied,
removing the select from DRM_I915 got lost during merging.
Remove the now obsolete select statement.
Signed-off-by: Andreas Ziegler
Reviewed-by: Chris Wilso
Commit 86fffe4a61dd ("kernel: remove stop_machine() Kconfig
dependency") removed the option STOP_MACHINE from init/Kconfig, but
missed a select to this option from the DRM_I915 option.
Remove this now obsolete select statement.
Signed-off-by: Andreas Ziegler
---
drivers/gpu/drm/i9
Hi Chris,
your commit 5bab6f60cb4d ("drm/i915: Serialise updates to GGTT with
access through GGTT on Braswell") added a select to STOP_MACHINE to the
DRM_I915 Kconfig option.
In 4.5-rc1, your commit 86fffe4a61dd ("kernel: remove stop_machine()
Kconfig dependency") then removed STOP_MACHINE entire
27;s fix them up.
Signed-off-by: Andreas Ziegler
---
kernel/memremap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/memremap.c b/kernel/memremap.c
index e517a16..2e84aa8 100644
--- a/kernel/memremap.c
+++ b/kernel/memremap.c
@@ -377,7 +377,7 @@ struct vmem_altmap
Hi Florian,
your patch "MIPS: BMIPS: Enable GZIP ramdisk and timed printks"
showed up as commit fb9e5642aa9e in linux-next today (that is,
next-20151112). I noticed it because we (a research group from
Erlangen[0]) are running daily checks on linux-next.
Your commit adds two entries to arch/mips/
Hi Jarkko,
your patch "tpm, tpm_tis: fix tpm_tis ACPI detection issue with TPM 2.0"
showed up as commit 399235dc6e95 in linux-next today (that is,
next-20151020). I noticed it because we (a research group from
Erlangen[0]) are running daily checks on linux-next.
Your commit creates the following
Hi Jonas,
your patch "spi/bcm63xx: fix standard accessors and compile guard"
showed up as commit 682b5280bf00 in linux-next today (that is,
next-20151013). I noticed it because we (a research group from
Erlangen[0]) are running daily checks on linux-next.
Your commit fixes two #ifdef statements i
Hi,
On 09/14/2015 10:41, Mason wrote:
> Hello,
>
> I did make menuconfig in v4.2
>
> In the help for CONFIG_CRYPTO_HMAC, I have
>
> │ Selected by: IP_SCTP [=n] && NET [=y] && INET [=y] && (IPV6 [=n] ||
> IPV6 [=n]=n) || INET_AH [=n] && NET [=y] && INET [=y] || \ │
> │ INET
Hi Helge,
today's linux-next tree (next-20150903) contains commit 20f924902ff6
("parisc: adjust L1_CACHE_BYTES to 128 bytes on PA8800 and PA8900 CPUs")
which you authored.
I noticed it because we[0] are running a daily analysis on all commits
in linux-next as part of our research and our tools re
42 matches
Mail list logo