On Mon, Jul 08, 2019 at 12:37:06PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d58b5ab9 Add linux-next specific files for 20190708
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=12
On Mon, Jul 08, 2019 at 10:19:41PM +0200, Geert Uytterhoeven wrote:
> Yeah, it started when I queued up the DMA rework.
> I didn't double-check when Greg said it was OK for him, as it wouldn't affect
> Coldfire or mmu. Sorry for that.
> And that has just been pulled by Linus... Oops...
The fix
On Mon, Jul 08, 2019 at 09:26:29PM +0200, Jiri Pirko wrote:
> Mon, Jul 08, 2019 at 07:27:29PM CEST, mkube...@suse.cz wrote:
> >
> >There are two reasons for this design. First is to reduce the number of
> >requests needed to get the information. This is not so much a problem of
> >ethtool itself;
On Mon, Jul 08, 2019 at 04:29:22PM +0100, Ben Hutchings wrote:
> On Mon, 2019-07-08 at 06:05 -0700, Luke Nowakowski-Krijger wrote:
> > Hello,
> >
> > I got 1 error when applying this patch series to the latest linux-3.16.y
> > stable branch
> >
> > fs/fuse/file.c:218:3: error: implicit
On Mon, 8 Jul 2019, Marco Elver wrote:
> This refactors common code of ksize() between the various allocators
> into slab_common.c: __ksize() is the allocator-specific implementation
> without instrumentation, whereas ksize() includes the required KASAN
> logic.
Acked-by: Christoph Lameter
Hi Günter,
CC Greg
On Mon, Jul 8, 2019 at 9:45 PM Guenter Roeck wrote:
> On Mon, Jul 08, 2019 at 09:13:02PM +0200, Geert Uytterhoeven wrote:
> > On Mon, Jul 8, 2019 at 7:06 PM Guenter Roeck wrote:
> > > I see the following build error in -next:
> > >
> > > kernel/dma/direct.o: In function
Den 08.07.2019 21:38, skrev Jason Gunthorpe:
On Mon, Jul 08, 2019 at 07:22:45PM +, Mark Bloch wrote:
On 7/8/19 11:47 AM, Dag Moxnes wrote:
Thanks Jason,
Regards,
Dag
Den 08.07.2019 19:50, skrev Jason Gunthorpe:
On Mon, Jul 08, 2019 at 01:16:24PM +0200, Dag Moxnes wrote:
Use
Booting today's linux-next starts to have several memory leaks. Looks like the
new xfs_rw_bdev() was introduced in the commit "xfs: use bios directly to read
and write the log recovery buffers".
https://patchwork.kernel.org/patch/10977673/
unreferenced object 0x888f595487c0 (size 184):
On Mon, 24 Jun 2019 14:46:20 +0200, Geert Uytterhoeven wrote:
> There is no need to cast "u64" to "unsigned long long" before printing
> it, as both types have been made identical on all architectures many
> years ago.
>
> Signed-off-by: Geert Uytterhoeven
> ---
> drivers/of/platform.c | 3 +--
Hi Andrew,
On Mon, Jul 08, 2019 at 09:48:34PM +0200, Andrew Lunn wrote:
> On Mon, Jul 08, 2019 at 12:24:58PM -0700, Matthias Kaehlcke wrote:
> > The LED behavior of some Realtek PHYs is configurable. Add the
> > property 'realtek,led-modes' to specify the configuration of the
> > LEDs.
> >
> >
On Mon, Jul 08, 2019 at 09:46:15PM +0200, Andrew Lunn wrote:
> On Mon, Jul 08, 2019 at 12:24:53PM -0700, Matthias Kaehlcke wrote:
> > Add the 'realtek,eee-led-mode-disable' property to disable EEE
> > LED mode on Realtek PHYs that support it.
> >
> > Signed-off-by: Matthias Kaehlcke
> > ---
> >
In commit 46d179525a1f ("mmc: dw_mmc: Wait for data transfer after
response errors.") we fixed a tuning-induced hang that I saw when
stress testing tuning on certain SD cards. I won't re-hash that whole
commit, but the summary is that as a normal part of tuning you need to
deal with transfer
On 2019-07-05 18:37:35, Roberto Sassu wrote:
> Commit c78719203fc6 ("KEYS: trusted: allow trusted.ko to initialize w/o a
> TPM") allows the trusted module to be loaded even a TPM is not found to
> avoid module dependency problems.
>
> Unfortunately, this does not completely solve the issue, as
On Mon, 8 Jul 2019, Linus Torvalds wrote:
> On Mon, Jul 8, 2019 at 2:22 AM Thomas Gleixner wrote:
> >
> > @@ -643,9 +644,11 @@ static unsigned long ptrace_get_debugreg(struct
> > task_struct *tsk, int n)
> > {
> > struct thread_struct *thread = >thread;
> > unsigned long val =
On Mon, Jul 08, 2019 at 12:24:58PM -0700, Matthias Kaehlcke wrote:
> The LED behavior of some Realtek PHYs is configurable. Add the
> property 'realtek,led-modes' to specify the configuration of the
> LEDs.
>
> Signed-off-by: Matthias Kaehlcke
Hi Matthias
Humm. I thought you were going to drop
On Mon, Jul 08, 2019 at 12:24:53PM -0700, Matthias Kaehlcke wrote:
> Add the 'realtek,eee-led-mode-disable' property to disable EEE
> LED mode on Realtek PHYs that support it.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> TODO: adapt PHY core to deal with optional compatible strings
Yes. Does
On 04.07.19 15:39, Andy Shevchenko wrote:
> On Thu, Jul 4, 2019 at 12:02 PM Florian Eckert wrote:
>>
>> This patchset adds the following changes to this pcengines-apuv2
>> platform device.
>>
>
> Before doing anything to this driver, what is the plan for previously
> upstreamed:
>
>
On Mon, Jul 08, 2019 at 09:13:02PM +0200, Geert Uytterhoeven wrote:
> Hi Günter,
>
> On Mon, Jul 8, 2019 at 7:06 PM Guenter Roeck wrote:
> > I see the following build error in -next:
> >
> > kernel/dma/direct.o: In function `dma_direct_alloc_pages':
> > direct.c:(.text+0x4d8): undefined
On 04.07.19 11:02, Florian Eckert wrote:
> On APUx we have also mpcie2/mpcie3 reset pins. To make it possible to reset
> the ports from the userspace, add the definition to this platform
> device. The gpio can then be exported by the legancy gpio subsystem to
> toggle the mpcie reset pin.
Are you
On 04.07.19 11:02, Florian Eckert wrote:
> Extend the apu2_leds definition to make the leds exportable via the
> legacy gpio subsystem.
What for ? The gpios are bound to LED devices as that's exactly what
they are: LEDs.
> Without this change the leds are not visible
> under "/sys/class/leds"
From: Arnd Bergmann
Date: Mon, 8 Jul 2019 14:48:23 +0200
> When CONFIG_OF is disabled, we get a harmless warning about the
> newly added variable:
>
> drivers/net/ethernet/cadence/macb_main.c:48:39: error: 'mgmt' defined but not
> used [-Werror=unused-variable]
> static struct
> -Original Message-
> From: Biwen Li
> Sent: Friday, July 5, 2019 5:18 AM
> To: a.zu...@towertech.it; alexandre.bell...@bootlin.com; Leo Li
>
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Xiaobo Xie
> ; Jiafei Pan ; Ran Wang
> ; Biwen Li
> Subject: [PATCH 1/2]
From: Jose Abreu
Date: Mon, 8 Jul 2019 14:26:28 +0200
> Ben Hutchings says:
> "This is the wrong place to change the queue mapping.
> stmmac_xmit() is called with a specific TX queue locked,
> and accessing a different TX queue results in a data race
> for all of that
From: Arnd Bergmann
Date: Mon, 8 Jul 2019 14:43:39 +0200
> On unusual page sizes, we get harmless warnings:
>
> drivers/net/ethernet/google/gve/gve_rx.c:283:6: error: unused variable
> 'pagecount' [-Werror,-Wunused-variable]
> drivers/net/ethernet/google/gve/gve_rx.c:336:1: error: unused
On 05.07.19 13:36, Florian Eckert wrote:
Hi,
> APU1 (PC-Engines) CPU "AMD G series T40E APU":> This is also an old design
> and is not recommend for new design>
(deprecated).> Also not many were produced and are in the field.> See
https://pcengines.ch/apu.htm
Yes, and I haven't been able to get
On Mon, Jul 08, 2019 at 07:22:45PM +, Mark Bloch wrote:
>
>
> On 7/8/19 11:47 AM, Dag Moxnes wrote:
> > Thanks Jason,
> >
> > Regards,
> > Dag
> >
> > Den 08.07.2019 19:50, skrev Jason Gunthorpe:
> >> On Mon, Jul 08, 2019 at 01:16:24PM +0200, Dag Moxnes wrote:
> >>> Use neighbour lock when
Hello,
syzbot found the following crash on:
HEAD commit:d58b5ab9 Add linux-next specific files for 20190708
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=123d6887a0
kernel config: https://syzkaller.appspot.com/x/.config?x=bf9882946ecc11d9
Hello,
syzbot found the following crash on:
HEAD commit:9d1bc24b bonding: validate ip header before check IPPROTO_..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=152fab25a0
kernel config: https://syzkaller.appspot.com/x/.config?x=e7c31a94f66cc0aa
Hello,
syzbot found the following crash on:
HEAD commit:537de0c8 ipv4: Fix NULL pointer dereference in ipv4_neigh_..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=14521cc3a0
kernel config: https://syzkaller.appspot.com/x/.config?x=90f5d2d9c1e7421c
On 7/8/19 12:02 PM, Alexander Duyck wrote:
> On Tue, 2019-06-25 at 13:24 -0700, Dave Hansen wrote:
>> I also don't see what the boundary has to do with aerated pages being on
>> the tail of the list. If you want them on the tail, you just always
>> list_add_tail() them.
>
> The issue is that
On Mon, Jul 8, 2019 at 12:09 PM Alexey Dobriyan wrote:
>
> Thomas Garnier wrote:
> > - "pushq $1f\n\t"
> > + "movabsq $1f, %q0\n\t"
> > + "pushq %q0\n\t"
> > "iretq\n\t"
> > UNWIND_HINT_RESTORE
> > "1:"
>
> Fake PIE.
On 7/4/19 10:46 AM, Josh Poimboeuf wrote:
> AMD and Intel both have serializing lfence (X86_FEATURE_LFENCE_RDTSC).
> They've both had it for a long time, and AMD has had it enabled in Linux
> since Spectre v1 was announced.
>
> Back then, there was a proposal to remove the serializing mfence
stable-rc/linux-4.14.y boot: 105 boots: 3 failed, 101 passed with 1
untried/unknown (v4.14.132-57-gb33dcbc2d8e5)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.132-57-gb33dcbc2d8e5/
Full Build Summary:
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-entry-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0d37dde70655be73575d011be1bffaf0e3b16ea9
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> timers-core-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/927ba67a63c72ee87d655e30183d1576c3717d3e
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-core-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2a1ccd31420a7b1acd6ca37b2bec2d723aa093e4
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-fpu-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ab2486a9ee3243c8342549f58a13cdfa9abb497a
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/223cea6a4f0552b86fb25e3b8bbd00469816cd7a
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> smp-hotplug-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e0e86b111bca6bbf746c03ec5cf3e6a61fa3f8e9
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-rslib-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/568521d058aaab18f01ac39d7a6ef00b75e5cc79
Thank you!
--
Deet-doot-dot, I am
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-apic-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0902d5011cfaabd6a09326299ef77e1c8735fb89
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/13324c42c1401ad838208ee1e98f3821fce1cd86
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-timers-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2f0f6503e37551eb8d8d5e4d27c78d28a30fed5a
Thank you!
--
Deet-doot-dot, I am
The pull request you sent on Thu, 4 Jul 2019 16:54:29 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-upstream
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/dfd437a257924484b144ee750e60affc95562c6d
Thank you!
--
Deet-doot-dot, I am a
On Mon, Jul 08, 2019 at 05:12:32PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.1.17 release.
> There are 96 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
The pull request you sent on Mon, 8 Jul 2019 10:22:54 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git s390-5.3-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1758feddb0f9751debdc865fefde94b45907c948
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Mon, 08 Jul 2019 09:05:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> core-debugobjects-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6b37754790067c9b25cf75fbf72b69edd6d7fffd
Thank you!
--
The pull request you sent on Mon, 8 Jul 2019 10:00:05 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
> tags/m68k-for-v5.3-tag1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/278ecbf027c3c559deb225f0cf53a23b7672dacf
Thank you!
--
Mon, Jul 08, 2019 at 09:26:29PM CEST, j...@resnulli.us wrote:
>Mon, Jul 08, 2019 at 07:27:29PM CEST, mkube...@suse.cz wrote:
>>On Wed, Jul 03, 2019 at 10:41:51AM +0200, Jiri Pirko wrote:
>>> Tue, Jul 02, 2019 at 04:52:41PM CEST, mkube...@suse.cz wrote:
>>> >On Tue, Jul 02, 2019 at 02:25:21PM
On 04.07.19 11:02, Florian Eckert wrote:
> * Add the gpio number, so the button subsystem can find the right gpio.
> * Change also the keycode from KEY_SETUP to KEY_RESTART, because it
> seems more expressive to me and in the Alix-Board, which is the
> predecessor, there isthis keycode defined
On Mon, Jul 08, 2019 at 01:51:30PM +0200, Radoslaw Burny wrote:
> fs: Fix the default values of i_uid/i_gid on /proc/sys inodes.
> Normally, the inode's i_uid/i_gid are translated relative to s_user_ns,
> but this is not a correct behavior for proc. Since sysctl permission
> check in test_perm is
On Thu 13 Jun 08:13 PDT 2019, Georgi Djakov wrote:
> The Qualcomm QCS404 platform has several buses that could be controlled
> and tuned according to the bandwidth demand.
>
> Reviewed-by: Bjorn Andersson
> Signed-off-by: Georgi Djakov
> ---
>
> v4:
> - Add the DT header into this patch.
> -
Mon, Jul 08, 2019 at 07:27:29PM CEST, mkube...@suse.cz wrote:
>On Wed, Jul 03, 2019 at 10:41:51AM +0200, Jiri Pirko wrote:
>> Tue, Jul 02, 2019 at 04:52:41PM CEST, mkube...@suse.cz wrote:
>> >On Tue, Jul 02, 2019 at 02:25:21PM +0200, Jiri Pirko wrote:
>> >> Tue, Jul 02, 2019 at 01:49:59PM CEST,
Add the 'realtek,eee-led-mode-disable' property to disable EEE
LED mode on Realtek PHYs that support it.
Signed-off-by: Matthias Kaehlcke
---
TODO: adapt PHY core to deal with optional compatible strings
Changes in v3:
- added entry for compatible string
- added compatible string to example
-
The Realtek RTL8211E allows customization of the PHY LED behavior,
like which LEDs are on for certain link speeds and which LEDs blink
when there is traffic. By default EEE LED mode is enabled, in which
a blinking LED is on for 400ms and off for 2s. This series adds
support for configuring the LED
EEE LED mode is enabled by default on the RTL8211E. Disable it when
the device tree property 'realtek,eee-led-mode-disable' exists.
The magic values to disable EEE LED mode were taken from the RTL8211E
datasheet, unfortunately they are not further documented.
Signed-off-by: Matthias Kaehlcke
Add the 'realtek,enable-ssc' property to enable Spread Spectrum
Clocking (SSC) on Realtek PHYs that support it.
Signed-off-by: Matthias Kaehlcke
---
Changes in v3:
- changed wording for supported PHY models
Changes in v2:
- patch added to the series (kind of, it already existed, but now
the
By default Spread-Spectrum Clocking (SSC) is disabled on the RTL8211E.
Enable it if the device tree property 'realtek,enable-ssc' exists.
Signed-off-by: Matthias Kaehlcke
---
TODO: DT validation
Changes in v3:
- use phydev_err() instead of dev_err()
Changes in v2:
- enable SSC in config_init()
The RTL8211E has extension pages, which can be accessed after
selecting a page through a custom method. Add a function to
modify bits in a register of an extension page and a helper for
selecting an ext page. Use rtl8211e_modify_ext_paged() in
rtl8211e_config_init() instead of doing things
The LED behavior of some Realtek PHYs is configurable. Add the
property 'realtek,led-modes' to specify the configuration of the
LEDs.
Signed-off-by: Matthias Kaehlcke
---
Changes in v3:
- added RTL8211E_LED_OFF to LED modes
- changed wording for supported PHY models
Changes in v2:
- patch added
Configure the RTL8211E LEDs behavior when the device tree property
'realtek,led-modes' is specified.
Signed-off-by: Matthias Kaehlcke
---
TODO: DT validation
Changes in v3:
- sanity check led-modes values
- set LACR bits in a more readable way
- use phydev_err() instead of dev_err()
- log an
On Mon, Jul 8, 2019 at 2:22 AM Thomas Gleixner wrote:
>
> @@ -643,9 +644,11 @@ static unsigned long ptrace_get_debugreg(struct
> task_struct *tsk, int n)
> {
> struct thread_struct *thread = >thread;
> unsigned long val = 0;
> + int index = n;
>
> if (n < HBP_NUM)
On 7/8/19 11:47 AM, Dag Moxnes wrote:
> Thanks Jason,
>
> Regards,
> Dag
>
> Den 08.07.2019 19:50, skrev Jason Gunthorpe:
>> On Mon, Jul 08, 2019 at 01:16:24PM +0200, Dag Moxnes wrote:
>>> Use neighbour lock when copying MAC address from neighbour data struct
>>> in dst_fetch_ha.
>>>
>>> When
On Mon, 8 Jul 2019 16:10:29 -0300
Thadeu Lima de Souza Cascardo wrote:
> On Fri, Mar 22, 2019 at 03:09:23PM -0400, Steven Rostedt wrote:
> > From: Steven Rostedt (VMware)
> >
> > Running the ftrace selftests on the latest kernel caused the
> > kprobe_eventname test to fail. It was due to the
On 08.07.19 20:06, Al Viro wrote:
> On Mon, Jul 08, 2019 at 06:52:14PM +0200, Christian Borntraeger wrote:
>
>> smp: Brought up 1 node, 1 CPU
>> Unable to handle kernel pointer dereference in virtual kernel address space
>> Failing address: 3a07 TEID: 3a070407
>> Fault in
8ddd2249bcb1d9974fb5d28] Merge tag
'for-linus-20190706' of git://git.kernel.dk/linux-block
git bisect good 46713c3d2f8da5e3d8ddd2249bcb1d9974fb5d28
# bad: [d58b5ab90ee7528126fd5833df7fc5bda8331ce8] Add linux-next specific files
for 20190708
git bisect bad d58b5ab90ee7528126fd5833df7fc5bda8331ce8
On 6/28/19 11:49 AM, David Howells wrote:
Add a security hook that allows an LSM to rule on whether a notification
message is allowed to be inserted into a particular watch queue.
The hook is given the following information:
(1) The credentials of the triggerer (which may be init_cred for a
Hi Günter,
On Mon, Jul 8, 2019 at 7:06 PM Guenter Roeck wrote:
> I see the following build error in -next:
>
> kernel/dma/direct.o: In function `dma_direct_alloc_pages':
> direct.c:(.text+0x4d8): undefined reference to `arch_dma_prep_coherent'
>
> Example: m68k:allnoconfig.
>
> Bisect log is
stable-rc/linux-4.9.y boot: 94 boots: 2 failed, 92 passed
(v4.9.184-102-gf075c4e9d730)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.184-102-gf075c4e9d730/
Full Build Summary:
stable-rc/linux-5.1.y boot: 108 boots: 3 failed, 105 passed
(v5.1.16-96-gadc3bfb5810c)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.1.y/kernel/v5.1.16-96-gadc3bfb5810c/
Full Build Summary:
stable-rc/linux-4.4.y boot: 100 boots: 4 failed, 95 passed with 1 conflict
(v4.4.184-73-g71b130d46805)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.184-73-g71b130d46805/
Full Build Summary:
stable-rc/linux-4.19.y boot: 100 boots: 2 failed, 98 passed
(v4.19.57-91-g7b63e70b83fc)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.57-91-g7b63e70b83fc/
Full Build Summary:
On Fri, Mar 22, 2019 at 03:09:23PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> Running the ftrace selftests on the latest kernel caused the
> kprobe_eventname test to fail. It was due to the test that searches for
> a function with at "dot" in the name and adding a probe to
Thomas Garnier wrote:
> - "pushq $1f\n\t"
> + "movabsq $1f, %q0\n\t"
> + "pushq %q0\n\t"
> "iretq\n\t"
> UNWIND_HINT_RESTORE
> "1:"
Fake PIE. True PIE looks like this:
81022d70 :
81022d70: 8c d0
On Mon, Jul 08, 2019 at 05:12:52PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.133 release.
> There are 56 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
On Mon, Jul 08, 2019 at 06:29:57PM +0300, Konstantin Khlebnikov wrote:
> After commit 991f61fe7e1d ("Blk-throttle: reduce tail io latency when iops
> limit is enforced") wait time could be zero even if group is throttled and
> cannot issue requests right now. As a result throtl_select_dispatch()
On Mon, Jul 08, 2019 at 02:56:18PM -0400, Steven Rostedt wrote:
> On Mon, 8 Jul 2019 15:19:33 -0300
> Thadeu Lima de Souza Cascardo wrote:
>
> > Check that the function is on available_filter_functions. If it's not,
> > mark the test as unresolved, instead of failing it.
> >
>
> Actually, I
Make it obvious how the gsm mux number relates to the virtual tty lines
by using helper function instead of shifting 6 bits.
Signed-off-by: Martin Hundebøll
---
drivers/tty/n_gsm.c | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/n_gsm.c
There is no reason to gues the line discipline number when it is
available from tty.h
Signed-off-by: Martin Hundebøll
---
Documentation/serial/n_gsm.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/serial/n_gsm.rst b/Documentation/serial/n_gsm.rst
index
Guessing the base tty for a gsm0710 multiplexed serial device is not
currently possible, which makes it racy to use with multiple modems.
Add a way to map the physical serial tty to its related mux devices
using a ioctl.
Signed-off-by: Martin Hundebøll
---
Documentation/serial/n_gsm.rst | 8
The n_gsm driver handles registration of /dev/gsmttyX nodes, so there's
no need to do mknod manually.
Signed-off-by: Martin Hundebøll
---
Documentation/serial/n_gsm.rst | 10 --
1 file changed, 10 deletions(-)
diff --git a/Documentation/serial/n_gsm.rst b/Documentation/serial/n_gsm.rst
On Tue, 2019-06-25 at 13:24 -0700, Dave Hansen wrote:
> On 6/19/19 3:33 PM, Alexander Duyck wrote:
> > Add a set of pointers we shall call "boundary" which represents the upper
> > boundary between the "raw" and "aerated" pages. The general idea is that in
> > order for a page to cross from one
Hi list,
NFS caching appears broken in 4.19.37.
The more cores/threads the easier to reproduce. Tested with identical
results on Ryzen 1600 and 1600X.
1. Mount an openwrt build tree over NFS v4
2. Run make -j `cat /proc/cpuinfo | grep vendor | wc -l` ; make clean in
a loop
3. Result after
On Mon, 8 Jul 2019 15:19:33 -0300
Thadeu Lima de Souza Cascardo wrote:
> Check that the function is on available_filter_functions. If it's not,
> mark the test as unresolved, instead of failing it.
>
Actually, I sent this out a while ago:
Thanks Jason,
Regards,
Dag
Den 08.07.2019 19:50, skrev Jason Gunthorpe:
On Mon, Jul 08, 2019 at 01:16:24PM +0200, Dag Moxnes wrote:
Use neighbour lock when copying MAC address from neighbour data struct
in dst_fetch_ha.
When not using the lock, it is possible for the function to race with
> -Original Message-
> From: Leo Li
> Sent: Monday, June 17, 2019 8:29 AM
> To: Olof Johansson
> Cc: a...@kernel.org; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.kernel.org; shawn...@kernel.org
> Subject: RE: [GIT PULL v2] updates to soc/fsl drivers for next(v5.3)
>
>
On Tue, Jul 02, 2019 at 03:36:56PM +, Loic PALLARDY wrote:
> Agree there is definitively an issue with the way virtio device are defined.
> Today definition is based on rproc firmware ressource table and rproc
> framework is in charge of vdev creation.
> Device tree definition was discarded
On Mon, Jul 8, 2019 at 11:29 AM Dmitry V. Levin wrote:
>
> The syscall entry/exit is now exposed via PTRACE_GETEVENTMSG,
> update the test accordingly.
Reviewed-by: Andy Lutomirski
On Mon, Jul 8, 2019 at 7:29 AM Arnd Bergmann wrote:
>
> On Sun, Jul 7, 2019 at 7:05 AM wrote:
>
> > * mm-move-mem_cgroup_uncharge-out-of-__page_cache_release.patch
> > * mm-shrinker-make-shrinker-not-depend-on-memcg-kmem.patch
> > * mm-shrinker-make-shrinker-not-depend-on-memcg-kmem-fix.patch
>
The syscall entry/exit is now exposed via PTRACE_GETEVENTMSG,
update the test accordingly.
Reported-by: kernel test robot
Signed-off-by: Dmitry V. Levin
---
tools/testing/selftests/seccomp/seccomp_bpf.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git
On 08.07.2019 08:37, AceLan Kao wrote:
> We have many commits in the driver which enable and then disable ASPM
> function over and over again.
>commit b75bb8a5b755 ("r8169: disable ASPM again")
>commit 0866cd15029b ("r8169: enable ASPM on RTL8106E")
>commit 94235460f9ea ("r8169: Align
On Mon, 8 Jul 2019, Andy Lutomirski wrote:
> > On Jul 8, 2019, at 3:35 AM, Thomas Gleixner wrote:
> > Anything less than the actual number of present CPUs is problematic except
> > you use the 'let's hope nothing happens' approach. We could add an option
> > to stop the bringup at the early
Check that the function is on available_filter_functions. If it's not,
mark the test as unresolved, instead of failing it.
Signed-off-by: Thadeu Lima de Souza Cascardo
---
tools/testing/selftests/ftrace/test.d/kprobe/kprobe_eventname.tc | 1 +
1 file changed, 1 insertion(+)
diff --git
From: David Miller
Date: Sun, 07 Jul 2019 22:18:05 -0700 (PDT)
> From: Jiangfeng Xiao
> Date: Fri, 5 Jul 2019 14:10:03 +0800
>
>> HI13X1 changed the offsets and bitmaps for tx_desc
>> registers in the same peripheral device on different
>> models of the hip04_eth.
>>
>> Signed-off-by:
Update cros_ec_commands.h to match the fingerprint MCU section in
the current ec_commands.h
Signed-off-by: Yicheng Li
---
include/linux/mfd/cros_ec_commands.h | 12
1 file changed, 12 insertions(+)
diff --git a/include/linux/mfd/cros_ec_commands.h
On Mon, 2019-07-08 at 19:27 +0200, Michal Kubecek wrote:
>
> Second reason is that with 8-bit genetlink command/message id, the space
> is not as infinite as it might seem.
FWIW, there isn't really any good reason for this, we have like 16
reserved bits in the genl header.
OTOH, having a LOT of
On 7/8/19 11:58 AM, Mathieu Desnoyers wrote:
- On Jun 30, 2019, at 9:56 AM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
Using ".arm .inst" for the arm signature introduces build issues for
programs compiled in Thumb mode because the assembler stays in the
arm mode for the rest
JJ
On 7/8/19 5:06 AM, Jean-Jacques Hiblot wrote:
Use the managed API of the LED class (devm_led_classdev_register()
instead of led_classdev_register()).
This allows us to remove the code used to track-and-destroy the LED devices
What changed from v1?
I don't see any changes especially the
On Mon, Jul 08, 2019 at 06:52:14PM +0200, Christian Borntraeger wrote:
> smp: Brought up 1 node, 1 CPU
> Unable to handle kernel pointer dereference in virtual kernel address space
> Failing address: 3a07 TEID: 3a070407
> Fault in home space mode while using kernel ASCE.
>
On 7/8/19 1:32 AM, Jian-Hong Pan wrote:
diff --git a/drivers/net/wireless/realtek/rtw88/pci.c
b/drivers/net/wireless/realtek/rtw88/pci.c
index cfe05ba7280d..1bfc99ae6b84 100644
--- a/drivers/net/wireless/realtek/rtw88/pci.c
+++ b/drivers/net/wireless/realtek/rtw88/pci.c
@@ -786,6 +786,15 @@
301 - 400 of 1336 matches
Mail list logo
