pci_map_rom/pci_get_rom_size() performs memory access in the ROM.
In case the Memory Space accesses were disabled, readw() is likely
to trigger a synchronous external abort on some platforms.
In case memory accesses were disabled, re-enable them before the
call and disable them back again just aft
Hi,
* Lokesh Vutla [190214 18:03]:
> On 2/14/2019 11:16 PM, Tony Lindgren wrote:
> > But I'd rather have a proper hardware based phandle + index
> > type mapping in the dts if possible though.
>
> The idea about sysfw here is that Linux is not aware of anything about
> this device(Interrupt Rout
On 2/15/19 10:11 AM, Alex Deucher wrote:
> On Fri, Feb 15, 2019 at 11:08 AM Gustavo A. R. Silva
> wrote:
>>
>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>> cases where we are expecting to fall through.
>>
>> Warning level 3 was used: -Wimplicit-fallthrough=3
>>
>> Notice th
Some PHY drivers like the generic one do not provide a read_status
callback on their own but rely on genphy_read_status being called
directly.
With the current code, this results in a NULL function pointer call.
Call genphy_read_status instead when there is no specific callback.
Signed-off-by: Pa
DW USB controller on HSDK hangs sometimes after SW reset, so
add reset handle to make possible to reset DW USB controller HW.
Signed-off-by: Eugeniy Paltsev
---
arch/arc/boot/dts/hsdk.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arc/boot/dts/hsdk.dts b/arch/arc/boot/dts/hsdk.dt
On 02/14, Kees Cook wrote:
>
> --- a/fs/binfmt_script.c
> +++ b/fs/binfmt_script.c
> @@ -42,9 +42,18 @@ static int load_script(struct linux_binprm *bprm)
> fput(bprm->file);
> bprm->file = NULL;
>
> - bprm->buf[BINPRM_BUF_SIZE - 1] = '\0';
> - if ((cp = strchr(bprm->buf,
On 15/02/2019, Michal Hocko wrote:
> On Fri 15-02-19 10:19:12, Sasha Levin wrote:
>> On Fri, Feb 15, 2019 at 10:42:05AM +0100, Michal Hocko wrote:
>> > On Fri 15-02-19 10:20:13, Greg KH wrote:
>> > > On Fri, Feb 15, 2019 at 10:10:00AM +0100, Michal Hocko wrote:
>> > > > On Fri 15-02-19 08:00:22, G
It seemed odd to say "since 4.17" in a 4.4 kernel. Consider
rewording the reference to indicate where in the stable series
it was introduced as well as where it originated.
Signed-off-by: Mark Rustad
---
Does this brief elaboration add useful information? It seems to
me that someone using a par
On Fri, Feb 15, 2019 at 3:54 AM Axel Lin wrote:
>
> Use case range for continuous range to make the code shorter.
> The .readable_reg and .writable_reg implementation are exactly the same,
> so use a common ltc3676_readable_writeable_reg function instead.
>
> Signed-off-by: Axel Lin
> ---
> driv
On Fri, Feb 15, 2019 at 05:17:08PM +0100, Paul Kocialkowski wrote:
> Some PHY drivers like the generic one do not provide a read_status
> callback on their own but rely on genphy_read_status being called
> directly.
>
> With the current code, this results in a NULL function pointer call.
> Call ge
Le vendredi 15 février 2019 à 14:44 +0100, Hans Verkuil a écrit :
> Hi Stanimir,
>
> I never paid much attention to this patch series since others were busy
> discussing it and I had a lot of other things on my plate, but then I heard
> that this patch made G_FMT blocking.
>
> That's a no-go. App
On Fri, Feb 15, 2019 at 8:18 AM Oleg Nesterov wrote:
> WITHOUT '\n' at the end. If I read load_script() correctly it should work,
> so I think the 2nd for() loop should also reset "truncated" if *cp == '\0'.
Correct. My original v3 handles this correctly. I'll work on a version
with small inline
On 15/02/2019 16:35, Oleksandr Andrushchenko wrote:
> On 2/15/19 5:28 PM, Boris Ostrovsky wrote:
>> On 2/15/19 10:07 AM, Oleksandr Andrushchenko wrote:
>>> On 2/15/19 5:03 PM, Boris Ostrovsky wrote:
On 2/14/19 9:23 AM, Oleksandr Andrushchenko wrote:
> /* DMA buffer export support. */
Hi,
On Fri, 2019-02-15 at 17:23 +0100, Andrew Lunn wrote:
> On Fri, Feb 15, 2019 at 05:17:08PM +0100, Paul Kocialkowski wrote:
> > Some PHY drivers like the generic one do not provide a read_status
> > callback on their own but rely on genphy_read_status being called
> > directly.
> >
> > With th
On 2/13/19 3:52 PM, Arnd Bergmann wrote:
On Wed, Feb 13, 2019 at 10:56 AM Benjamin Gaignard
wrote:
Implement ARM errata 814220 for Cortex A7.
This patch has been wroten by Jason Liu years ago but never send upstream.
I have tried to contact the author on multiple email addresses but I have
Some PHY drivers like the generic one do not provide a read_status
callback on their own but rely on genphy_read_status being called
directly.
With the current code, this results in a NULL function pointer call.
Call genphy_read_status instead when there is no specific callback.
Fixes: f411a6160b
On Mon, Feb 11, 2019 at 10:58:04AM -0500, J. Bruce Fields wrote:
> On Sat, Feb 09, 2019 at 07:43:54AM -0500, Jeff Layton wrote:
> > On Fri, 2019-02-08 at 15:10 -0500, J. Bruce Fields wrote:
> > > From: "J. Bruce Fields"
> > >
> > > These patches allow NFSv4 clients holding delegations to keep the
Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI
device exposes the capability for 64-bit PPNs.
Reviewed-by: Adit Ranadive
Reviewed-by: Jorgen Hansen
Signed-off-by: Vishnu Dasa
---
drivers/misc/vmw_vmci/vmci_doorbell.c | 9 ++--
drivers/misc/vmw_vmci/vmci_doorbell.h
According to the chipidea driver bindings, the USB PHY is specified via
the "phys" phandle node. However, this only takes effect for USB PHYs
that use the common PHY framework. For legacy USB PHYs, a simple lookup
based on the USB PHY type is done instead.
This does not play out well when more tha
>> > Ok, I can add a check in another patch. Should we return NULL pointer
>> > if msg->len is 0 or print out some warnings? Thanks.
>>
>> No warning, msg->len == 0 is a valid setting. But interesting question:
>> I was about to say NULL, but your driver would assume ENOMEM there and
>> discard t
syzbot has found a reproducer for the following crash on:
HEAD commit:cb5b020a8d38 Revert "exec: load_script: don't blindly trun..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12b68c8f40
kernel config: https://syzkaller.appspot.com/x/.config?x=ee4345
In some of our hottest network services, fget_light + fput overhead
can represent 1-2% of the processes' total CPU usage. I'd like to
discuss ways to reduce this overhead.
One proposal we have been testing is removing the refcount increment
and decrement, and using some sort of safe memory reclam
On Fri, Feb 15, 2019 at 8:18 AM Oleg Nesterov wrote:
>
> Not sure. Consider a script file which has a single line
>
> #!/path/to/interpreter
>
> WITHOUT '\n' at the end.
Heh. I'm not sure how valid that is, but it's an interesting case for sure.
But it's actually fairly easy to fix with
On 2/15/19 5:27 PM, Nicolas Dufresne wrote:
> Le vendredi 15 février 2019 à 14:44 +0100, Hans Verkuil a écrit :
>> Hi Stanimir,
>>
>> I never paid much attention to this patch series since others were busy
>> discussing it and I had a lot of other things on my plate, but then I heard
>> that this p
On Wed, Feb 13, 2019 at 06:21:31PM -0500, Prarit Bhargava wrote:
> From: Konrad Rzeszutek Wilk
>
+LKML
> This was submitted in 2015 here
>
> https://marc.info/?l=linux-kernel&m=142807132515973&w=2
>
> and has been included in Fedora builds ever since. No issues have been
> reported with the p
On Mon, Feb 11, 2019 at 8:54 PM Krzysztof Kozlowski wrote:
> Samsung mach/soc changes for v5.1
>
> Two fixes: one for handling timeout while booting secondary CPU of
> Exynos and second for S3C24xx DVS notifier.
Pulled into arm/soc, thanks!
Arnd
Em Fri, Feb 15, 2019 at 03:42:46PM +0200, Tommi Rantala escreveu:
> From: Tommi Rantala
>
> If perf was built without trace support, trace+probe_vfs_getname.sh
> fails:
>
> # perf trace -h
> perf: 'trace' is not a perf-command. See 'perf --help'
>
> # perf test 64
> 64: Check open filen
On 15/02/2019 14:37, Ulf Hansson wrote:
> On Fri, 15 Feb 2019 at 12:00, Jon Hunter wrote:
>>
>> Hi Rafael,
>>
>> On 12/02/2019 12:08, Rafael J. Wysocki wrote:
>>> From: Rafael J. Wysocki
>>>
>>> If a stateless device link to a certain supplier with
>>> DL_FLAG_PM_RUNTIME set in the flags is add
On Fri, 15 Feb 2019 15:53:24 +0800
Jason Wang wrote:
> When fail, translate_desc() returns negative value, otherwise the
> number of iovs. So we should fail when the return value is negative
> instead of a blindly check against zero.
>
> Reported-by: Stephen Hemminger
> Fixes: cc5e71075947 ("vh
On Thu, Feb 14, 2019 at 12:32 PM Dan Williams wrote:
>
> The ARS implementation implements exponential back-off on the poll
> interval to prevent high-frequency access to the DIMM / platform
> interface. Depending on when the ARS completes the poll interval may
> exceed the completion event by min
On Fri, Feb 15, 2019 at 5:03 PM Jann Horn wrote:
>
> On Fri, Feb 15, 2019 at 4:40 PM Dmitry Vyukov wrote:
> > On Thu, Oct 11, 2018 at 4:18 PM Paolo Bonzini wrote:
> > > On 10/10/2018 09:58, syzbot wrote:
> > > > do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316
> > > > invalid_op+0x14/0x20 a
On Thu, Feb 14, 2019 at 12:08:58PM +0800, Xiaoyao Li wrote:
> Commit ca83b4a7f2d068da79a0 ("x86/KVM/VMX: Add find_msr() helper function")
> introduces the helper function find_msr(), which returns -ENOENT when
> not find the msr in vmx->msr_autoload.guest/host. Correct checking contion
s/not find/
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
Warning level 3 was used: -Wimplicit-fallthrough=3
This patch is part of the ongoing efforts to enable
-Wimplicit-fallthrough.
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/amd
On 2/14/19 10:03 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190214:
>
on x86_64:
ld: net/core/lwt_bpf.o: in function `bpf_lwt_xmit_reroute':
lwt_bpf.c:(.text+0x11e): undefined reference to `ip_route_output_flow'
ld: net/core/lwt_bpf.o: in function `bpf_input':
lwt_bpf.c:(.text+0x
On 2/14/19 8:31 PM, Alexandre Ghiti wrote:
> On systems without CMA or (MEMORY_ISOLATION && COMPACTION) activated but
> that support gigantic pages, boottime reserved gigantic pages can not be
> freed at all. This patch simply enables the possibility to hand back
> those pages to memory allocator.
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
Warning level 3 was used: -Wimplicit-fallthrough=3
This patch is part of the ongoing efforts to enable
-Wimplicit-fallthrough.
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/amd
Have the IMA architecture specific policy require signed kernel modules
on systems with secure boot mode enabled; and coordinate the different
signature verification methods, so only one signature is required.
Requiring appended kernel module signatures may be configured, enabled
on the boot comma
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
Warning level 3 was used: -Wimplicit-fallthrough=3
Notice that, in this particular case, the code comment is modified
in accordance with what GCC is expecting to find.
This patch is part
James Morris wrote:
> For which kernel, -rc or 5.1?
-rc, preferably, but I don't think any of them are particularly urgent, so if
you'd rather wait...
David
The following changes since commit 69c1f396f25b805aeff08f06d2e992c315ee5b1e:
efi/x86: Convert x86 EFI earlyprintk into generic earlycon implementation
(2019-02-04 08:27:30 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-next
From: Anders Roxell
Commit a893ea15d764 ("tpm: move tpm_chip definition to
include/linux/tpm.h") introduced a build error when both ima and efi is
enabled. What happens is that both headers (ima.h and efi.h) defines the
same 'NONE' constant, and it broke when they started getting included
from th
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
Warning level 3 was used: -Wimplicit-fallthrough=3
This patch is part of the ongoing efforts to enable
-Wimplicit-fallthrough.
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/amd
I have noticed ext4 filesystem corruption on two of my test alphas with
4.20.0-09062-gd8372ba8ce28.
Retried it, still happens with 5.0.0-rc5-00358-gdf3865f8f568 - rsync of emerge
--sync just fail with nothing in dmesg.
Finished second round of bisecting, first round did not get me far enough
On Mon, Feb 4, 2019 at 9:56 AM Jens Wiklander wrote:
>
> Hello arm-soc maintainers,
>
> Please pull this TEE subsystem enhancement. A tee bus driver framework
> is introduced in order to support an OP-TEE based RNG driver.
>
> The last commit makes changes under drivers/char/hw_random which
> also
Quoting Jerome Brunet (2019-02-13 01:16:18)
> On Tue, 2019-02-05 at 16:01 -0800, Stephen Boyd wrote:
> > >
> > > I really don't understand why you insist on keeping this special case for
> > > num_parent == 1, when we know it is not coherent.
> > >
> > > Considering, that I already proposed the f
On Fri, Feb 15, 2019 at 05:32:20PM +0100, Paul Kocialkowski wrote:
> Some PHY drivers like the generic one do not provide a read_status
> callback on their own but rely on genphy_read_status being called
> directly.
>
> With the current code, this results in a NULL function pointer call.
> Call ge
On Fri, Feb 15, 2019 at 8:39 AM Linus Torvalds
wrote:
>
> On Fri, Feb 15, 2019 at 8:18 AM Oleg Nesterov wrote:
> >
> > Not sure. Consider a script file which has a single line
> >
> > #!/path/to/interpreter
> >
> > WITHOUT '\n' at the end.
>
> Heh. I'm not sure how valid that is, but it's
On Fri, Feb 1, 2019 at 7:04 PM Santosh Shilimkar
wrote:
> soc: ti: couple of non critical fixes for v5.1
>
> - Fix the Clang warning for enum in Navigator dma
> - Simplify code in ti_sci with DEFINE_SHOW_ATTRIBUTE macro
Pulled into arm/drivers, thanks!
Arnd
On Fri, Feb 15, 2019 at 11:50:18AM -0500, Mimi Zohar wrote:
> Have the IMA architecture specific policy require signed kernel modules
> on systems with secure boot mode enabled; and coordinate the different
> signature verification methods, so only one signature is required.
>
> Requiring appended
> > How about using phy_read_status()?
>
> Thanks fo rthe suggestion! Though I don't that would work here since
> our priv->phy_drv != phydev->drv, so it looks like we need to be
> breaking it down in the driver.
Ahm, yes. I forgot how this driver works.
Andrew
Hello,
syzbot found the following crash on:
HEAD commit:cb5b020a8d38 Revert "exec: load_script: don't blindly trun..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1016c0f340
kernel config: https://syzkaller.appspot.com/x/.config?x=ee434566c893c7b1
da
> On Feb 15, 2019, at 6:14 AM, Arnaldo Carvalho de Melo wrote:
>
> Em Thu, Feb 14, 2019 at 03:58:40PM -0800, Song Liu escreveu:
>> Events with bpf_event should be considered as side-band event, as they
>> carry information about BPF programs.
>>
>> Fixes: 6ee52e2a3fe4 ("perf, bpf: Introduce P
Most architectures current have a debugfs file for dumping the kernel
page tables. Currently each architecture has to implement custom
functions for walking the page tables because the generic
walk_page_range() function is unable to walk the page tables used by the
kernel.
This series extends the
From: James Morse
Exposing the pud/pgd levels of the page tables to walk_page_range() means
we may come across the exotic large mappings that come with large areas
of contiguous memory (such as the kernel's linear map).
Expose p?d_large() from each architecture to detect these large mappings.
a
The pte_hole() callback is called at multiple levels of the page tables.
Code dumping the kernel page tables needs to know what at what depth
the missing entry is. Add this is an extra parameter to pte_hole().
When the depth isn't know (e.g. processing a vma) then -1 is passed.
Note that depth sta
Exposing the pud/pgd levels of the page tables to walk_page_range() means
we may come across the exotic large mappings that come with large areas
of contiguous memory (such as the kernel's linear map).
Expose p?d_large() from each architecture to detect these large mappings.
x86 already has these
pgd_entry() and pud_entry() were removed by commit 0b1fbfe50006c410
("mm/pagewalk: remove pgd_entry() and pud_entry()") because there were
no users. We're about to add users so reintroduce them, along with
p4d_entry() as we now have 5 levels of tables.
Note that commit a00cc7d9dd93d66a ("mm, x86:
Now walk_page_range() can walk kernel page tables, we can switch the
arm64 ptdump code over to using it, simplifying the code.
Signed-off-by: Steven Price
---
arch/arm64/mm/dump.c | 108 +--
1 file changed, 53 insertions(+), 55 deletions(-)
diff --git a/a
mm/dump_pagetables.c passes both struct seq_file and struct pg_state
down the chain of walk_*_level() functions to be passed to note_page().
Instead place the struct seq_file in struct pg_state and access it from
struct pg_state (which is private to this file) in note_page().
Signed-off-by: Steven
It is useful to be able to skip parts of the page table tree even when
walking without VMAs. Add test_p?d callbacks similar to test_walk but
which are called just before a table at that level is walked. If the
callback returns non-zero then the entire table is skipped.
Signed-off-by: Steven Price
From: James Morse
Exposing the pud/pgd levels of the page tables to walk_page_range() means
we may come across the exotic large mappings that come with large areas
of contiguous memory (such as the kernel's linear map).
For architectures that don't provide p?d_large() macros, provided a
does not
An mm_struct is needed to enable x86 to use of the generic
walk_page_range() function.
In the case of walking the user page tables (when
CONFIG_PAGE_TABLE_ISOLATION is enabled), it is necessary to create a
fake_mm structure because there isn't an mm_struct with a pointer
to the pgd of the user pag
> On Feb 15, 2019, at 6:21 AM, Arnaldo Carvalho de Melo wrote:
>
> Em Thu, Feb 14, 2019 at 04:00:06PM -0800, Song Liu escreveu:
>> bpf_prog_info contains information necessary to annotate bpf programs.
>> This patch saves bpf_prog_info for bpf programs loaded in the system.
>>
>> Signed-off-b
To enable x86 to use the generic walk_page_range() function, the
callers of ptdump_walk_pgd_level_debugfs() need to pass in the mm_struct.
This means that ptdump_walk_pgd_level_core() is now always passed a
valid pgd, so drop the support for pgd==NULL.
Signed-off-by: Steven Price
---
arch/x86/i
Make use of the new functionality in walk_page_range to remove the
arch page walking code and use the generic code to walk the page tables.
The effective permissions are passed down the chain using new fields
in struct pg_state.
The KASAN optimisation is implemented by including test_p?d callback
To enable x86 to use the generic walk_page_range() function, the
callers of ptdump_walk_pgd_level() need to pass an mm_struct rather
than the raw pgd_t pointer. Luckily since commit 7e904a91bf60
("efi: Use efi_mm in x86 as well as ARM") we now have an mm_struct
for EFI on x86.
Signed-off-by: Steve
Since 48684a65b4e3: "mm: pagewalk: fix misbehavior of walk_page_range
for vma(VM_PFNMAP)", page_table_walk() will report any kernel area as
a hole, because it lacks a vma.
This means each arch has re-implemented page table walking when needed,
for example in the per-arch ptdump walker.
Remove the
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
Warning level 3 was used: -Wimplicit-fallthrough=3
Notice that, in this particular case, the code comment is modified
in accordance with what GCC is expecting to find.
This patch is part
> On Feb 15, 2019, at 6:27 AM, Arnaldo Carvalho de Melo wrote:
>
> Em Thu, Feb 14, 2019 at 04:00:10PM -0800, Song Liu escreveu:
>> bpf events are only tracked when opts->bpf_event is enabled. This patch
>> adds command line flag to enable this for perf-top.
>
> Shouldn't this start as enabled
On Fri, Feb 15, 2019 at 04:32:29PM +0100, Antoine Tenart wrote:
> This patch makes the link interrupt handler to avoid calling
> phylink_mac_change when there are no event.
The reasoning being?
>
> Signed-off-by: Antoine Tenart
> ---
> drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 6 +++---
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
Warning level 3 was used: -Wimplicit-fallthrough=3
This patch is part of the ongoing efforts to enable
-Wimplicit-fallthrough.
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/rad
On Fri, Feb 15, 2019 at 6:21 AM Steven Rostedt wrote:
>
> - Have kprobes not use copy_from_user to access kernel addresses
>as this is now considered a security issue.
No, you people are confused.
The problem isn't that it's using a user access function on kernel memory.
The problem is tha
The pull request you sent on Fri, 15 Feb 2019 13:17:43 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-02-15-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/545aabcbdcec6c88faa3dfde506ad1931d119f52
Thank you!
--
Deet-doot-dot, I am a bot.
https:/
On 02/15, Linus Torvalds wrote:
>
> +static inline bool tabspc(char c) { return c == ' ' || c == '\t'; }
> +static inline bool no_tab_or_space(const char *first, const char *last)
> +{
> + // Skip leading space
> + for (;tabspc(*first) ; first++)
> + if (!*first || first == last
The pull request you sent on Fri, 15 Feb 2019 10:49:01 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v5.0-rc5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/dfeae3379836fd0609488e73f4df260af4af2672
Thank you!
--
Deet-doot-dot, I am a b
The pull request you sent on Thu, 14 Feb 2019 14:56:25 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
> for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/02d75040897f37e43cc6df9a7084ecdd20526f1a
Thank you!
--
Deet-doot-dot
The pull request you sent on Thu, 14 Feb 2019 18:00:59 -0800 (PST):
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net refs/heads/master
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6e7bd3b5494620265d39463b9289b7ba872f6df1
Thank you!
--
Deet-doot-dot, I am
The pull request you sent on Fri, 15 Feb 2019 10:47:39 +0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2aba322074de0d6781f4ae6b44d3e792b9bd2243
Thank you!
--
Deet-doot-dot, I am a bot
On Fri, Feb 15, 2019 at 8:48 AM Randy Dunlap wrote:
>
> On 2/14/19 10:03 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190214:
> >
>
> on x86_64:
>
> ld: net/core/lwt_bpf.o: in function `bpf_lwt_xmit_reroute':
> lwt_bpf.c:(.text+0x11e): undefined reference to `ip_route_output_flo
On Fri, Feb 15, 2019 at 5:45 PM Dmitry Vyukov wrote:
>
> On Fri, Feb 15, 2019 at 5:03 PM Jann Horn wrote:
> >
> > On Fri, Feb 15, 2019 at 4:40 PM Dmitry Vyukov wrote:
> > > On Thu, Oct 11, 2018 at 4:18 PM Paolo Bonzini wrote:
> > > > On 10/10/2018 09:58, syzbot wrote:
> > > > > do_invalid_op+0
On Fri, Feb 15, 2019 at 6:10 PM Jann Horn wrote:
>
> On Fri, Feb 15, 2019 at 5:45 PM Dmitry Vyukov wrote:
> >
> > On Fri, Feb 15, 2019 at 5:03 PM Jann Horn wrote:
> > >
> > > On Fri, Feb 15, 2019 at 4:40 PM Dmitry Vyukov wrote:
> > > > On Thu, Oct 11, 2018 at 4:18 PM Paolo Bonzini
> > > > wro
> On Feb 15, 2019, at 6:41 AM, Arnaldo Carvalho de Melo wrote:
>
> Em Thu, Feb 14, 2019 at 04:00:45PM -0800, Song Liu escreveu:
>> To annotate bpf programs in perf, it is necessary to save information in
>> bpf_prog_info and btf. For short living bpf program, it is necessary to
>> save these i
On Fri, Feb 15, 2019 at 04:32:38PM +0100, Antoine Tenart wrote:
> The documentation advises to set the XPCS in reset while reconfiguring
> the serdes lanes. This seems to be a good thing to do, but the PPv2
> driver wasn't doing it. This patch fixes it.
Hmm. That statment seems to have some ambig
On Fri, Feb 15, 2019 at 9:01 AM Kees Cook wrote:
>
> The !*first will never hit here (since it's been checked to be either
> ' ' or '\t', and if first == last it's whitespace all the way, so we
> could just return true here to bail out early (there's no interpreter
> at all, so we want to -ENOEXEC
On Fri, 2019-02-15 at 08:49 -0700, Jens Axboe wrote:
> On 2/15/19 4:13 AM, Ming Lei wrote:
> > This patchset brings multi-page bvec into block layer:
>
> Applied, thanks Ming. Let's hope it sticks!
Hi Jens and Ming,
Test nvmeof-mp/002 fails with Jens' for-next branch from this morning.
I have no
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
Warning level 3 was used: -Wimplicit-fallthrough=3
This patch is part of the ongoing efforts to enable
-Wimplicit-fallthrough.
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/rad
On Fri, Feb 15, 2019 at 04:38:05PM +, Dave Watson wrote:
> There might also be ways to rearrange the file* struct or fd table so
> that we're not taking so many cache misses for sockfd_lookup_light,
> since for sockets we don't use most of the file* struct at all.
I don't think there's too muc
On 2/15/19 9:02 AM, Steven Price wrote:
> arch/x86/mm/dump_pagetables.c | 281 ++
> 1 file changed, 146 insertions(+), 135 deletions(-)
I'll look through this in more detail in a bit. But, I'm a bit bummed
out by the diffstat. When I see patches add a bunch of in
On Thu, Feb 14, 2019 at 11:34 AM Peter Zijlstra wrote:
>
> Something like the below, right?
>
> + frame->flags = 0;
> + frame->flags = 0;
Those are not valid flag values.
Can you popf them? Yes.
Do they make sense? No.
It has the IF flag clear, for example. Is that intentional? If
On Fri, Feb 15, 2019 at 07:56:22AM +0100, Greg Kroah-Hartman wrote:
> On Thu, Feb 14, 2019 at 01:02:26PM -0800, Guenter Roeck wrote:
> > On Wed, Feb 13, 2019 at 07:38:05PM +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.20.9 release.
> > > There are 50
On Fri, 15 Feb 2019 17:00:49 +0100
Daniel Bristot de Oliveira wrote:
> On 2/14/19 3:40 PM, Steven Rostedt wrote:
> > On Thu, 14 Feb 2019 15:30:30 +0100
> > Borislav Petkov wrote:
> >
> >>> void *trampoline;
> >>
> >> Well, it ain't a trampoline either. It is a "temporary location to go
On Fri, Feb 15, 2019 at 6:13 PM Dmitry Vyukov wrote:
> On Fri, Feb 15, 2019 at 6:10 PM Jann Horn wrote:
> > On Fri, Feb 15, 2019 at 5:45 PM Dmitry Vyukov wrote:
> > > On Fri, Feb 15, 2019 at 5:03 PM Jann Horn wrote:
> > > > On Fri, Feb 15, 2019 at 4:40 PM Dmitry Vyukov
> > > > wrote:
> > > >
On 05/02/19 08:50, Nadav Amit wrote:
>> In cases where RCU cannot be used (e.g. because some callees need to RCU
>> synchronise), it might be possible to add a variant that uses
>> synchronize_rcu_tasks() when updating, but this series does not attempt this.
> I wonder why.
Mainly because I have ye
On Fri, 15 Feb 2019 09:08:38 -0800
Linus Torvalds wrote:
> On Fri, Feb 15, 2019 at 6:21 AM Steven Rostedt wrote:
> >
> > - Have kprobes not use copy_from_user to access kernel addresses
> >as this is now considered a security issue.
>
> No, you people are confused.
>
> The problem isn't
> On Fri, Feb 15, 2019 at 04:32:38PM +0100, Antoine Tenart wrote:
> > The documentation advises to set the XPCS in reset while reconfiguring
> > the serdes lanes. This seems to be a good thing to do, but the PPv2
> > driver wasn't doing it. This patch fixes it.
>
> Hmm. That statment seems to h
> On Feb 15, 2019, at 6:26 AM, Arnaldo Carvalho de Melo wrote:
>
> Em Thu, Feb 14, 2019 at 04:00:09PM -0800, Song Liu escreveu:
>> This patch enables perf-record to save btf information as headers to
>> perf.data A new header type HEADER_BTF is introduced for this data.
>
> Jiri,
>
> W
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
Warning level 3 was used: -Wimplicit-fallthrough=3
This patch is part of the ongoing efforts to enable
-Wimplicit-fallthrough.
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/amd
Hi all,
Alex Deucher requested me to send separate patches for each
driver, which makes this patch available to be taken,
again.
Thanks
--
Gustavo
On 2/15/19 10:02 AM, Gustavo A. R. Silva wrote:
> Hi,
>
> Please drop this, as I have included this fix into
> the following patch, which addresses
On 15/02/2019 17:16, Dave Hansen wrote:
> On 2/15/19 9:02 AM, Steven Price wrote:
>> arch/x86/mm/dump_pagetables.c | 281 ++
>> 1 file changed, 146 insertions(+), 135 deletions(-)
>
> I'll look through this in more detail in a bit. But, I'm a bit bummed
> out by t
Hi Jacob, Lu,
On 30/01/2019 19:05, Jacob Pan wrote:
> On Mon, 12 Nov 2018 14:44:57 +0800
> Lu Baolu wrote:
>
>> This adds APIs for IOMMU drivers and device drivers to manage
>> the PASIDs used for DMA transfer and translation. It bases on
>> I/O ASID allocator for PASID namespace management and
501 - 600 of 987 matches
Mail list logo
