On 2019/01/19 21:16, Dmitry Vyukov wrote:
>> The question for me is, whether sysbot can detect hash collision with
>> different
>> syz-program lines before writing the hash value to /dev/kmsg, and retry by
>> modifying
>> syz-program lines in order to get a new hash value until collision is
>>
On 25-12-18, 11:04, Peng Ma wrote:
> Add NXP Data Path Acceleration Architecture 2 (dpaa2) queue direct
> memory(qDMA) controller driver support.
> This module can be found on NXP LS2 SoCs.
>
> Signed-off-by: Peng Ma
> ---
> drivers/dma/Kconfig |2 +
>
On Sat, Jan 19, 2019 at 12:52:52PM +0100, Christian Zigotzky wrote:
> Hi Christoph,
>
> I have found a small workaround. If I add 'mem=3500M' to the boot arguments
> then it detects the SATA hard disk and boots without any problems.
>
> X5000> setenv bootargs root=/dev/sda2 console=ttyS0,115200
On 2019/01/19 20:41, Dmitry Vyukov wrote:
> On Sat, Jan 19, 2019 at 12:32 PM syzbot
> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:2339e91d0e66 Merge tag 'media/v5.0-1' of git://git.kernel...
>> git tree: upstream
>> console output:
On Sat, Jan 19, 2019 at 1:39 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:9673b4aa71ca Add linux-next specific files for 20190118
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=10c2097f40
> kernel config:
Use of_device_get_match_data() to simplify the code a bit.
Signed-off-by: Axel Lin
---
drivers/regulator/twl-regulator.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/regulator/twl-regulator.c
b/drivers/regulator/twl-regulator.c
index
Hi Kamil,
2019년 1월 18일 (금) 오후 10:18, Kamil Konieczny
님이 작성:
>
> Add imem clocks for exynos5433. This will enable to use crypto Slim
> Security SubSystem (in short SlimSSS) IP block.
>
> Signed-off-by: Kamil Konieczny
> ---
> drivers/clk/samsung/clk-exynos5433.c | 32
On Fri, Jan 18, 2019 at 9:07 PM tedheadster wrote:
>
> I do not see this problem with the upstream kernel, so 3.16 probably
> needs a missing upstream patch.
This was indeed fixed by Andy Lutomirski's follow-up patch "x86/vdso: Fix vDSO
syscall fallback asm constraint regression". I tested part
Hello,
syzbot found the following crash on:
HEAD commit:9673b4aa71ca Add linux-next specific files for 20190118
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10c2097f40
kernel config: https://syzkaller.appspot.com/x/.config?x=4086e03c3128165
Signed-off-by: Axel Lin
---
drivers/regulator/arizona-ldo1.c | 37
1 file changed, 9 insertions(+), 28 deletions(-)
diff --git a/drivers/regulator/arizona-ldo1.c b/drivers/regulator/arizona-ldo1.c
index b9a93049e41e..dfed6d3f03ad 100644
---
Hi Yangtao,
2019년 1월 19일 (토) 오후 2:03, Yangtao Li 님이 작성:
>
> 'devfreq' is malloced in devfreq_add_device() and should be freed in
> the error handling cases, otherwise it will cause memory leak.
>
> devm_kzalloc() could fail, so insert a check of its return value. And
> if it fails, returns
On Fri, Jan 18, 2019 at 6:20 AM Tetsuo Handa
wrote:
>
> Dmitry Vyukov wrote:
> > On Sun, Jan 6, 2019 at 2:47 PM Tetsuo Handa
> > wrote:
> > >
> > > On 2019/01/06 22:24, Dmitry Vyukov wrote:
> > > >> A report at 2019/01/05 10:08 from "no output from test machine (2)"
> > > >> (
Hi Linus,
Please pull the watchdog changes for the v4.21 release cycle.
This series contains:
* mt7621_wdt/rt2880_wdt: Fix compilation problem
* tqmx86: Fix a couple IS_ERR() vs NULL bugs
The output from git request-pull:
The
WMI drivers can if they have specified an array of struct wmi_device_id
use the MODULE_DEVICE_TABLE() macro to automatically generate the
appropriate MODULE_ALIAS() output.
Change all driver that have specified an array of struct wmi_device_id
to use MODULE_DEVICE_TABLE() instead of
This patchset adds WMI support to MODULE_DEVICE_TABLE().
[PATCH 1/3]: prepare struct wmi_device_id
[PATCH 2/3]: add support
[PATCH 3/3]: update existing drivers to use MODULE_DEVICE_TABLE()
Mattias Jacobsson (3):
platform/x86: wmi: move struct wmi_device_id to mod_devicetable.h
platform/x86:
In preparation for adding WMI support to MODULE_DEVICE_TABLE() move the
definition of struct wmi_device_id to mod_devicetable.h and inline
guid_string in the struct.
Changing guid_string to an inline char array changes the loop conditions
when looping over an array of struct wmi_device_id.
Add WMI support to MODULE_DEVICE_TABLE() by adding info about struct
wmi_device_id in devicetable-offsets.c and add a WMI entry point in
file2alias.c.
The type argument for MODULE_DEVICE_TABLE(type, name) is wmi.
Signed-off-by: Mattias Jacobsson <2...@mok.nu>
---
The idea of adding wmi support
Hi Christoph,
I have found a small workaround. If I add 'mem=3500M' to the boot
arguments then it detects the SATA hard disk and boots without any problems.
X5000> setenv bootargs root=/dev/sda2 console=ttyS0,115200 mem=3500M
Cheers,
Christian
On 19 January 2019 at 12:40PM, Christian
> Jeremy Linton hat am 18. Januar 2019 um 23:22
> geschrieben:
>
>
> On 01/18/2019 12:05 PM, Stefan Wahren wrote:
> > Hi,
> >
> > ...
> >
> > a snippet or a new version would be nice
>
> Sure, I've got another version, to be posted soon (probably Tue of next
> week).
>
> In the
On Tue, Jan 15, 2019 at 7:17 PM Christoph Hellwig wrote:
>
> On Mon, Jan 07, 2019 at 09:40:47PM +0530, Anup Patel wrote:
> > From: Anup Patel
> >
> > This patch implements compile-time virtual to physical
> > mappings. These compile-time fixed mappings can be used
> > by earlycon, ACPI, and
On Sat, Jan 19, 2019 at 12:32 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:2339e91d0e66 Merge tag 'media/v5.0-1' of git://git.kernel...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=175f2638c0
> kernel
Hi Christoph,
I bought a USB null modem RS-232 serial cable today so I was able to get
some SATA error messages.
Error messages:
[ 13.468538] fsl-sata ffe22.sata: Sata FSL Platform/CSB Driver init
[ 13.475106] fsl-sata ffe22.sata: failed to start port 0 (errno=-12)
[ 13.481736]
Hi Mark,
Sorry, I forgot to mention that the patch for EC command definition
has been already merged in upstream, but not in Mark's for-next tree
yet.
c1f3375be60c mfd: cros_ec: Add commands to control codec
This is needed.
Thanks!
On Sat, Jan 19, 2019 at 7:34 PM Cheng-Yi Chiang wrote:
>
>
Add documentation for Chrome EC codec driver.
Signed-off-by: Cheng-Yi Chiang
---
Change in v4:
- Add a property max-dmic-gain so we can configure maximum gain on dmic.
- Add Guenter to the reviewer list.
.../bindings/sound/google,cros-ec-codec.txt | 26 +++
MAINTAINERS
Add a codec driver to control ChromeOS EC codec.
Use EC Host command to enable/disable I2S recording and control other
configurations.
Signed-off-by: Cheng-Yi Chiang
---
Changes in v4:
- Fix Kconfig that SND_SOC_CROS_EC_CODEC should depend on MFD_CROS_EC.
- Remove usage of MAX_GAIN.
- Add
Hello,
syzbot found the following crash on:
HEAD commit:2339e91d0e66 Merge tag 'media/v5.0-1' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=175f2638c0
kernel config: https://syzkaller.appspot.com/x/.config?x=abc3dc9b7a900258
Hi Martyn,
Am 18.01.19 um 20:48 schrieb Martyn Welch:
> Add vendor prefix "catalyst" for Catalyst Semiconductor which is
> already in use but undocumented.
>
> Signed-off-by: Martyn Welch
> Reviewed-by: Rob Herring
> ---
>
> Changes in v2: None
>
>
Commit ae7c8cba3221 ("platform/x86: ideapad-laptop: add lenovo RESCUER
R720-15IKBN to no_hw_rfkill_list") added
DMI_MATCH(DMI_BOARD_NAME, "80WW")
for Lenovo RESCUER R720-15IKBN.
But DMI_BOARD_NAME does not match 80WW on Lenovo RESCUER R720-15IKBN,
thus cause Wireless LAN still be hard
On Friday, January 18, 2019, Alan Cox wrote:
>
> > This is going to be a mammoth task. The alternatives are to continue
> > as things are, which is a mess that cannot be cleaned up by either of
> > (mutually exclusive) hardware or software alone.
> >
> > Thoughts and feedback appreciated.
>
> You
as you are already in a tasklet, it is unnecessary to call
spin_lock_bh, because softirq already disable BH.
Signed-off-by: Zhiwei Jiang
---
drivers/net/wireless/ath/ath9k/htc_drv_txrx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Tue, Jan 15, 2019 at 7:17 PM Christoph Hellwig wrote:
>
> On Mon, Jan 07, 2019 at 09:40:47PM +0530, Anup Patel wrote:
> > From: Anup Patel
> >
> > This patch implements compile-time virtual to physical
> > mappings. These compile-time fixed mappings can be used
> > by earlycon, ACPI, and
On Tue, Jan 15, 2019 at 7:14 PM Christoph Hellwig wrote:
>
> On Mon, Jan 07, 2019 at 09:40:45PM +0530, Anup Patel wrote:
> > From: Anup Patel
> >
> > The setup_bootmem() mainly populates memblocks and does
> > early memory reservations. The right location for this
> > function is mm/init.c.
> >
On Tue, Jan 15, 2019 at 7:14 PM Christoph Hellwig wrote:
>
> On Mon, Jan 07, 2019 at 09:40:44PM +0530, Anup Patel wrote:
> > From: Anup Patel
> >
> > We should setup init_mm before doing parse_early_param()
> > in setup_arch() to be consistent with setup_arch() of
> > other architectures such as
Rob Herring writes:
> Commit 8ce5f8415753 ("of: Remove struct device_node.type pointer")
> removed struct device_node.type pointer, but the conversion to use
> of_node_is_type() accessor was missed in chrp_init_IRQ().
>
> Fixes: 8ce5f8415753 ("of: Remove struct device_node.type pointer")
>
On Sat, Jan 19, 2019 at 02:28:00AM -0800, Christoph Hellwig wrote:
> This seems like a pretty horrible idea and waste of kernel memory.
It's only a waste if you want it to be a waste, i.e. if you load the
kernel module.
This really isn't any different from how /proc/config.gz works.
> Just add
On Tue, Jan 15, 2019 at 7:13 PM Christoph Hellwig wrote:
>
> On Mon, Jan 07, 2019 at 09:40:43PM +0530, Anup Patel wrote:
> > From: Anup Patel
> >
> > We move free_initrd_mem() to kernel/setup.c so that all initrd
> > related functions are in one place.
> >
> > Signed-off-by: Anup Patel
>
>
On 01/19/2019 02:03 AM, shuah wrote:
> On 1/18/19 2:54 PM, shuah wrote:
>> On 1/18/19 1:36 AM, Hans Verkuil wrote:
>>> On 12/18/18 6:59 PM, sh...@kernel.org wrote:
From: Shuah Khan
Media Device Allocator API to allows multiple drivers share a media
device.
This API
> > as far as I understand this code, freezable_schedule() avoids blocking the
> > freezer during the schedule() call, but in the end try_to_freeze() is still
> > called so the result is the same, right?
> > I wonder why wait_event_freezable is not calling freezable_schedule().
>
> It could be
This seems like a pretty horrible idea and waste of kernel memory.
Just add support to kbuild to store a compressed archive in initramfs
and unpack it in the right place.
On Fri, Jan 18, 2019 at 10:37:46AM -0800, Liam Mark wrote:
> Add support for configuring dma mapping attributes when mapping
> and unmapping memory through dma_buf_map_attachment and
> dma_buf_unmap_attachment.
>
> Signed-off-by: Liam Mark
And who is going to decide which ones to pass? And who
Christophe Leroy writes:
> The purpose of this serie is to activate CONFIG_THREAD_INFO_IN_TASK which
> moves the thread_info into task_struct.
>
> Moving thread_info into task_struct has the following advantages:
> - It protects thread_info from corruption in the case of stack
> overflows.
> -
On 18/01/2019 18:38, Qian Cai wrote:
> On 1/18/19 12:05 PM, Marc Gonzalez wrote:
>
>> On 18/01/2019 17:14, Qian Cai wrote:
>>
>>> This looks like something different from the original "invalid PFNs from
>>> pfn_to_online_page()" issue. What's your .config ?
>>
>> Here's my defconfig:
>>
>> #
On Fri, Jan 18, 2019 at 12:31:34PM -0800, Laura Abbott wrote:
> I thought about doing that, the problem is it becomes an ABI break for
> existing users which I really didn't want to do again. If it
> ends up being the last thing we do before moving out of staging,
> I'd consider doing it.
This is
On Fri, Jan 18, 2019 at 02:46:53PM -0500, Josef Bacik wrote:
> On Fri, Jan 18, 2019 at 07:44:03PM +0100, Andrea Righi wrote:
> > On Fri, Jan 18, 2019 at 11:35:31AM -0500, Josef Bacik wrote:
> > > On Fri, Jan 18, 2019 at 11:31:24AM +0100, Andrea Righi wrote:
> > > > This is a redesign of my old
On Fri, 18 Jan 2019 at 22:30, Heiner Kallweit wrote:
>
> On 18.01.2019 21:58, Heiner Kallweit wrote:
> > On 18.01.2019 09:48, Krzysztof Kozlowski wrote:
> >> On Fri, 18 Jan 2019 at 09:39, Krzysztof Kozlowski wrote:
> >>>
> >>> Hi,
> >>>
> >>> On today's next (next-20190118) my Colibri VF50 board
On Fri, Jan 18, 2019 at 05:05:59PM -0700, Logan Gunthorpe wrote:
> However, this doesn't create the IOVA entries necessary for addresses
> mapped this way to work when the IOMMU is enabled. Thus, when the
> IOMMU is enabled, drivers relying on dma_map_resource() will trigger
> DMAR errors. We see
resend this email.
On 2019-01-18 08:21, Kees Cook wrote:
> On Thu, Jan 17, 2019 at 4:15 PM Kees Cook wrote:
>>
>> On Mon, Jan 7, 2019 at 4:01 AM liaoweixiong
>> wrote:
>>>
>>> It is a sample for pstore_blk, using general ram rather than block device.
>>> According to pstore_blk, the data will
On 2019-01-18 08:21, Kees Cook wrote:
> On Thu, Jan 17, 2019 at 4:15 PM Kees Cook wrote:
>>
>> On Mon, Jan 7, 2019 at 4:01 AM liaoweixiong
>> wrote:
>>>
>>> It is a sample for pstore_blk, using general ram rather than block device.
>>> According to pstore_blk, the data will be saved to ram
On 2019-01-18 08:15, Kees Cook wrote:
> On Mon, Jan 7, 2019 at 4:01 AM liaoweixiong
> wrote:
>>
>> It is a sample for pstore_blk, using general ram rather than block device.
>> According to pstore_blk, the data will be saved to ram buffer if not
>> register device path and apis for panic. So, it
On Fri, Jan 18, 2019 at 08:09:07PM +0100, Jann Horn wrote:
> Hi!
>
> When a line discipline doesn't have a ->receive_buf handler, tiocsti()
> attempts to call a NULL pointer. Both tty_n_tracesink and
> spk_ttyio_ldisc_ops don't have such a handler.
>
> To reproduce, build a kernel with
Hi Bartosz,
On Fri, Jan 18, 2019 at 02:42:43PM +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Add support for the push- and slide-button events for max77650.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> drivers/input/misc/Kconfig | 9 ++
>
The NXP pcf8523 supports two different xtal load capacitance
- 7000fF (7pF)HW default
- 12500fF (12.5pF) Minimum power consumption, driver default
To obtain a precise RTC the pcf8523 must be configured
with the correct capacitance load of the xtal.
Add a property to specify the xtal
On Fri, Jan 18, 2019 at 01:08:02PM -0800, Dan Williams wrote:
> On Thu, Jan 17, 2019 at 3:41 AM Rafael J. Wysocki wrote:
> >
> > On Wed, Jan 16, 2019 at 6:59 PM Keith Busch wrote:
> > >
> > > Add entries for memory initiator and target node class attributes.
> > >
> > > Signed-off-by: Keith
Add support for specifying the xtal load capacitance in the DT node.
The pcf85063 supports xtal load capacitance of 7pF or 12.5pF.
If the rtc has the wrong configuration the time will
drift several hours/week.
The driver use the default value 7pF.
The DT may specify either 7000fF or 12500fF.
When dealing with capacitance of 0.5 pF then
a smaller unit is preferred.
Add femtofarads to deal with this.
Signed-off-by: Sam Ravnborg
Reviewed-by: Rob Herring
Cc: Mark Rutland
Cc: Alessandro Zummo
Cc: Alexandre Belloni
---
Documentation/devicetree/bindings/property-units.txt | 1 +
1
Respin of patchset on top of v5.0-rc2 with feedback addressed (thanks!)
Introduce a new generic property "quartz-load-femtofarad"
to specify the quartz load.
The default value is selected to match the current Linux
drivers, so there are no behavior changes if a binding do not
specify the
The quartz-load-femtofarads are relevant for
several users. Add it as a common property in rtc.
Note that valid values and default values must be documented.
Signed-off-by: Sam Ravnborg
Suggested-by: Rob Herring
Cc: Alessandro Zummo
Cc: Alexandre Belloni
Cc: Rob Herring
Cc: Mark Rutland
---
Add support for specifying the xtal load capacitance in the DT node.
The pcf8523 supports xtal load capacitance of 7pF or 12.5pF.
If the rtc has the wrong configuration the time will
drift several hours/week.
The driver use the default value 12.5pF.
The DT may specify either 7000fF or 12500fF.
The NXP pcf85063 supports two different xtal load capacitance
- 7000fF (7pF)HW default, Linux driver default
- 12500fF (12.5pF) Minimum power consumption
To obtain a precise RTC the pcf85063 must be configured
with the correct capacitance load of the xtal.
Add a property to specify the xtal
On 2019-01-18 08:12, Kees Cook wrote:
> On Mon, Jan 7, 2019 at 4:01 AM liaoweixiong
> wrote:
>>
>> pstore_blk is similar to pstore_ram, but dump log to block devices
>> rather than persistent ram.
>>
>> Why should we need pstore_blk?
>> 1. Most embedded intelligent equipment have no persistent
Hello my dear,
I'm 25 years old girl a nurse by profession:I want to come to your country and
start a better life with my late father's $8.5million as i want to stay away
from my wicked step mother.
Yours
Dr. Aliane
The patch below was just applied to my tree, hopefully ti fixes this
issue.
Yes, it cures both the HP A500 (parisc) and HP RX2620 (ia64) that I also found
breaking meanwhile.
--
Meelis Roos
The use of drmP.h is discouraged and removal of it from
drm_modeset_helper.h caused kirin to fail to build.
This patch introduce the necessary fixes to prepare for the
drmP.h removal from drm_modeset_helper.h.
List of include files sorted alphabetically.
Build tested on arm x86 allmodconfig
The use of drmP.h is discouraged and removal of it from
drm_modeset_helper.h caused drm/stm to fail to build.
This patch introduce the necessary fixes to prepare for the
drmP.h removal from drm_modeset_helper.h.
Build tested on arm and x86 allmodconfig
v2:
- sort list of include files
With the removal of drmP.h from drm_modeset_helper.h
the drmP.h are no longer included by any include files
in include/drm.
The drmP.h file is thus only included explicit
either in .c files or in local .h files.
This makes the process of deleting the drmP.h includes easier
as we have a more local
The use of drmP.h is discouraged and removal of it from
drm_modeset_helper.h caused arcgpu to fail to build.
This patch introduce the necessary fixes to prepare for the
drmP.h removal from drm_modeset_helper.h.
List of include files sorted alphabetically.
Build tested on arm x86 and arm
The use of drmP.h is discouraged and removal of it from
drm_modeset_helper.h caused cdns to fail to build.
This patch introduce the necessary fixes to prepare for the
drmP.h removal from drm_modeset_helper.h.
Build tested on arm x86 and arm allmodconfig.
Signed-off-by: Sam Ravnborg
Cc: Andrzej
The use of drmP.h is discouraged and removal of it from
drm_modeset_helper.h caused rcar-du to fail to build.
This patch introduce the necessary fixes to prepare for the
drmP.h removal from drm_modeset_helper.h.
Build tested on arm x86 and arm allmodconfig.
Signed-off-by: Sam Ravnborg
Updated patchset, with merged patches removed.
Addressed Laurents feedback (sorted include files)
> From the original mail:
- drmP.h is now stripped down to include files
and forward declarations.
- All header files in include/drm/ no longer include drmP.h.
The series
On Fri, Jan 18, 2019 at 10:58:04PM +0100, Federico Vaga wrote:
> The link referred by the note can't be retrieved: this patch just
> remove that old note.
>
> Signed-off-by: Federico Vaga
> ---
> Documentation/process/stable-api-nonsense.rst | 3 +--
> 1 file changed, 1 insertion(+), 2
On Fri, Jan 18, 2019 at 05:55:43PM -0500, Joel Fernandes wrote:
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -549,6 +549,16 @@ config IKCONFIG_PROC
> This option enables access to the kernel configuration file
> through /proc/config.gz.
>
> +config IKHEADERS_PROC
> +
On Fri, Jan 18, 2019 at 05:55:43PM -0500, Joel Fernandes wrote:
> --- /dev/null
> +++ b/kernel/kheaders.c
> @@ -0,0 +1,74 @@
> +// SPDX-License-Identifier: GPL-2.0
Nice, but:
> +MODULE_LICENSE("GPL");
That means "GPL2+" (yeah, horrible, I know, we all get it wrong, look at
On Fri, Jan 18, 2019 at 02:29:31PM -0700, Shuah Khan wrote:
> From: Shuah Khan
>
> Fix vhci_urb_enqueue() to print error and return error instead of
> failing with WARN_ON.
>
> Signed-off-by: Shuah Khan
> ---
> drivers/usb/usbip/vhci_hcd.c | 6 --
> 1 file changed, 4 insertions(+), 2
On Fri, Jan 18, 2019 at 10:19:41AM +0100, Marcel Holtmann wrote:
> Hi Myungho,
>
> > In h4_recv(), if h4_recv_buf() returns error and h4_recv() is
> > asynchronously called again before setting rx_skb to NULL, ERR_PTR will
> > be dereferenced in h4_recv_buf(). Check return value in a local
On Fri, Jan 18, 2019 at 02:29:30PM -0700, Shuah Khan wrote:
> From: Shuah Khan
>
> Fix vep_free_request() to return when usb_ep and usb_request are null
> instead of calling WARN_ON.
>
> Signed-off-by: Shuah Khan
> ---
> drivers/usb/usbip/vudc_dev.c | 2 +-
> 1 file changed, 1 insertion(+), 1
This patch fixes an issue in cpumap.c when used with the
TOPOLOGY header. In some configurations, some NUMA nodes may
have no CPU (empty cpulist). Yet a cpumap map must be created
otherwise perf abort with an error. This patch handles this
case by creating a dummy map.
Before:
$ perf record -o -
On Fri, Jan 18, 2019 at 03:10:39PM -0800, Fred Klassen wrote:
> Some IPMI modules (e.g. ibmpex_msg_handler()) will have ipmi_usr_hdlr
> handlers that call ipmi_free_recv_msg() directly. This will essentially
> kfree(msg), leading to use-after-free.
>
> This does not happen in the ipmi_devintf
201 - 277 of 277 matches
Mail list logo
