Here are the know kselftest issues on Linux 5.4 with
top commit commit 619e17cf75dd58905aa67ccd494a6ba5f19d6cc6
on x86_64:
The goal is to get these addressed before 5.4 comes out.
3 build failures and status:
pidfd - undefined reference to `pthread_create' collect2: error: ld
returned 1 exit s
> From: David Hildenbrand
> Sent: Thursday, September 26, 2019 12:20 AM
> To: Dexuan Cui ; KY Srinivasan ;
> Haiyang Zhang ; Stephen Hemminger
> ; sas...@kernel.org;
> linux-hyp...@vger.kernel.org; linux-kernel@vger.kernel.org; Michael Kelley
>
> Subject: Re: [PATCH] hv_balloon: Add the support o
On 9/25/19 10:11 PM, tim.b...@sony.com wrote:
I found a bug in kselftest KBUILD_OUTPUT handling.
The following works:
$ cd /home/tbird/work/linux
$ export KBUILD_OUTPUT=/home/tbird/work/kbuild
$ yes '' | make localmodconfig
$ make TARGETS=size kselftest
But this doesn't work:
$ cd /home/tbird/w
On Thu, Sep 26, 2019 at 07:51:00PM +0300, Schmauss, Erik wrote:
> > -Original Message-
> > From: linux-acpi-ow...@vger.kernel.org
> > On Behalf Of Shevchenko, Andriy
> > Sent: Thursday, September 26, 2019 9:35 AM
> > To: Schmauss, Erik
> > Cc: Nikolaus Voss ; Rafael J. Wysocki
> > ; Moore
Hi Tim,
On Thu, Sep 26, 2019 at 6:10 PM Tim Sander wrote:
>
> Hi
>
> Am Mittwoch, 11. September 2019, 04:37:46 CEST schrieb Masahiro Yamada:
> > Hi Dinh,
> >
> > On Wed, Sep 11, 2019 at 12:22 AM Dinh Nguyen wrote:
> > > On 9/10/19 8:48 AM, Tim Sander wrote:
> > > > Hi
> > > >
> > > > I have noti
On 9/24/19 9:28 AM, Connor Kuehl wrote:
The local variable 'bcmd_down' is always set to true almost immediately
before the do-while's condition is checked. As a result, !bcmd_down
evaluates to false which short circuits the logical AND operator meaning
that the second operand is never reached and
--
I am Dr Haruna Bello
I have a Geniue business transaction of 18.5 Million Us Dollars to do with
You
Hence You Co-operate with me I am assured you that within (7) seven
banking working days, this said amount will enter your given Bank
account with immediate alacrity. If you agree to my business
Quoting Jeffrey Hugo (2019-09-24 20:54:41)
> On Mon, Sep 16, 2019 at 3:44 PM Stephen Boyd wrote:
> >
> > Quoting Srinivas Kandagatla (2019-09-12 02:10:19)
> > > looks like SoC ID is not exported to sysfs for some reason.
> > > This patch adds it!
> > >
> > > This is mostly used by userspace librar
Instead of depending on markings in the section following NOTES to
restore the associated Program Header, use a dummy section, as done
in other architectures. This is preparation for moving NOTES into the
RO_DATA macro.
Signed-off-by: Kees Cook
---
arch/x86/kernel/vmlinux.lds.S | 3 ++-
1 file c
The .notes section should be non-executable read-only data. As such, it
can live in the RO_DATA macro instead of being per-architecture defined.
Signed-off-by: Kees Cook
---
arch/alpha/kernel/vmlinux.lds.S | 2 --
arch/arc/kernel/vmlinux.lds.S| 2 --
arch/arm/kernel/vmlinux-xip.lds.
This finishes renaming RO_DATA_SECTION to RO_DATA. (Calling this a
"section" is a lie, since it's multiple sections and section flags cannot
be applied to the macro.)
Signed-off-by: Kees Cook
---
arch/arc/kernel/vmlinux.lds.S | 2 +-
arch/c6x/kernel/vmlinux.lds.S | 2 +-
arch/csky/ke
The EXCEPTION_TABLE is read-only, so collapse it into RO_DATA.
Signed-off-by: Kees Cook
---
arch/c6x/kernel/vmlinux.lds.S | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/c6x/kernel/vmlinux.lds.S b/arch/c6x/kernel/vmlinux.lds.S
index a3547f9d415b..9a09aab63ab3 100644
After commit f7fac17ca925 ("xhci: Convert xhci_handshake() to use
readl_poll_timeout_atomic()"), ASMedia xHCI may fail to suspend.
Although the algorithms are essentially the same, the old max timeout is
(usec + usec * time of doing readl()), and the new max timeout is just
usec, which is much les
This series works to move the linker sections for NOTES and
EXCEPTION_TABLE into the RO_DATA area, where they belong on most
(all?) architectures. The problem being addressed was the discovery
by Rick Edgecombe that the exception table was accidentally marked
executable while he was developing his
In preparation for moving NOTES into RO_DATA, this renames the linker
script internal identifier for the PT_LOAD Program Header from "kernel"
to "text" to match other architectures.
Signed-off-by: Kees Cook
---
arch/powerpc/kernel/vmlinux.lds.S | 12 ++--
1 file changed, 6 insertions(+),
The Program Header identifiers are internal to the linker scripts. In
preparation for moving the NOTES segment declaration into RO_DATA,
standardize the identifier for the PT_NOTE entry to "note" as used by
all other architectures that emit PT_NOTE.
Signed-off-by: Kees Cook
---
arch/powerpc/kern
Function write_cam_from_cache in rtw_wlan_util.c is never used,
so remove it.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8723bs/core/rtw_wlan_util.c | 13 -
drivers/staging/rtl8723bs/include/rtw_mlme_ext.h | 1 -
2 files changed, 14 deletions(-)
diff --git a/drivers/st
Hi Anson,
On Mon, Aug 5, 2019 at 11:25 PM Anson Huang wrote:
>
> Hi, Stephen
> I think we should resume this thread, without this patch, mainline
> kernel boot up will cause mmc timeout all the time. If it is NOT good to
> disabling those peripheral devices' clock in i.MX7ULP's clock dr
> +++ b/drivers/net/wireless/realtek/rtlwifi/ps.c
> @@ -161,8 +161,7 @@ static void _rtl_ps_inactive_ps(struct ieee80211_hw *hw)
> if (ppsc->inactive_pwrstate == ERFON &&
> rtlhal->interface == INTF_PCI) {
> if ((ppsc->reg_rfps_level & RT_RF_OFF_LEVL_ASPM) &&
Can it
On 9/26/19 5:34 AM, Peter Zijlstra wrote:
> On Fri, Sep 20, 2019 at 11:54:02AM -0400, Waiman Long wrote:
>> While looking at a customr bug report about potential missed wakeup in
>> the system V semaphore code, I spot a potential problem. The fact that
>> semaphore waiter stays in TASK_RUNNING sta
On Fri, Sep 27, 2019 at 04:37:37AM +0530, Ravulapati Vishnu vardhan rao wrote:
> RAVEN has multiple I2S instances:BT and SP.But only BT is enabled.
> Now I2S SP instance also gets enabled with this patch.
This is extremely difficult to review as is, the patch is very
large and the description very
On Wed, Sep 25, 2019 at 10:38:35AM +0100, Colin King wrote:
> From: Colin Ian King
>
> There is a statement that is indented one level too deeply,
> remove the extraneous tab.
>
> Signed-off-by: Colin Ian King
Applied.
On Thu, Sep 26, 2019 at 11:57 AM Stephen Boyd wrote:
>
> Quoting Jeffrey Hugo (2019-09-24 20:54:41)
> > On Mon, Sep 16, 2019 at 3:44 PM Stephen Boyd wrote:
> > >
> > > Quoting Srinivas Kandagatla (2019-09-12 02:10:19)
> > > > looks like SoC ID is not exported to sysfs for some reason.
> > > > Thi
On Mon, Sep 23, 2019 at 8:31 PM Micah Morton wrote:
>
>The best way I know of ensuring this is
> for me to personally run the SafeSetID selftest (in
> tools/testing/selftests/safesetid/) every release, regardless of
> whether we make any changes to SafeSetID itself. Does this sound
On Fri, Sep 27, 2019 at 04:37:35AM +0530, Ravulapati Vishnu vardhan rao wrote:
> -#define ACP3x_PHY_BASE_ADDRESS 0x124
> -#define ACP3x_I2S_MODE 0
> -#define ACP3x_REG_START 0x124
> -#define ACP3x_REG_END 0x1250200
> -#define I2S_MODE 0x04
> -#define BT_TX_THRESH
This patch adds support for MSG_PEEK. In such a case, packets are not
removed from the rx_queue and credit updates are not sent.
Signed-off-by: Matias Ezequiel Vara Larsen
---
net/vmw_vsock/virtio_transport_common.c | 50 +++--
1 file changed, 47 insertions(+), 3 dele
On Fri, Sep 27, 2019 at 04:37:38AM +0530, Ravulapati Vishnu vardhan rao wrote:
> +static int snd_acp3x_suspend(struct device *dev)
> +{
> + return 0;
> +}
> +
> +static int snd_acp3x_resume(struct device *dev)
> +{
> + return 0;
> +}
> +
> +static const struct dev_pm_ops acp3x_pm = {
> +
Hi Kees,
Thanks for the quick patch. It seems my binaries start up well, and work
as expected, as before.
Thanks again for the quick response.
Regards,
Richard Kojedzinszky
2019-09-26 19:15 időpontban Kees Cook ezt írta:
When brk was moved for binaries without an interpreter, it should have
23.09.2019 16:36, Dmitry Osipenko пишет:
> 23.09.2019 16:31, Dmitry Osipenko пишет:
>> 23.09.2019 16:01, Jon Hunter пишет:
>>>
>>> On 23/09/2019 13:49, Dmitry Osipenko wrote:
23.09.2019 13:56, Jon Hunter пишет:
>
>
> On 04/08/2019 21:29, Dmitry Osipenko wrote:
>> It is possible
Hi Kevin,
On Thu, Sep 26, 2019 at 12:47 AM Kevin Hilman wrote:
>
> Martin Blumenstingl writes:
>
> > Hi Jerome,
> >
> > On Mon, Sep 23, 2019 at 11:29 AM Jerome Brunet wrote:
> >>
> >> On Sat 21 Sep 2019 at 17:12, Martin Blumenstingl
> >> wrote:
> >>
> >> > So far the HHI clock controller has
Hi Linus,
Please pull this usercopy fix for v5.4-rc1. Randy found a corner case
(HIGHMEM, DEBUG_VIRTUAL, >512MB RAM) with hardened usercopy that went
unnoticed since v4.8. This adds HIGHMEM awareness to hardened usercopy,
and has been living in -next for a bit more than a week now.
Thanks!
-Kees
On Wed, Sep 25, 2019 at 07:43:53PM +0800, Kai-Heng Feng wrote:
> Add pci_pr3_present() to check whether the platform supplies _PR3 to
> tell us which power resources the device depends on when in D3hot. This
> information is useful to let drivers choose different runtime suspend
> behavior. A user
Make the examples in Exynos Multi Core Timer bindings more readable and
bring them closer to real DTS by using defines for interrupt flags.
Suggested-by: Marek Szyprowski
Signed-off-by: Krzysztof Kozlowski
---
Rebased on top of:
https://patchwork.kernel.org/project/linux-samsung-soc/list/?seri
On Thu, Sep 26, 2019 at 08:26:12PM +0200, Richard Kojedzinszky wrote:
> Thanks for the quick patch. It seems my binaries start up well, and work as
> expected, as before.
>
> Thanks again for the quick response.
Awesome; thanks for the testing (and sorry for the breakage)! :)
-Kees
>
> Regards
It is common practice to place a comma after the last entry in an
initialized array to avoid the need to add one in future patches that
extend the array. But when the last element is a termination marker, the
comma could be harmful. Any new entries must be added before the
terminator (and the comma
The current implementation of pmc_core driver allows to reuse, but does
not reflect the exact number and names of IPs for a newer platform which
does not necessarily support all the IPs in the entries. The names and
number of these IPs might differ from its previous platforms. The number
of PCH IPs
Check if the platform supports and only then add a debugfs entry for PCH
IP power gating status.
Cc: Peter Zijlstra
Cc: Srinivas Pandruvada
Cc: Andy Shevchenko
Cc: Kan Liang
Cc: David E. Box
Cc: Rajneesh Bhardwaj
Cc: Tony Luck
Reviewed-by: Tony Luck
Signed-off-by: Gayatri Kammela
---
dri
Hi,
Patch 1: Cleans up termination lines
Patch 2: Refactor driver for ease of adding new SoCs
Patch 3: Refactor debugfs entry for PCH IPs power gating status
Patch 4: Add Tiger Lake legacy support to pmc_core
Patch 5: Add Elkhart Lake legacy support to pmc_core
All the information regarding the P
Add Elkhart Lake to the list of the platforms that intel_pmc_core
driver supports for pmc_core device.
Just like ICL and TGL, EHL can also reuse all the CNL PCH IPs. Also, it
uses the same PCH IPs of TGL, no additional effort is needed to enable
but to simply reuse them.
Cc: Peter Zijlstra
Cc: S
Add Tiger Lake to the list of the platforms that intel_pmc_core driver
supports for the pmc_core device.
Just like ICL, TGL can also reuse all the CNL PCH IPs. Since TGL has
almost the same number of PCH IPs as ICL, reuse ICL's PPFEAR_NUM_ENTRIES
instead of defining a new macro.
Cc: Peter Zijlstr
Hi Erik,
On Thu, 26 Sep 2019, Schmauss, Erik wrote:
-Original Message-
From: Nikolaus Voss
Sent: Thursday, September 12, 2019 1:08 AM
To: Shevchenko, Andriy ; Schmauss, Erik
; Rafael J. Wysocki ; Moore,
Robert
Cc: Len Brown ; Jacek Anaszewski
; Pavel Machek ; Dan Murphy
; linux-a...@vg
On Thu, 26 Sep 2019, Schmauss, Erik wrote:
-Original Message-
From: linux-acpi-ow...@vger.kernel.org
On Behalf Of Shevchenko, Andriy
Sent: Thursday, September 26, 2019 9:35 AM
To: Schmauss, Erik
Cc: Nikolaus Voss ; Rafael J. Wysocki
; Moore, Robert ; Len Brown
; Jacek Anaszewski ; Pavel
Before this change, trying to boot from the internal storage would
result in a lot of errors like:
[ 11.224046] mmc0: cache flush error -110
[ 11.224180] blk_update_request: I/O error, dev mmcblk0, sector 0 op
0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
or:
[ 137.544673] mmc0: tuning e
The gpio is not used for SD card detection on the FP2.
Signed-off-by: Luca Weiss
---
arch/arm/boot/dts/qcom-msm8974-fairphone-fp2.dts | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/arch/arm/boot/dts/qcom-msm8974-fairphone-fp2.dts
b/arch/arm/boot/dts/qcom-msm8974-f
Hi Chris,
Thank you for updating this.
On Thu, 26 Sep 2019 at 11:18, Chris Paterson
wrote:
>
> Ramesh is now using a new email address. Update the maintainer entry for
> the MAX2175 SDR tuner and the Renesas R-Car DRIF drivers.
>
> Signed-off-by: Chris Paterson
Acked-by: Ramesh Shanmugasundara
On Thu, Sep 26, 2019 at 04:49:23PM +0300, Kirill A. Shutemov wrote:
> It happens if the VMA got unmapped under us while we dropped mmap_sem
> and inode got freed.
>
> Pinning the file if we drop mmap_sem fixes the issue.
>
> Signed-off-by: Kirill A. Shutemov
> Reported-by: syzbot+03ee87124ee05af
>> Does this feedback indicate also an agreement for the detail
>> if the mapping of internal phy registers would be a required operation?
>> (Would such a resource allocation eventually be optional?)
>
> It is optional.
Would you like to integrate an other patch variant then?
Regards,
Markus
On Wed, 25 Sep 2019, Michal Hocko wrote:
> I am especially interested about this part. The more I think about this
> the more I am convinced that the underlying problem really is in the pre
> mature fallback in the fast path.
I appreciate you taking the time to continue to look at this but I'm
c
Hi all,
News: Builds for this week won't appear every day, I will try to
do some but no guarantees until Stephen returns on the 30th.
pending-fixes will get more updates than full -next.
Changes since 20190925:
The amlogic tree gained a conflict with Linus' tree which I fixed
up.
Non-merge comm
On Wed, 25 Sep 2019, Dan Carpenter wrote:
> The "mode" and "level" variables are enums and in this context GCC will
> treat them as unsigned ints so the error handling is never triggered.
>
> I also removed the bogus initializer because it isn't required any more
> and it's sort of confusing.
>
From: Masayoshi Mizuma
The system which has SVE feature crashed by unknown
reason. According to the memory dump, the panic happened
because the memory data pointed by task->thread.sve_state was
destroyed by someone.
We tried to reproduce the crash, however, it's hard to do that.
But, we found a
From: Masayoshi Mizuma
The system which has SVE feature crashed because of
the memory pointed by task->thread.sve_state was destroyed
by someone.
That is because sve_state is freed while the forking the
child process. The child process has the pointer of sve_state
which is same as the parent's b
Hi Linus,
The following changes since commit d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1:
Linux 5.3-rc5 (2019-08-18 14:31:08 -0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-5.4-1
for you to fetch changes up to a8fd0feeca35cb8f9dd
It is possible to get a lockup if kernel decides to enter LP2 cpuidle
from some clk-notifier, in that case CCF's "prepare" mutex is kept locked
and thus clk_get_rate(pclk) blocks on the same mutex with interrupts being
disabled, hanging machine.
Signed-off-by: Dmitry Osipenko
---
Changelog:
v5:
The removed barrier isn't needed because writes/reads are strictly ordered
and even if PMC had separate ports for writes, it wouldn't matter since
the hardware logic takes into effect after triggering CPU's power-gating
and at that point all CPU accesses are guaranteed to be completed. That
barrier
On Thu, Sep 26, 2019 at 8:44 PM Nikolaus Voss wrote:
>
> On Thu, 26 Sep 2019, Schmauss, Erik wrote:
> >> -Original Message-
> >> From: linux-acpi-ow...@vger.kernel.org
> >> On Behalf Of Shevchenko, Andriy
> >> Sent: Thursday, September 26, 2019 9:35 AM
> >> To: Schmauss, Erik
> >> Cc: Ni
On Thu, Sep 26, 2019 at 04:49:23PM +0300, Kirill A. Shutemov wrote:
> On Tue, Sep 24, 2019 at 05:43:37PM -0400, Johannes Weiner wrote:
> > On Tue, Sep 24, 2019 at 01:46:08PM -0700, Matthew Wilcox wrote:
> > > On Tue, Sep 24, 2019 at 03:42:38PM -0400, Johannes Weiner wrote:
> > > > Signed-off-by: Jo
On Thu, Sep 26, 2019 at 6:16 AM Oleksandr Andrushchenko
wrote:
>
> On 9/26/19 1:46 PM, Robin Murphy wrote:
> > On 2019-09-26 11:17 am, Oleksandr Andrushchenko wrote:
> >>
> >> On 9/26/19 12:49 PM, Julien Grall wrote:
> >>> Hi Rob,
> >>>
> >>>
> >>> On 9/25/19 10:50 PM, Rob Herring wrote:
> As
On Tue, 24 Sep 2019, Mina Almasry wrote:
> > I personally prefer the one counter approach only for the reason that it
> > exposes less information about hugetlb reservations. I was not around
> > for the introduction of hugetlb reservations, but I have fixed several
> > issues having to do with r
Hi,
I'm trying to get an allmodconfig kernel to boot. The way I configure
the kernel is:
'make allmodconfig KCONFIG_ALLCONFIG=$(pwd)/arch/arm64/configs/defconfig'
allmodconfig will use the KCONFIG_ALLCONFIG file as the base and then
turn the rest into modules.
The idea behind using the defconfig
Commit 833c97254724 ("arm64: defconfig: Enable DRM DU and V4L2 FCP + VSP
modules") ment to enable the camera framework and drivers but enabled a
bit more.
Since we don't have any drivers for MEDIA_ANALOG_TV_SUPPORT or
MEDIA_DIGITAL_TV_SUPPORT theres no meaning to enable the framework to
the defcon
When building allmodconfig KCONFIG_ALLCONFIG=$(pwd)/arch/arm64/configs/defconfig
CONFIG_CMDLINE_FORCE gets enabled. Which forces the user to pass the
full cmdline to CONFIG_CMDLINE="...".
Rework so that we disable CONFIG_CMDLINE_FORCE in the defconfig file so
we don't have to pass in the CONFIG_CM
When building allmodconfig KCONFIG_ALLCONFIG=$(pwd)/arch/arm64/configs/defconfig
CONFIG_CPU_BIG_ENDIAN gets enabled. Which tends not to be what most
people wants.
Rework so that we disable CONFIG_CPU_BIG_ENDIAN in the defcinfig file so
it doesn't get enabled when building allmodconfig kernels. Whe
When building an allmodconfig
KCONFIG_ALLCONFIG=$(pwd)/arch/arm64/configs/defconfig
kernel, CONFIG_DEBUG_PREEMPT and CONFIG_FTRACE will be turn off.
There is no benefit in disabling these fragments. By enabling these
nothing will happen without interaction from the user to enable it from
the cmd o
On 26/09/2019 20:52:38+0200, Markus Elfring wrote:
> >> Does this feedback indicate also an agreement for the detail
> >> if the mapping of internal phy registers would be a required operation?
> >> (Would such a resource allocation eventually be optional?)
> >
> > It is optional.
>
> Would you li
On 9/26/19 11:23 AM, Matias Ezequiel Vara Larsen wrote:
> This patch adds support for MSG_PEEK. In such a case, packets are not
> removed from the rx_queue and credit updates are not sent.
>
> Signed-off-by: Matias Ezequiel Vara Larsen
> ---
> net/vmw_vsock/virtio_transport_common.c | 50
> +
> -Original Message-
> From: Rafael J. Wysocki
> Sent: Thursday, September 26, 2019 12:26 PM
> To: Nikolaus Voss
> Cc: Schmauss, Erik ; Shevchenko, Andriy
> ; Rafael J. Wysocki ;
> Moore, Robert ; Len Brown ;
> Jacek Anaszewski ; Pavel Machek
> ; Dan Murphy ; linux-a...@vger.kernel.org;
The description of "regulator-boot-on" was a little unclear, at least
to me. Did this property mean that we should turn the regulator on at
boot? Or perhaps it was intended only to be used for regulators where
we couldn't read the state at bootup to indicate what state we should
assume? The answ
Hello,
On Fri, 27 Sep 2019, Haishuang Yan wrote:
> Test virtual server via ipip tunnel.
>
> Tested:
> # selftests: netfilter: ipvs.sh
> # Testing DR mode...
> # Testing NAT mode...
> # Testing Tunnel mode...
> # ipvs.sh: PASS
> ok 6 selftests: netfilter: ipvs.sh
>
> Signed-off-by: Hai
On Thu, Sep 26, 2019 at 1:37 AM Ardelean, Alexandru
wrote:
>
> On Wed, 2019-09-25 at 10:14 -0500, Adam Ford wrote:
> > [External]
> >
> > On Fri, Sep 20, 2019 at 2:06 AM Philipp Puschmann
> > wrote:
> > > Hi Andy,
> > >
> > > Am 20.09.19 um 05:42 schrieb Andy Duan:
> > > > From: Philipp Puschmann
Hi,
On Tue, Sep 24, 2019 at 11:28 AM Mark Brown wrote:
> On Mon, Sep 23, 2019 at 03:40:09PM -0700, Doug Anderson wrote:
> > On Mon, Sep 23, 2019 at 11:49 AM Mark Brown wrote:
> > > On Mon, Sep 23, 2019 at 11:36:11AM -0700, Doug Anderson wrote:
>
> > > > 1. Would it be valid to say that it's alwa
Dear all,
Is there any summary of crash/panic behaviors in the Linux Kernel? For
example, GPF (general protection fault), Kernel BUG (BUG_ON).
--
My best regards to you.
No System Is Safe!
Dongliang Mu
On Thu, Sep 26, 2019 at 10:33 AM Kees Cook wrote:
>
> Please pull this mostly mechanical treewide conversion to the single and
> more accurately named sizeof_member() macro for the end of v5.4-rc1. This
> replaces 3 macros of the same behavior (FIELD_SIZEOF(), SIZEOF_FIELD(),
> and sizeof_field())
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: 26acf400d2dcc72c7e713e1f55db47ad92010cc2 perf unwind: Fix libunwind
build failure on i386 systems
The only kernel change is comment
The pull request you sent on Thu, 26 Sep 2019 09:02:07 -0700:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.4-merge-8
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2268419e4c9559ec1e80ee7ae7bd54f8976234cb
Thank you!
--
Deet-doot-dot, I am a bot.
ht
The pull request you sent on Thu, 26 Sep 2019 19:13:30 +:
> git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-5.4-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/972a2bf7dfe39ebf49dd47f68d27c416392e53b1
Thank you!
--
Deet-doot-dot, I am a bot.
ht
The pull request you sent on Thu, 26 Sep 2019 15:30:04 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.mount3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/dadedd85630af28b21c826265f7a651f040f6f13
Thank you!
--
Deet-doot-dot, I am a bot.
ht
The pull request you sent on Thu, 26 Sep 2019 16:17:43 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-5.4-rc1-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ec56103e18c7590303c69329dd4aaadf8a898c19
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Thu, 26 Sep 2019 16:58:34 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-5.4-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/16cdf08467848dc53acd2175d563b30a3cd486aa
Thank you!
--
Deet-doot-dot, I am a b
The pull request you sent on Thu, 26 Sep 2019 11:35:41 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
> tags/usercopy-v5.4-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0576f0602a4926b0027fdd7561a1c0053fa99d26
Thank you!
--
Deet-doot-d
The pull request you sent on Mon, 23 Sep 2019 16:40:15 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux-kselftest-5.4-rc1.1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/797a3242755da1b7c1ada6fb153cb2700ef30a80
Thank you!
--
On 9/26/19 4:17 PM, Catalin Marinas wrote:
> On Thu, Sep 26, 2019 at 01:22:01PM +0100, Vincenzo Frascino wrote:
>> On 9/26/19 11:56 AM, Vincenzo Frascino wrote:
>>> On 9/26/19 9:06 AM, Catalin Marinas wrote:
Now, could we not generate a COMPATCC in the Makefile and use
$(COMPATCC) here in
On 9/26/19 3:26 PM, Catalin Marinas wrote:
> On Thu, Sep 26, 2019 at 02:38:03PM +0100, Vincenzo Frascino wrote:
>> diff --git a/arch/arm64/Kbuild b/arch/arm64/Kbuild
>> index d6465823b281..75cf8c796d0e 100644
>> --- a/arch/arm64/Kbuild
>> +++ b/arch/arm64/Kbuild
>> @@ -4,3 +4,9 @@ obj-$(CONFIG_NET)
Linus,
Please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
# HEAD: e430d802d6a3aaf61bd3ed03d9404888a29b9bf9 timer: Read jiffies once
when forwarding base clk
Fixes a timer expiry bug that would c
The pull request you sent on Thu, 26 Sep 2019 05:09:26 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> trace-v5.4-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7897c04ad09f815aea1f2dbb05825887d4494a74
Thank you!
--
Deet-doot-dot,
On Thu, 2019-09-26 at 08:54 -0400, Prarit Bhargava wrote:
> The current code structure has similar but separate command functions
> for
> the enable and disable operations. This can be improved by adding an
> int
> argument to the command function structure, and interpreting 1 as
> enable
> and 0
On 9/26/19 4:31 PM, Catalin Marinas wrote:
> On Thu, Sep 26, 2019 at 02:38:01PM +0100, Vincenzo Frascino wrote:
>> this patch series is meant to address the various compilation issues you
>> reported about arm64 vdso32. (This time for real I hope ;))
>>
>> Please let me know if there is still somet
On Thu, 26 Sep 2019 at 23:06, Arnaldo Carvalho de Melo
wrote:
>
> Em Thu, Sep 26, 2019 at 10:59:41PM +0530, Naresh Kamboju escreveu:
> > perf build failed on linux -next on i386 build
> >
> > build error:
> > perf-in.o: In function `libunwind__x86_reg_id':
> > tools/perf/util/libunwind/../../arch/
Summary / Changelog-v5:
- Add the new flags GRND_INSECURE and GRND_SECURE_UNBOUNDED_INITIAL_WAIT
to getrandom(2), instead of introducing a new getrandom2(2) system
call, which nobody liked.
- Fix a bug discovered through testing where "int ret =
wait_event_interruptible_timeout(wa
Since Linux v3.17, getrandom(2) has been created as a new and more
secure interface for pseudorandom data requests. It attempted to
solve three problems, as compared to /dev/urandom:
1. the need to access filesystem paths, which can fail, e.g. under a
chroot
2. the need to open a file d
Neil Armstrong writes:
> This serie aime to support when the suspend/resume firmware alters the
> clock tree, leading to an incorrect representation of the clock tree
> after a resume from suspend-to-mem.
>
> For the Amlogic G12A/G12B/SM1 case, the SCPI firmware handling suspend
> alters the CPU
On Wed, Sep 18, 2019 at 11:51 AM Alan Stern wrote:
>
> On Wed, 18 Sep 2019, Abhishek Pandit-Subedi wrote:
>
> > Sorry, last reply went out with HTML. Re-sending in plain text.
> >
> > On Wed, Sep 18, 2019 at 7:23 AM Alan Stern
> > wrote:
> > >
> > > On Tue, 17 Sep 2019, Abhishek Pandit-Subedi wr
On Thu, Sep 26, 2019 at 01:06:01PM -0700, Linus Torvalds wrote:
> (a) why didn't this use the already existing and well-named macro
> that nobody really had issues with?
That was suggested, but other folks wanted the more accurate "member"
instead of "field" since a treewide change was happening
On Mon, Sep 23, 2019 at 11:33:21AM -0700, Andy Lutomirski wrote:
> On Fri, Sep 20, 2019 at 11:07 PM Florian Weimer wrote:
> >
> > * Linus Torvalds:
> >
> > > Violently agreed. And that's kind of what the GRND_EXPLICIT is really
> > > aiming for.
> > >
> > > However, it's worth noting that nobody s
On 9/26/19 4:59 PM, Catalin Marinas wrote:
> On Thu, Sep 26, 2019 at 02:38:03PM +0100, Vincenzo Frascino wrote:
>> arch/arm64/kernel/vdso32/Makefile| 9 +
>
> Could you please also remove the unnecessary gcc-goto.sh check in this
> file? We don't use jump labels in the vdso
On 9/26/19 12:28 PM, David Rientjes wrote:
> On Tue, 24 Sep 2019, Mina Almasry wrote:
>
>>> I personally prefer the one counter approach only for the reason that it
>>> exposes less information about hugetlb reservations. I was not around
>>> for the introduction of hugetlb reservations, but I ha
On Thu, Sep 19, 2019 at 10:31:42AM -0700, Christoph Hellwig wrote:
> On Thu, Sep 19, 2019 at 01:26:38AM -0700, Paul Walmsley wrote:
> >
> > Resolve most of the warnings emitted by sparse. The objective here is
> > to keep arch/riscv as clean as possible with regards to sparse warnings,
> > and to
The btree implementation defines its own MAX macro, whilst also
including kernel.h, which already defines a max macro. This removes the
custom implementation in favour of the standard one provided in kernel.h
Signed-off-by: Harry Jeffery
---
lib/btree.c | 3 +--
1 file changed, 1 insertion(+), 2
On Mon, Sep 23, 2019 at 3:12 PM Brian Starkey wrote:
>
> I didn't see any response about using the test harness. Did you decide
> against it?
Hey! Spent a little time looking at this bit and just wanted to reply
to this point. So first, apologies, I think I missed the suggestion
earlier. That sa
On 9/26/19 1:44 PM, Ahmed S. Darwish wrote:
Since Linux v3.17, getrandom(2) has been created as a new and more
secure interface for pseudorandom data requests. It attempted to
solve three problems, as compared to /dev/urandom:
1. the need to access filesystem paths, which can fail, e.g. unde
401 - 500 of 690 matches
Mail list logo