On Tue, Jul 28, 2020 at 09:39:55AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jul 20, 2020 at 09:16:25PM +0200, Jiri Olsa escreveu:
> > On Mon, Jul 20, 2020 at 02:32:40PM +0530, kajoljain wrote:
> > >
> > >
> > > On 7/20/20 1:49 PM, Jiri Olsa wrote:
> > > > On Mon, Jul 20, 2020 at
Reviewed-by: Johannes Thumshirn
On Tue, 28 Jul 2020 18:27:19 +0800
Chengming Zhou wrote:
> We should clear module from hash of all ops on ftrace_ops_list when
> module going, or the ops including these modules will be matched
> wrongly by new module loaded later.
This is really up to the owner of the hash and not the
On Tue, Jul 28, 2020 at 02:51:23PM +0200, Paul Cercueil wrote:
>
>
> Le mar. 28 juil. 2020 à 14:00, Krzysztof Kozlowski a écrit
> :
> > On Tue, Jul 28, 2020 at 01:37:02PM +0200, Thomas Bogendoerfer wrote:
> > > On Tue, Jul 28, 2020 at 01:19:35PM +0200, Krzysztof Kozlowski wrote:
> > > > On
On Fri, Jul 24, 2020 at 11:33:25AM -0600, Jonathan Corbet wrote:
> I'm not sure what to do other than to continue to push for minimal use of
> intrusive markup.
Perhaps make it clearer in:
Documentation/doc-guide/
because people claim they follow that, but the result is that I get
completely
Le mar. 28 juil. 2020 à 11:21, Krzysztof Kozlowski a
écrit :
On Mon, Jul 27, 2020 at 06:20:34PM +0200, Paul Cercueil wrote:
The driver only uses the registers up to offset 0x54. Since the
EFUSE
registers are in the middle of the NEMC registers, we only request
the registers we will use
Le mar. 28 juil. 2020 à 14:00, Krzysztof Kozlowski a
écrit :
On Tue, Jul 28, 2020 at 01:37:02PM +0200, Thomas Bogendoerfer wrote:
On Tue, Jul 28, 2020 at 01:19:35PM +0200, Krzysztof Kozlowski wrote:
> On Tue, Jul 28, 2020 at 01:12:11PM +0200, Paul Cercueil wrote:
> > Hi Krzysztof,
> >
On Tue, Jul 28, 2020 at 12:35:17PM +, David Laight wrote:
> From: Peilin Ye
> > Sent: 28 July 2020 12:52
> > Currently `struct drm_buf_desc` is defined as follows:
> >
> > struct drm_buf_desc {
> > int count;
> > int size;
> > int low_mark;
> > int high_mark;
> > enum {
>
Thanks for the review! I'll send a new revision of the patch with the
%x formatter and using the TP_CONDITION macro.
On adding further information to the trace event, I would prefer
adding the strict minimum to be able to correlate the event with the
avc message. The reason is that tracevents
On 2020/7/28 07:04, Gustavo A. R. Silva wrote:
> Replace the existing /* fall through */ comments and its variants with
> the new pseudo-keyword macro fallthrough[1].
>
> [1]
> https://www.kernel.org/doc/html/v5.7/process/deprecated.html?highlight=fallthrough#implicit-switch-case-fall-through
>
On Tue, Jul 28, 2020 at 02:24:37PM +0200, Dafna Hirschfeld wrote:
>
>
> On 24.07.20 14:02, Kaaira Gupta wrote:
> > An output which is running is already part of a pipeline and trying to
> > start a new pipeline is not possible. This prevents two capture devices
> > from streaming at the same
On Tue, Jul 28, 2020 at 10:27:56AM +0800, Qinglang Miao wrote:
> the function clk_get() returns ERR_PTR() in case of error and
> never returns NULL. So there's no need to test whether xusbxti
> is NULL, just remove the redundant part in the return value check.
>
> Signed-off-by: Qinglang Miao
>
Em Tue, Jul 28, 2020 at 01:57:32AM -0700, Ian Rogers escreveu:
> Test that a command line option doesn't override the period set on a
> libpfm4 event.
> Without libpfm4 test passes as unsupported.
Thanks, applied.
- Arnaldo
At the moment opening a serial device node (such as /dev/ttyS3)
succeeds even if there is no actual serial device behind it.
Reading/writing/ioctls (most) expectantly fail as the uart port is not
initialized (the type is PORT_UNKNOWN) and the TTY_IO_ERROR error state
bit is set fot the tty.
On Mon, 27 Jul 2020 at 19:37, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.190 release.
> There are 64 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
Hi,
On Mon, Jul 27, 2020 at 11:39:12AM -0300, Ezequiel Garcia wrote:
> On Sat, 2020-07-25 at 23:34 +0900, Alexandre Courbot wrote:
> > On Thu, Jul 16, 2020 at 5:23 AM Ezequiel Garcia
> > wrote:
> > > The H.264 specification requires in its "Slice header semantics"
> > > section that the
Em Thu, Jul 23, 2020 at 10:59:58AM -0500, Paul A. Clarke escreveu:
> On Wed, Jul 22, 2020 at 08:11:58PM +0200, Jiri Olsa wrote:
> > On Tue, Jul 21, 2020 at 09:48:48AM -0500, Paul A. Clarke wrote:
> > > On Sun, Jul 19, 2020 at 08:13:01PM +0200, Jiri Olsa wrote:
> > > > hi,
> > > > this patchset is
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git
tags/asm-generic-fixes-5.8
for you to fetch changes up to
This patch is compile-tested only
Thanks
Vaibhav Gupta
Linus Torvalds writes:
> On Mon, Jul 27, 2020 at 2:06 PM Eric W. Biederman
> wrote:
>>
>> Therefore make it simpler to get exec correct by freezing the other
>> threads at the beginning of exec. This removes an entire class of
>> races, and makes it tractable to fix some of the long standing
This patch is compile-tested only.
Thanks
Vaibhav Gupta
The "fd" transport layer uses 2 file descriptors passed externally
and calls kernel_write()/kernel_read() on these. If files were opened
without FMODE_WRITE/FMODE_READ, WARN_ON_ONCE() will fire.
This adds file mode checking in p9_fd_open; this returns -EBADF to
preserve the original behavior.
Hi Arnaldo,
On Tue, Jul 28, 2020 at 09:06:23AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jul 24, 2020 at 05:16:03PM +0800, Wei Li escreveu:
> > The ARMv8.3-SPE adds an Alignment Flag in the Events packet and filtering
> > on this event using PMSEVFR_EL1, together with support for the
On 28.07.20 10:15, Vitaly Kuznetsov wrote:
Alexander Graf writes:
MSRs are weird. Some of them are normal control registers, such as EFER.
Some however are registers that really are model specific, not very
interesting to virtualization workloads, and not performance critical.
Others
This patch is compile-tested only.
Thanks
Vaibhav Gupta
This patch is compile-tested only.
Thanks
Vaibhav Gupta
Em Mon, Jul 20, 2020 at 09:16:25PM +0200, Jiri Olsa escreveu:
> On Mon, Jul 20, 2020 at 02:32:40PM +0530, kajoljain wrote:
> >
> >
> > On 7/20/20 1:49 PM, Jiri Olsa wrote:
> > > On Mon, Jul 20, 2020 at 01:39:24PM +0530, kajoljain wrote:
> > >
> > > SNIP
> > >
> > >> This is with your
The following changes since commit 2648298a06ba7e902c4489a15c0db26032813c7b:
Merge tag 'socfpga_fixes_for_v5.8_v2' of
git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux into
arm/fixes (2020-07-17 18:01:41 +0200)
are available in the Git repository at:
Em Sun, Jul 26, 2020 at 02:51:19PM +0530, kajoljain escreveu:
>
>
> On 7/19/20 11:43 PM, Jiri Olsa wrote:
> > Following the previous change that rename egroup
> > to metric, there's no reason to call the list
> > 'group_list' anymore, renaming it to metric_list.
> >
> > Signed-off-by: Jiri Olsa
This patch is compile-tested only.
Thanks
Vaibhav Gupta
Hi Arnaldo,
On Tue, Jul 28, 2020 at 09:02:20AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jul 27, 2020 at 02:34:36PM -0600, Mathieu Poirier escreveu:
> > On Fri, Jul 24, 2020 at 03:11:11PM +0800, Wei Li wrote:
> > > - Firstly, the function auxtrace_record__init() will be invoked only
> > >
On 28.7.2020 14.16, Greg KH wrote:
> On Mon, Jul 27, 2020 at 11:24:06PM -0500, Forest Crossman wrote:
>> The first patch just defines some host controller device IDs to make the
>> code a bit easier to read (since the controller part number is not
>> always the same as the DID) and to prepare for
This patch is compile-tested only.
Thanks
Vaibhav Gupta
Hi Maxime
On Wed, 8 Jul 2020 at 18:43, Maxime Ripard wrote:
>
> The HDMI controllers found in the BCM2711 has a pretty different clock and
> registers areas than found in the older BCM283x SoCs.
>
> Let's create a variant structure to store the various adjustments we'll
> need later on, and a
Em Sun, Jul 19, 2020 at 03:41:14PM -0700, Ian Rogers escreveu:
> On Sun, Jul 19, 2020 at 11:14 AM Jiri Olsa wrote:
> >
> > Adding test for metric group plus compute_metric_group
> > function to get metrics values within the group.
> >
> > Signed-off-by: Jiri Olsa
>
> Acked-by: Ian Rogers
Em Sun, Jul 19, 2020 at 08:13:17PM +0200, Jiri Olsa escreveu:
> So far compute_single function relies on the fact, that
> there's only single metric defined within evlist in all
> tests. In following patch we will add test for metric
> group, so we need to be able to compute metric by given
>
Drivers using legacy power management .suspen()/.resume() callbacks
have to manage PCI states and device's PM states themselves. They also
need to take care of standard configuration registers.
Switch to generic power management framework using a single
"struct dev_pm_ops" variable to take the
From: Peilin Ye
> Sent: 28 July 2020 12:52
> Currently `struct drm_buf_desc` is defined as follows:
>
> struct drm_buf_desc {
> int count;
> int size;
> int low_mark;
> int high_mark;
> enum {
> _DRM_PAGE_ALIGN = 0x01,
> _DRM_AGP_BUFFER =
Em Sun, Jul 19, 2020 at 03:40:26PM -0700, Ian Rogers escreveu:
> On Sun, Jul 19, 2020 at 11:14 AM Jiri Olsa wrote:
> >
> > Keeping the stack of nested metrics via 'struct expr_id' objects
> > and checking if we are in recursion via already processed metric.
> >
> > The stack is implemented as
Em Sun, Jul 26, 2020 at 02:49:35PM +0530, kajoljain escreveu:
>
>
> On 7/19/20 11:43 PM, Jiri Olsa wrote:
> > Adding test that compute metric with other metrics in it.
> >
> > cache_miss_cycles = metric:dcache_miss_cpi + metric:icache_miss_cycles
> >
> > Acked-by: Ian Rogers
> >
Em Sun, Jul 26, 2020 at 02:49:46PM +0530, kajoljain escreveu:
> On 7/19/20 11:43 PM, Jiri Olsa wrote:
> > Adding test that compute DCache_L2 metrics with other related metrics in it.
> >
> > Acked-by: Ian Rogers
> > Signed-off-by: Jiri Olsa
>
> Reviewed-By : Kajol Jain
Thanks, applied.
-
On 2020/7/27 16:32, Arnd Bergmann wrote:
On Mon, Jul 27, 2020 at 10:22 AM Tianjia Zhang
wrote:
SPI protocol standardized by the TCG is described in the TCG PTP
specification 1.3 (chapter 6.4.6 SPI Bit Protocol), It was published by
Em Sun, Jul 19, 2020 at 03:34:48PM -0700, Ian Rogers escreveu:
> On Sun, Jul 19, 2020 at 11:14 AM Jiri Olsa wrote:
> >
> > There's no need to iterate the whole list of groups,
> > when adding new events. The currently created groups
> > are the ones we want to add.
> >
> > Signed-off-by: Jiri
Hi Maxime
On Wed, 8 Jul 2020 at 18:43, Maxime Ripard wrote:
>
> The unbind function needs to retrieve a vc4_hdmi structure pointer through
> the struct device that we're given since we want to support multiple HDMI
> controllers.
>
> However, our optional ASoC support doesn't make that trivial
Em Sun, Jul 26, 2020 at 02:49:04PM +0530, kajoljain escreveu:
>
>
> On 7/19/20 11:43 PM, Jiri Olsa wrote:
> > Adding computation (expr__parse call) of referenced metric at
> > the point when it needs to be resolved during the parent metric
> > computation.
> >
> > Once the inner metric is
Looks good,
Reviewed-by: Johannes Thumshirn
On Fri, Jul 24, 2020 at 03:10:52PM -0400, Liang, Kan wrote:
> > > > Per the SIBLING patch this then wants to be:
> > > >
> > > > if (!is_slots_event(leader))
> > > > return -EINVAL;
> > > >
> > > > event->event_caps |= PERF_EV_CAP_SIBLING.
> > > >
Em Sun, Jul 19, 2020 at 03:32:26PM -0700, Ian Rogers escreveu:
> On Sun, Jul 19, 2020 at 11:14 AM Jiri Olsa wrote:
> >
> > Adding referenced metrics to the parsing context so they
> > can be resolved during the metric processing.
> >
> > Adding expr__add_ref function to store referenced metrics
>
On 2020/7/27 16:33, peter.hu...@infineon.com wrote:
Hi,
On 2020/7/27 15:10, Arnd Bergmann wrote:
On Mon, Jul 27, 2020 at 4:54 AM Tianjia Zhang
wrote:
Obviously, the TPM version number in the help message is wrong, which
will cause confusion. This patch fixes it.
How is this "obvious"? I
Em Sun, Jul 19, 2020 at 03:18:58PM -0700, Ian Rogers escreveu:
> On Sun, Jul 19, 2020 at 11:13 AM Jiri Olsa wrote:
> >
> > Collecting referenced metrics in struct metric_ref_node object,
> > so we can process them later on.
> >
> > The change will parse nested metric names out of expression and
>
Hi Jürgen,
I'm sorry about the late reply (vacation).
On Mon, Jul 20, 2020 at 06:31:04PM +0200, Jürgen Stauber wrote:
> Hi all,
>
> I was made aware in the following launchpad bug report, that I should report
> the issue directly with the upstream maintainers:
>
Add a DT binding documentation for the MT8192 soc.
Acked-by: Rob Herring
Signed-off-by: Qii Wang
---
Documentation/devicetree/bindings/i2c/i2c-mt65xx.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-mt65xx.txt
Add i2c compatible for MT8192. Compare to MT8183 i2c controller,
MT8192 support more then 8GB DMA mode.
Signed-off-by: Qii Wang
---
drivers/i2c/busses/i2c-mt65xx.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/drivers/i2c/busses/i2c-mt65xx.c
Em Sun, Jul 26, 2020 at 02:48:35PM +0530, kajoljain escreveu:
>
>
> On 7/19/20 11:43 PM, Jiri Olsa wrote:
> > Add referenced metrics into struct metric_expr object,
> > so they are accessible when computing the metric.
> >
> > Storing just name and expression itself, so the metric
> > can be
With the apdma remove hand-shake signal, it need to keep i2c and
apdma in sync manually.
Reviewed-by: Yingjoe Chen
Reviewed-by: Matthias Brugger
Signed-off-by: Qii Wang
---
drivers/i2c/busses/i2c-mt65xx.c | 23 ---
1 file changed, 20 insertions(+), 3 deletions(-)
diff
This series are based on 5.8-rc1 and we provide four i2c patches
to support mt8192 SoC.
Main changes compared to v1:
--modify the commit with access more than 8GB dram
--add Reviewed-by and Acked-by from Yingjoe, Matthias and Rob
Qii Wang (4):
i2c: mediatek: Add apdma sync in i2c driver
i2c:
Newer MTK chip support more than 8GB of dram. Replace support_33bits
with more general dma_max_support and remove mtk_i2c_set_4g_mode.
Signed-off-by: Qii Wang
---
drivers/i2c/busses/i2c-mt65xx.c | 38 +-
1 file changed, 17 insertions(+), 21 deletions(-)
diff
Em Sun, Jul 26, 2020 at 02:48:05PM +0530, kajoljain escreveu:
>
>
> On 7/19/20 11:43 PM, Jiri Olsa wrote:
> > Renaming __metricgroup__add_metric to __add_metric
> > to fit in the current function names.
> >
> > Acked-by: Ian Rogers
> > Signed-off-by: Jiri Olsa
>
> Reviewed-By : Kajol Jain
Hi Andy,
On Mon, Jul 27, 2020 at 04:07:07PM +0300, Andy Shevchenko wrote:
> On Mon, Jul 27, 2020 at 3:23 PM Vadym Kochan wrote:
> >
> > Add very basic support for devlink interface:
> >
> > - driver name
> > - fw version
> > - devlink ports
>
> ...
>
> > +static int
Em Sun, Jul 26, 2020 at 02:47:53PM +0530, kajoljain escreveu:
>
>
> On 7/19/20 11:43 PM, Jiri Olsa wrote:
> > Decouple metric adding logging into add_metric function,
> > so it can be used from other places in following changes.
> >
> > Acked-by: Ian Rogers
> > Signed-off-by: Jiri Olsa
> >
Em Sun, Jul 19, 2020 at 02:46:12PM -0700, Ian Rogers escreveu:
> On Sun, Jul 19, 2020 at 11:13 AM Jiri Olsa wrote:
> >
> > Adding following macros to iterate events and metric:
> > map_for_each_event(__pe, __idx, __map)
> > - iterates over all pmu_events_map events
> >
The following commit has been merged into the perf/core branch of tip:
Commit-ID: d903b6d029d66e6478562d75ea18d89098f7b7e8
Gitweb:
https://git.kernel.org/tip/d903b6d029d66e6478562d75ea18d89098f7b7e8
Author:Pu Wen
AuthorDate:Mon, 20 Jul 2020 16:22:05 +08:00
Committer:
The following commit has been merged into the x86/kaslr branch of tip:
Commit-ID: 237069512d18f0f20b230680f067a2c070a7903a
Gitweb:
https://git.kernel.org/tip/237069512d18f0f20b230680f067a2c070a7903a
Author:Arvind Sankar
AuthorDate:Mon, 27 Jul 2020 19:07:55 -04:00
The following commit has been merged into the x86/kaslr branch of tip:
Commit-ID: a68bcea591a040cce5e08615c829a316beb3e4b4
Gitweb:
https://git.kernel.org/tip/a68bcea591a040cce5e08615c829a316beb3e4b4
Author:Arvind Sankar
AuthorDate:Mon, 27 Jul 2020 19:07:56 -04:00
The following commit has been merged into the x86/kaslr branch of tip:
Commit-ID: c8465b03acf9d4bb43b9714b6cfb99442defe664
Gitweb:
https://git.kernel.org/tip/c8465b03acf9d4bb43b9714b6cfb99442defe664
Author:Arvind Sankar
AuthorDate:Mon, 27 Jul 2020 19:07:54 -04:00
The following commit has been merged into the x86/kaslr branch of tip:
Commit-ID: 7f104ea54e69ec45cbc4948cdb7d7f74d46def6d
Gitweb:
https://git.kernel.org/tip/7f104ea54e69ec45cbc4948cdb7d7f74d46def6d
Author:Arvind Sankar
AuthorDate:Mon, 27 Jul 2020 19:07:57 -04:00
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 112a0e4171e111e963aada3fe790c71accf4d705
Gitweb:
https://git.kernel.org/tip/112a0e4171e111e963aada3fe790c71accf4d705
Author:Masami Hiramatsu
AuthorDate:Tue, 28 Jul 2020 16:34:00 +09:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 21a6ee14a8f277766618ef07154432b46528113e
Gitweb:
https://git.kernel.org/tip/21a6ee14a8f277766618ef07154432b46528113e
Author:Miaohe Lin
AuthorDate:Tue, 28 Jul 2020 19:17:55 +08:00
Committer:
From: Landen Chao
in recent Kernel-Versions there are warnings about incorrect MTU-Size
like these:
eth0: mtu greater than device maximum
mtk_soc_eth 1b10.ethernet eth0: error -22 setting MTU to include DSA
overhead
Fixes: bfcb813203e6 ("net: dsa: configure the MTU for switch ports")
Em Sun, Jul 26, 2020 at 02:47:11PM +0530, kajoljain escreveu:
>
>
> On 7/19/20 11:43 PM, Jiri Olsa wrote:
> > Adding expr__del_id function to remove ID from hashmap.
> > It will save us few lines in following changes.
> >
> > Acked-by: Ian Rogers
> > Signed-off-by: Jiri Olsa
>
> Reviewed-By
Em Sun, Jul 26, 2020 at 02:47:00PM +0530, kajoljain escreveu:
>
>
> On 7/19/20 11:43 PM, Jiri Olsa wrote:
> > Changing expr__get_id to use and return struct expr_id_data
> > pointer as value for the ID. This way we can access data other
> > than value for given ID in following changes.
> >
> >
Em Sun, Jul 26, 2020 at 02:46:47PM +0530, kajoljain escreveu:
>
>
> On 7/19/20 11:43 PM, Jiri Olsa wrote:
> > Adding expr__add_id function to data for ID
> > with zero value, which is used when scanning
> > the expression for IDs.
> >
>
> Reviewed-By : Kajol Jain
Thanks, applied.
- Arnaldo
Looks good,
Reviewed-by: Johannes Thumshirn
Hi Wei,
On Fri, Jul 24, 2020 at 05:16:04PM +0800, Wei Li wrote:
> Armv8.3 extends the SPE by adding:
> - Alignment field in the Events packet, and filtering on this event
> using PMSEVFR_EL1.
> - Support for the Scalable Vector Extension (SVE).
>
> The main additions for SVE are:
> - Recording
On 27.07.2020 20:11, Anthony Yznaga wrote:
> This patchset adds support for preserving an anonymous memory range across
> exec(3) using a new madvise MADV_DOEXEC argument. The primary benefit for
> sharing memory in this manner, as opposed to re-attaching to a named shared
> memory segment, is to
Looks good,
Reviewed-by: Johannes Thumshirn
Em Sun, Jul 19, 2020 at 02:41:46PM -0700, Ian Rogers escreveu:
> On Sun, Jul 19, 2020 at 11:13 AM Jiri Olsa wrote:
> >
> > Arnaldo found that we don't release value data in case the
> > hashmap__set fails. Releasing it in case of an error.
> >
> > Reported-by: Arnaldo Carvalho de Melo
> >
On 7/28/20 3:07 AM, Kevin Tang wrote:
> diff --git a/drivers/gpu/drm/sprd/Kconfig b/drivers/gpu/drm/sprd/Kconfig
> new file mode 100644
> index 000..b189a54
> --- /dev/null
> +++ b/drivers/gpu/drm/sprd/Kconfig
> @@ -0,0 +1,12 @@
> +config DRM_SPRD
> + tristate "DRM Support for Unisoc SoCs
Hi all,
In commit
cde1a8a99287 ("Bluetooth: btusb: Fix and detect most of the Chinese Bluetooth
controllers")
Fixes tag
Fixes: 81cac64ba258ae (Deal with USB devices that are faking CSR vendor)
has these problem(s):
- Subject does not match target commit subject
Just use
On 24.07.20 14:02, Kaaira Gupta wrote:
An output which is running is already part of a pipeline and trying to
start a new pipeline is not possible. This prevents two capture devices
from streaming at the same time.
Instead of failing to start the second capture device allow it to join
the
Looks good,
Reviewed-by: Johannes Thumshirn
On Mon, Jul 27, 2020 at 3:17 PM Dan Carpenter wrote:
> Here are my latest warnings on linux-next from Friday.
Thanks for sharing this Dan, very interesting findings.
> drivers/gpio/gpiolib-cdev.c:473 lineevent_read() warn: check that 'ge'
> doesn't leak information (struct has a hole after
On Tue, Jul 28, 2020 at 12:19:03PM +, Song Bao Hua (Barry Song) wrote:
> I am sorry I haven't got your point yet. Do you mean something like the below?
>
> arch/arm64/Kconfig:
> config CMDLINE
> string "Default kernel command string"
> - default ""
> + default "pernuma_cma=16M"
Aleksa Sarai writes:
> On 2020-07-27, Eric W. Biederman wrote:
>> To the best of my knowledge processes with more than one thread
>> calling exec are not common, and as all of the threads will be killed
>> by exec there does not appear to be any useful work a thread can
>> reliably do during
This patch allows copying the DSCP from inner IPv4 header to the
outer IPv6 header, when doing SRv6 Encapsulation.
This allows forwarding packet across the SRv6 fabric based on their
original traffic class.
Signed-off-by: Ahmed Abdelsalam
---
net/ipv6/seg6_iptunnel.c | 11 ++-
1 file
> -Original Message-
> From: Christoph Hellwig [mailto:h...@lst.de]
> Sent: Tuesday, July 28, 2020 11:53 PM
> To: Song Bao Hua (Barry Song)
> Cc: h...@lst.de; m.szyprow...@samsung.com; robin.mur...@arm.com;
> w...@kernel.org; ganapatrao.kulka...@cavium.com;
> catalin.mari...@arm.com;
Looks good,
Reviewed-by: Johannes Thumshirn
On 7/28/20 7:07 AM, Mark Brown wrote:
On Tue, Jul 28, 2020 at 06:59:50AM +, RAVULAPATI, VISHNU VARDHAN RAO wrote:
So Actually for rt5682 codec Now in 5.8 there are three flags :
SND_SOC_RT5682
SND_SOC_RT5682_I2C
SND_SOC_RT5682_SDW
But till 5.7.8 we have
SND_SOC_RT5682
Em Mon, Jul 27, 2020 at 08:26:27AM +0800, Jin, Yao escreveu:
>
>
> On 7/27/2020 8:21 AM, Jin, Yao wrote:
> >
> >
> > On 7/26/2020 3:52 PM, Jiri Olsa wrote:
> > > Jin Yao reported issue with possible conflict between raw
> > > events and term values in pmu event syntax.
> > >
> > > Currently
Looks good,
Reviewed-by: Johannes Thumshirn
Em Sat, Jul 25, 2020 at 09:40:55AM -0700, Ian Rogers escreveu:
> On Sat, Jul 25, 2020 at 5:20 AM Jiri Olsa wrote:
> >
> > Adding support to specify raw event with 'r0' syntax within
> > pmu term syntax like:
> >
> > -e cpu/r0xdead/
> >
> > It will be used to specify raw events in cases where
Looks good,
Reviewed-by: Johannes Thumshirn
Em Mon, Jul 27, 2020 at 11:09:43PM -0700, Andrii Nakryiko escreveu:
> On Mon, Jul 27, 2020 at 12:21 PM Roman Gushchin wrote:
> >
> > Since bpf stopped using memlock rlimit to limit the memory usage,
> > there is no more reason for perf to alter its own limit.
> >
> > Signed-off-by: Roman Gushchin
On Tuesday, 28 July 2020, 13:20:15 CEST, David Laight wrote:
> From: Christian Eggers
>
> > {
> >
> > fram: fram@0 {
> > ...
> > mac_address_fec2: mac-address@126 {
> > reg = <0x126 6>;
> > };
> > ...
> > };
> > };
>
>
> H the
This code reads from the array before verifying that "c" is a valid
index. Move test array offset code before use to fix it.
Fixes: 2da572c959dd ("lib: add software 842 compression/decompression")
Signed-off-by: Huang Guobin
---
lib/842/842_compress.c | 9 +++--
1 file changed, 7
The first two patches fix a NULL-pointer dereference at probe that can
be triggered by a malicious device and a small transfer-buffer memory
leak, respectively.
For another subsystem I would have marked them:
Cc: sta...@vger.kernel.org # 4.3
The third one replaces the driver's
The interrupt URB transfer-buffer was never freed on disconnect or after
probe errors.
Fixes: 55d7de9de6c3 ("Microchip's LAN7800 family USB 2/3 to 10/100/1000
Ethernet device driver")
Cc: woojung@microchip.com
Signed-off-by: Johan Hovold
---
drivers/net/usb/lan78xx.c | 1 +
1 file
Drop the bogus endpoint-lookup helper which could end up accepting
interfaces based on endpoints belonging to unrelated altsettings.
Note that the returned bulk pipes and interrupt endpoint descriptor
were never actually used. Instead the bulk-endpoint numbers are
hardcoded to 1 and 2 (matching
Add the missing endpoint sanity check to prevent a NULL-pointer
dereference should a malicious device lack the expected endpoints.
Note that the driver has a broken endpoint-lookup helper,
lan78xx_get_endpoints(), which can end up accepting interfaces in an
altsetting without endpoints as long as
Em Fri, Jul 24, 2020 at 06:07:06PM +0800, Wang ShaoBo escreveu:
> Function jvmti_write_code called by compiled_method_load_cb may return
> error in using fwrite_unlocked, this failure should be captured and
> warned.
Thanks, applied.
- Arnaldo
> Signed-off-by: Wang ShaoBo
> ---
>
901 - 1000 of 1424 matches
Mail list logo
