Viele Grüße von mir. Wie geht es Ihnen heute? Verzeih mir, dass ich deinen
Frieden gestört habe, ich verstehe meine Herangehensweise vielleicht sehr
ungeschickt und unhöflich, bitte ich bitte, dass du mir verzeihst, ein
Eindringling zu sein. Ich bin Wesley mit Namen, ich bin aus dem Vereinigten
On Mon, Jul 16, 2018 at 12:30:05PM +0100, Mark Rutland wrote:
> Hi Ingo,
Sorry to ping, but are you happy to pick this up?
Mark.
> Are you happy to pick this series? Both Will and Peter are happy with v3, and
> since then I've only made a minor cleanup to the commit messages for patches
> 8-10 (
Hi all,
Changes since 20180720:
Dropped trees: xarray, ida (complex conflicts)
The drm-msm tree gained a conflict against the drm tree and a build
failure due to an interaction with the drm tree for which I added a
merge fix patch.
The kvm-arm tree gained a conflict against the arm64 tree.
The
Hi Sayali,
On 7/13/2018 3:22 PM, Sayali Lokhande wrote:
This change adds the use of devfreq to MMC.
Both eMMC and SD card will use it.
For some workloads, such as video playback, it isn't
necessary for these cards to run at high speed.
Running at lower frequency, for example 52MHz, in such
cases
Below is the list of build error/warning regressions/improvements in
v4.18-rc6[1] compared to v4.17[2].
Summarized:
- build errors: +2/-1
- build warnings: +222/-46421
JFYI, when comparing v4.18-rc6[1] to v4.18-rc5[3], the summaries are:
- build errors: +0/-104
- build warnings: +77/-63
On Wed, Jul 18, 2018 at 05:01:37PM -0700, Dave Hansen wrote:
> On 07/17/2018 04:20 AM, Kirill A. Shutemov wrote:
> > arch/x86/include/asm/mktme.h | 8 +
> > arch/x86/mm/init_64.c| 10 +
> > arch/x86/mm/mktme.c | 437 +++
> > 3 files changed, 455
>From the SD host controller version 4.0 on, SDHCI implementation either
is version 3 compatible or version 4 mode. This patch-set covers those
changes which are common for SDHCI 4.0 version, regardless of whether
they are used with SD or eMMC storage devices.
This patchset also added a new sdhci
According to the SD host controller specification version 4.10, when
Host Version 4 is enabled, SDMA uses ADMA System Address register
(05Fh-058h) instead of using SDMA System Address register to
support both 32-bit and 64-bit addressing.
Signed-off-by: Chunyan Zhang
---
drivers/mmc/host/sdhci.c
ADMA2 64-bit addressing support is divided into V3 mode and V4 mode.
So there are two kinds of descriptors for ADMA2 64-bit addressing
i.e. 96-bit Descriptor for V3 mode, and 128-bit Descriptor for V4
mode. 128-bit Descriptor is aligned to 8-byte.
For V4 mode, ADMA2 64-bit addressing is enabled vi
For SD host controller version 4.00 or later ones, there're two
modes of implementation - Version 3.00 compatible mode or
Version 4 mode. This patch introduced an interface to enable
v4 mode.
Signed-off-by: Chunyan Zhang
---
drivers/mmc/host/sdhci.c | 28
drivers/mm
From: Chunyan Zhang
This patch adds the initial support of Secure Digital Host Controller
Interface compliant controller found in some latest Spreadtrum chipsets.
This patch has been tested on the version of SPRD-R11 controller.
R11 is a variant based on SD v4.0 specification.
With this driver,
Dear Jörg,
On 07/20/18 14:31, Jörg Rödel wrote:
> On Tue, Jul 17, 2018 at 06:02:07PM +0200, Paul Menzel wrote:
>> $ dmesg
>> […]
>> [0.145696] calling pci_iommu_init+0x0/0x3f @ 1
>> [0.145719] AMD-Vi: Unable to write to IOMMU perf counter.
>
> This is likely a firmware issue. Either th
Host Controller Version 4.10 re-defines SDMA System Address register
as 32-bit Block Count for v4 mode, and SDMA uses ADMA System
Address register (05Fh-058h) instead if v4 mode is enabled. Also
when using 32-bit block count, 16-bit block count register need
to be set to zero.
Signed-off-by: Chuny
As SD Host Controller Specification v4.10 documents:
Host Controller Version 4.10 defines this "Auto CMD Auto Select" mode.
Selection of Auto CMD depends on setting of CMD23 Enable in the Host
Control 2 register which indicates whether card supports CMD23. If CMD23
Enable =1, Auto CMD23 is used and
From: Chunyan Zhang
This patch adds the device-tree binding documentation for Spreadtrum
SDHCI driver.
Signed-off-by: Chunyan Zhang
---
.../devicetree/bindings/mmc/sdhci-sprd.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/
On Thu, Jul 19, 2018 at 12:21:44AM +0200, Thomas Gleixner wrote:
> On Tue, 17 Jul 2018, Kirill A. Shutemov wrote:
>
> > Per-KeyID direct mappings require changes into how we find the right
> > virtual address for a page and virt-to-phys address translations.
> >
> > page_to_virt() definition over
On Fri, 20 Jul 2018, Kamalesh Babulal wrote:
> livepatch module author can pass module name/old function name with more
> than the defined character limit. With obj->name length greater than
> MODULE_NAME_LEN, the livepatch module gets loaded but waits forever on
> the module specified by obj->nam
> On Jul 22, 2018, at 20:16, Souptick Joarder wrote:
>
> Use new return type vm_fault_t for page_mkwrite
> and fault handler.
>
> vmf_error() is the newly introduce inline function
> in 4.17
>
> Signed-off-by: Souptick Joarder
> Reviewed-by: Matthew Wilcox
> ---
> fs/ceph/addr.c | 62 +
On 07/23/2018 10:16 AM, Marc Kleine-Budde wrote:
> On 06/25/2018 09:59 AM, Marcel Ziswiler wrote:
>> From: Marcel Ziswiler
>>
>> CAN2 currently fails on probe as follows:
>>
>> mcp251x spi1.1: Probe failed, err=19
>>
>> Fix this by enabling input on pin mux of resp. SPI4 pins.
>>
>> Signed-off-by:
The host buffer depth is hardware specific so it's better to
handle it inside the me and txe hw modules. In me the depth
is read from register in txe it's a constant number.
The value is now retrieved via mei_hbuf_depth accessor,
while it replaces mei_hbuf_max_len.
Signed-off-by: Tomas Winkler
--
Cleanup conversions between slots and data.
Define MEI_SLOT_SIZE instead of using 4 or sizeof(u32) across
the source code.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/client.c | 2 +-
drivers/misc/mei/hw-me.c | 8
drivers/misc/mei/hw-txe.c | 8
drivers/misc/mei/mei_de
Wrap the mei header boilerplate initialization code in
mei_msg_hdr_init function. On the way remove 'completed'
field from mei_cl_cb structure as this information
is already included in the header and is local to particular
fragment.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/client.c |
On Sat, Jul 21, 2018 at 10:06:23AM +, Marcel Ziswiler wrote:
> On Sat, 2018-07-21 at 10:56 +0100, Mark Brown wrote:
> > > > > - dev_err(&pdev->dev, "no codec-sync GPIO
> > > > > supplied\n");
> > > > > + ret = ac97->sync_gpio;
> And here I assign ret with that return v
On Sat, Jul 21, 2018 at 07:23:31AM -0400, Peter Geis wrote:
> Re-sending due to email address typo.
>
> SW2 and SW4 use a shared table to provide voltage to the cpu core and
> devices on Tegra hardware.
> Added this table to the cpcap regulator driver as the first step to
> supporting this device
On 2018-07-21 05:07, kbuild test robot wrote:
Hi Girish,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on spi/for-next]
[also build test ERROR on v4.18-rc5 next-20180720]
[if your patch is applied to the wrong git tree, please drop us a note
to help improve the syste
On Wed, Jun 20, 2018 at 10:32:52PM +0530, Srikar Dronamraju wrote:
> Since task migration under numa balancing can happen in parallel, more
> than one task might choose to move to the same node at the same time.
> This can cause load imbalances at the node level.
>
> The problem is more likely if
Am Dienstag, 17. Juli 2018, 18:06:06 CEST schrieb Enric Balletbo i Serra:
> Enable the Rockchip sound driver with MAX98357A/RT5514/DA7219 codecs
> needed for the Samsung Chromebook Plus.
>
> Signed-off-by: Enric Balletbo i Serra
applied all 5 for 4.19.
As Olof requested less granularity for def
On Mon, Jul 23, 2018 at 10:53:29AM +0200, Geert Uytterhoeven wrote:
> On Sat, Jul 21, 2018 at 11:39 PM Adam Borowski wrote:
> > Technically, every console can be made to blink by drawing/clearing affected
> > characters a few times per second, but that'd be quite a waste of coding
> > time and ker
The A64 have a SID controller which consist on EFUSE (starting at 0x200)
and three registers to read/write the efuses.
Signed-off-by: Emmanuel Vadot
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64
The SID controller on H3 is one of it's kind (at least from what we
know).
Add a compatible string for it in the SoC dtsi.
Signed-off-by: Emmanuel Vadot
---
arch/arm/boot/dts/sun8i-h3.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm/boot/dts
The SID controller on H5 look the same as the one present in the A64.
But in case we find some difference one day at a compatible string
of it's own and a fallback to the A64 one.
Signed-off-by: Emmanuel Vadot
---
.../devicetree/bindings/nvmem/allwinner,sunxi-sid.txt| 1 +
arch/arm64/boo
On Mon, Jul 23, 2018 at 06:34:36PM +0800, shaochun chen wrote:
> I have a question: we will try_module_get in __netlink_dump_start(),
> but why we need to call try_module_get again in nft_netlink_dump_start ??
Because they refer to two different modules. nfnetlink is multiplexing
all netfilter su
Both H3 and H5 and a SID controller at the same address.
They are know to be different, the H5 one is the same as the A64 so add
a node in the common dtsi and we will override the compatible string in
the SoC dts.
Signed-off-by: Emmanuel Vadot
---
arch/arm/boot/dts/sunxi-h3-h5.dtsi | 4
1 f
On Mon 23-07-18 10:56:13, 禹舟键 wrote:
> Hi Michal
> OK, thanks. Is there any problems for V14?
I do not know of any. Both patches are sitting in the mmotm tree so they
should be merged in a forseeable future as long as nobody finds any
problems.
--
Michal Hocko
SUSE Labs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/07/18 05:46, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the kvm-arm tree got a conflict in:
>
> arch/arm64/include/asm/cpucaps.h
>
> between commit:
>
> 314d53d29798 ("arm64: Handle mismatched cache type")
>
> from t
Am Sonntag, 8. Juli 2018, 17:19:55 CEST schrieb Christoph Hellwig:
> Hi Masahiro,
>
> what do you think about the series below, which moves the includes
> of all the architecture independ Kconfig files to the top-level
> Kconfig instead of duplicating the includes in all architectures?
>
> Note t
On Fri 20-07-18 14:34:21, David Hildenbrand wrote:
> The reserved bit once was used to hinder pages from getting swapped. While
> this still works,
Does it? There is no single PageReserved check in the reclaim path. I
have no idea when we stopped checking but it must be lng ago.
> the semanti
Fix sparse warning: Using plain integer as NULL pointer
Signed-off-by: Laurence Rochfort
---
drivers/staging/most/dim2/dim2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/most/dim2/dim2.c b/drivers/staging/most/dim2/dim2.c
index fe90a7c..31fbc1a 100644
---
Am Dienstag, den 24.07.2018, 01:46 +0800 schrieb Robin Gong:
> If multi-bds used in one transfer, all bds should be consisten
> memory.To easily follow it, enlarge the dma pool size into 20 bds,
> and it will report error if the number of bds is over than 20. For
> dmatest, the max count for single
On Wed, Jun 20, 2018 at 10:32:54PM +0530, Srikar Dronamraju wrote:
> Currently resetting the migrate rate limit is under a spinlock.
> The spinlock will only serialize the migrate rate limiting and something
> similar can actually be achieved by a simpler xchg.
You're again not explaining things r
[v5]
* Initialize pll config before assigining l/alpha values for
pll configure.
* Add module description.
[v4]
* Add comments for the RCGs/CBCRs using the CLK_GET_RATE_NOCACHE flag.
[v3]
* Move frequency table macro to common file,
add the patch along to maintain dependency.
Add support for the display clock controller found on SDM845
based devices. This would allow display drivers to probe and
control their clocks.
Signed-off-by: Taniya Das
---
drivers/clk/qcom/Kconfig | 10 +
drivers/clk/qcom/Makefile| 1 +
drivers/clk/qcom/dispcc-sdm845.c | 687
On Mon, 2018-07-23 at 11:41 +0200, Lucas Stach wrote:
> As this doesn't depend on any other patch in this series, I think it
> would be fine if Philipp takes this patch through the reset tree.
>
> Regards,
> Lucas
>
> Am Freitag, den 20.07.2018, 15:47 +0300 schrieb Leonard Crestez:
> > Right now
Hi Adam,
On Mon, Jul 23, 2018 at 12:42 PM Adam Borowski wrote:
> On Mon, Jul 23, 2018 at 10:53:29AM +0200, Geert Uytterhoeven wrote:
> > On Sat, Jul 21, 2018 at 11:39 PM Adam Borowski wrote:
> > > Technically, every console can be made to blink by drawing/clearing
> > > affected
> > > character
The new format will be called V4L2_PIX_FMT_Y10P.
It is similar to the V4L2_PIX_FMT_SBGGR10P family formats
but V4L2_PIX_FMT_Y10P is a grayscale format.
Signed-off-by: Todor Tomov
---
Documentation/media/uapi/v4l/pixfmt-y10p.rst | 33
Documentation/media/uapi/v4l/yuv-
The code will be called MEDIA_BUS_FMT_Y10_2X8_PADHI_LE.
It is similar to MEDIA_BUS_FMT_SBGGR10_2X8_PADHI_LE
but MEDIA_BUS_FMT_Y10_2X8_PADHI_LE describes grayscale
data.
Signed-off-by: Todor Tomov
---
Documentation/media/uapi/v4l/subdev-formats.rst | 72 +
include/uapi/lin
From: Sakari Ailus
These formats are compressed 14-bit raw bayer formats with four different
pixel orders. They are similar to 10-bit variants. The formats added by
this patch are
V4L2_PIX_FMT_SBGGR14P
V4L2_PIX_FMT_SGBRG14P
V4L2_PIX_FMT_SGRBG14P
V4L2_PIX_FMT_SRGGB
On Mon, Jul 23, 2018 at 10:32:58AM +0100, Ben Dooks wrote:
>
>
> On 2018-07-23 09:50, Peter De Schrijver wrote:
> >On Fri, Jul 20, 2018 at 02:45:26PM +0100, Ben Dooks wrote:
> >>The host1x clock according to both tegra2 and tegra3 manuals is
> >>an 8bit divider with lsb being fractional. This is
Secure keys are derieved using CAAM crypto block.
Secure keys derieved are the random number symmetric keys from CAAM.
Blobs corresponding to the key are formed using CAAM. User space
will only be able to view the blob of the key.
Signed-off-by: Udit Agarwal
Reviewed-by: Sahil Malhotra
---
Chan
Encrypted keys can use secure key-type as master key along with
trusted/user keys.
Secure key as master key uses, secure key type payload derieved
using CAAM hardware.
Signed-off-by: Udit Agarwal
Reviewed-by: Sahil Malhotra
---
MAINTAINERS | 1 +
security/key
* Peter Zijlstra [2018-07-23 12:38:30]:
> On Wed, Jun 20, 2018 at 10:32:52PM +0530, Srikar Dronamraju wrote:
> > Since task migration under numa balancing can happen in parallel, more
> > than one task might choose to move to the same node at the same time.
> > This can cause load imbalances at t
On Thu, Jul 19, 2018 at 11:24 PM, Rishabh Bhatnagar
wrote:
> Drivers that are registered at an initcall level may have to
> wait until late_init before the probe deferral mechanism can
> retry their probe functions. It is possible that their
> dependencies were resolved much earlier, in some cases
On Mon, Jul 23, 2018 at 09:40:36AM +0200, Dmitry Vyukov wrote:
> On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote:
> > Hi all-
> >
> > It would be really nice to make KASAN compatible with VMAP_STACK.
> > Both are valuable memory debugging features, and the fact that you
> > can't use both i
To prepare for handling /proc/pid/smaps_rollup differently from /proc/pid/smaps
factor out vma mem stats gathering from show_smap() - it will be used by both.
Signed-off-by: Vlastimil Babka
---
fs/proc/task_mmu.c | 55 ++
1 file changed, 31 insertions(
The /proc/pid/smaps_rollup file is currently implemented via the
m_start/m_next/m_stop seq_file iterators shared with the other maps files,
that iterate over vma's. However, the rollup file doesn't print anything
for each vma, only accumulate the stats.
There are some issues with the current code
Commit b76437579d13 ("procfs: mark thread stack correctly in proc//maps")
introduced differences between /proc/PID/maps and /proc/PID/task/TID/maps to
mark thread stacks properly, and this was also done for smaps and numa_maps.
However it didn't work properly and was ultimately removed by commit
b1
The recent regression in /proc/pid/smaps made me look more into the code.
Especially the issues with smaps_rollup reported in [1] as explained in
Patch 4, which fixes them by refactoring the code. Patches 2 and 3 are
preparations for that. Patch 1 is me realizing that there's a lot of
boilerplate l
To prepare for handling /proc/pid/smaps_rollup differently from /proc/pid/smaps
factor out from show_smap() printing the parts of output that are common for
both variants, which is the bulk of the gathered memory stats.
Signed-off-by: Vlastimil Babka
---
fs/proc/task_mmu.c | 51 +
> If you maybe write that like:
>
> if (time_after(jiffies, next_window) &&
> xchg(&pgdat->numabalancing_migrate_nr_pages, 0UL)) {
>
> do {
> next_window += interval;
> } while (unlikely(time_after(jiffies, next_window)));
>
>
This patch series adds a driver and device tree documentation binding
for the camera clock controller on some Qualcomm Technologies, Inc, SoCs
such as SDM845. This would allow camera drivers to probe and control their
clocks.
Amit Nischal (2):
dt-bindings: clock: Introduce QCOM Camera clock bind
Add device tree bindings for camera clock controller for
Qualcomm Technology Inc's SDM845 SoCs.
Signed-off-by: Amit Nischal
---
.../devicetree/bindings/clock/qcom,camcc.txt | 18
include/dt-bindings/clock/qcom,camcc-sdm845.h | 116 +
2 files changed, 134 inse
Add support for the camera clock controller found on SDM845
based devices. This would allow camera drivers to probe and
control their clocks.
Signed-off-by: Amit Nischal
---
drivers/clk/qcom/Kconfig|8 +
drivers/clk/qcom/Makefile |1 +
drivers/clk/qcom/camcc-sdm845.c | 1736
Vitaly Kuznetsov writes:
> Changes since v3 [Roman Kagan]:
> - Don't use vcpu_id in kvm_make_vcpus_request_mask to avoid dealing with
> sparse CPU masks.
> - Create get_vcpu_idx_by_vpidx() and use it in get_vcpu_by_vpidx() and
> kvm_hv_flush_tlb().
>
> Using hypercall for sending IPIs is fast
On 2018-07-23 12:12, Peter De Schrijver wrote:
On Mon, Jul 23, 2018 at 10:32:58AM +0100, Ben Dooks wrote:
On 2018-07-23 09:50, Peter De Schrijver wrote:
>On Fri, Jul 20, 2018 at 02:45:26PM +0100, Ben Dooks wrote:
>>The host1x clock according to both tegra2 and tegra3 manuals is
>>an 8bit di
On Monday, 23 July 2018 11:28:25 MSK Ben Dooks wrote:
> On 2018-07-22 12:55, Dmitry Osipenko wrote:
> > On Friday, 20 July 2018 16:45:30 MSK Ben Dooks wrote:
> >> The 2D and 3D clocks have an IDLE field in bits 15:8 so add these
> >> clocks by making a 2D and 3D mux, and split the divider into the
Vitaly Kuznetsov writes:
> Changes since v1 [Liran Alon]:
> - Split PATCH2 into two.
> - Add a comment explaining eVMCS versioning.
> - Convert evmcs_needs_write() to inline function.
> - Drop 'unlikely' in vmx_vcpu_run().
> - Add Reviewed-by tags.
>
> Description:
>
> This is an initial implemen
On Wednesday, July 18, 2018 11:51:59 PM CEST Srinivas Pandruvada wrote:
> On HWP platforms with Turbo 3.0, the HWP capability max ratio shows the
> maximum ratio of that core, which can be different than other cores. If
> we show the correct maximum frequency in cpufreq sysfs via
> cpuinfo_max_freq
On 2018-07-23 12:33, Dmitry Osipenko wrote:
On Monday, 23 July 2018 11:28:25 MSK Ben Dooks wrote:
On 2018-07-22 12:55, Dmitry Osipenko wrote:
> On Friday, 20 July 2018 16:45:30 MSK Ben Dooks wrote:
>> The 2D and 3D clocks have an IDLE field in bits 15:8 so add these
>> clocks by making a 2D a
Hello,
syzbot found the following crash on:
HEAD commit:6d93abaf4c5b Add linux-next specific files for 20180723
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10e02f0c40
dashboard link: https://syzkaller.appspot.com/bug?extid=9118f0a7ae77f4eee4a9
Hi all,
Commit
5b6f5ee0f97f ("s390 cio: Rewrite trace point in s390_cio_interrupt")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
pgpN8h42XIexR.pgp
Description: OpenPGP digital signature
jz4780-nemc use of_ functions, so it needs to depend on OF
This fix the following build failure on x86
drivers/memory/jz4780-nemc.c: In function ‘jz4780_nemc_num_banks’:
drivers/memory/jz4780-nemc.c:72:10: error: implicit declaration of function
‘of_read_number’ [-Werror=implicit-function-declara
On Mon, Jul 23, 2018 at 1:38 PM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:6d93abaf4c5b Add linux-next specific files for 20180723
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=10e02f0c40
On Mon, Jul 23, 2018 at 10:35:19AM +0200, Michal Hocko wrote:
> No, I do not think this is much better. Why do we need to separate those
> functions out? I think you are too focused on the current function
> without a broader context. Think about it. We have two code paths.
> Early initialization a
On Thursday, July 19, 2018 1:00:30 PM CEST Kai-Heng Feng wrote:
> This reverts commit 36904703aeeeb6cd31993f1353c8325006229f9a.
>
> Since commit 5a8361f7ecce ("ACPICA: Integrate package handling with
> module-level code"), acpi_gbl_execute_tables_as_methods is always true,
> so we can remove the q
On 07/20/2018 02:34 PM, David Hildenbrand wrote:
> Dumping tools (like makedumpfile) right now don't exclude reserved pages.
> So reserved pages might be access by dump tools although nobody except
> the owner should touch them.
Are you sure about that? Or maybe I understand wrong. Maybe it change
On 05/29/2018 10:26 PM, Dan Murphy wrote:
> The CAN error masks header file is in the
> include/uapi directory.
>
> Fix the path in the header to the correct location.
>
> Signed-off-by: Dan Murphy
Applied to linux-can-next.
Tnx,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde
On Mon, Jul 23, 2018 at 1:18 PM, Mark Rutland wrote:
> On Mon, Jul 23, 2018 at 09:40:36AM +0200, Dmitry Vyukov wrote:
>> On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote:
>> > Hi all-
>> >
>> > It would be really nice to make KASAN compatible with VMAP_STACK.
>> > Both are valuable memory d
On Mon, Jul 23, 2018 at 10:11 AM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 9:59 AM, syzbot
> wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x
On Mon, Jul 23, 2018 at 2:12 PM, Miklos Szeredi wrote:
> On Mon, Jul 23, 2018 at 10:11 AM, Dmitry Vyukov wrote:
>> On Mon, Jul 23, 2018 at 9:59 AM, syzbot
>> wrote:
>>> Hello,
>>>
>>> syzbot found the following crash on:
>>>
>>> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
>>> git tree: ups
On Mon, Jul 23, 2018 at 10:08:59AM +0200, David Woodhouse wrote:
> On Thu, 2018-07-19 at 10:09 -0700, Paul E. McKenney wrote:
> >
> > Of course, the real reason for the lack of fault on your part will not
> > because I believe I found the bug elsewhere, but instead because I will
> > be dropping y
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Quinn Tran
commit b5f3bc39a0e815a30005da246dd4ad47fd2f88ff upstream.
GPNFT command allocates 2 buffer for switch query. On completion, the same
buffers were freed using different size, instead
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: himanshu.madh...@cavium.com
commit d48cc67cd4406d589fdbfa8c7d51c86532f86feb upstream.
This patch fixes crash for FCoE adapter. Once driver initialization is
complete, firmware will start posti
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: OGAWA Hirofumi
commit 35033ab988c396ad7bce3b6d24060c16a9066db8 upstream.
In parse_options(), if match_strdup() failed, parse_options() leaves
opts->iocharset in unexpected state (i.e. still p
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit f3d737b6340b0c7bacd8bc751605f0ed6203f146 upstream.
The PCI SSID 1558:95e1 needs the same quirk for other Clevo P950
models, too. Otherwise no sound comes out of speakers.
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 39675f7a7c7e7702f7d5341f1e0d01db746543a0 upstream.
The SNDRV_RAWMIDI_IOCTL_PARAMS ioctl may resize the buffers and the
current code is racy. For example, the sequencer cli
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Vineet Gupta
commit af1fc5baa724c63ce1733dfcf855bad5ef6078e3 upstream.
This manifsted as strace segfaulting on HSDK because gcc was targetting
the accumulator registers as GPRs, which kernek w
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Liran Alon
commit 2307af1c4b2e0ad886f30e31739845322cbd328b upstream.
When eVMCS is enabled, all VMCS allocated to be used by KVM are marked
with revision_id of KVM_EVMCS_VERSION instead of rev
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Po-Hsu Lin
commit 9a6249d2a145226ec1b294116fcb08744cf7ab56 upstream.
Audio mute led does not work on HP ProBook 455 G5,
this can be fixed by using CXT_FIXUP_MUTE_LED_GPIO to support it.
BugLi
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: YOKOTA Hiroshi
commit 0fca97a29b83e3f315c14ed2372cfd0f9ee0a006 upstream.
This adds some required quirk when uses headset or headphone on
Panasonic CF-SZ6.
Signed-off-by: YOKOTA Hiroshi
Cc:
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Vitaly Kuznetsov
commit b062b794c7831a70bda4dfac202c1a9418e06ac0 upstream.
When we switched from doing rdmsr() to reading FS/GS base values from
current->thread we completely forgot about lega
On 07/23/2018 03:04 AM, Kirill A. Shutemov wrote:
> On Wed, Jul 18, 2018 at 05:01:37PM -0700, Dave Hansen wrote:>> Please make an
> effort to refactor this to reuse the code that we already
>> have to manage the direct mapping. We can't afford 455 new lines of
>> page table manipulation that nobo
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit 9432a3175770e06cb83eada2d91fac90c977cb99 upstream.
A comment warning against this bug is there, but the code is not doing what
the comment says. Therefore it is possible
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Chuck Anderson
commit 36eb8ff672faee83ccce60c191f0fef07c6adce6 upstream.
Crash dump shows following instructions
crash> bt
PID: 0 TASK: be412480 CPU: 0 COMMAND: "swapper/0"
#
This is the start of the stable review cycle for the 4.17.10 release.
There are 63 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.
Responses should be made by Wed Jul 25 12:24:28 UTC 2018.
Anything receiv
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Brodkin
commit 64234961c145606b36eaa82c47b11be842b21049 upstream.
We used to have pre-set CONFIG_INITRAMFS_SOURCE with local path
to intramfs in ARC defconfigs. This was quite convenien
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Tyler Hicks
[ Upstream commit 70ba5b6db96ff7324b8cfc87e0d0383cf59c9677 ]
The low and high values of the net.ipv4.ping_group_range sysctl were
being silently forced to the default disabled stat
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Lyude Paul
commit 37afe55b4ae0600deafe7c0e0e658593c4754f1b upstream.
When MST and atomic were introduced to nouveau, another structure that
could contain a drm_connector embedded within it was
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
[ Upstream commit 83ed7d1fe2d2d4a11b30660dec20168bb473d9c1 ]
My randconfig builds came across an old missing dependency for ILA:
ERROR: "dst_cache_set_ip6" [net/ipv6/ila/ila.ko]
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
[ Upstream commit 169dc027fb02492ea37a0575db6a658cf922b854 ]
The rol32 call is currently rotating hash but the rol'd value is
being discarded. I believe the current code is inco
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 5292221d6ddfed75e5b46cd42237a677094b99f3 upstream.
This reverts commit 018d82e5f02ef3583411bcaa4e00c69786f46f19.
This breaks DDC in certain cases. Revert for 4.18 and pre
101 - 200 of 944 matches
Mail list logo
