From: Vladimir Murzin
Commit 78869f0f0552 ("arm64: Extract parts of el2_setup into a macro")
reorganized el2 setup in such way that virtual cpu id registers set
only in nVHE, yet they used (and need) to be set irrespective VHE
support.
Fixes: 78869f0f0552 ("arm64: Extract parts of el2_setup into
From: J. Bruce Fields
commit 4aa5e002034f0701c3335379fd6c22d7f3338cce upstream.
This reverts commit 50747dd5e47b "nfsd4: remove check_conflicting_opens
warning", as a prerequisite for reverting 94415b06eb8a, which has a
serious bug.
Cc: sta...@vger.kernel.org
Signed-off-by: J. Bruce Fields
Sig
From: J. Bruce Fields
commit 6ee65a773096ab3f39d9b00311ac983be5bdeb7c upstream.
This reverts commit 94415b06eb8aed13481646026dc995f04a3a534a.
That commit claimed to allow a client to get a read delegation when it
was the only writer. Actually it allowed a client to get a read
delegation when *
From: Florian Fainelli
commit f9b3827ee66cfcf297d0acd6ecf33653a5f297ef upstream.
Add support for being able to set the learning attribute on port, and
make sure that the standalone ports start up with learning disabled.
We can remove the code in bcm_sf2 that configured the ports learning
attrib
From: Ard Biesheuvel
commit 86ad60a65f29dd862a11c22bb4b5be28d6c5cef1 upstream.
The XTS asm helper arrangement is a bit odd: the 8-way stride helper
consists of back-to-back calls to the 4-way core transforms, which
are called indirectly, based on a boolean that indicates whether we
are performin
From: Bob Peterson
[ Upstream commit 96b1454f2e8ede4c619fde405a1bb4e9ba8d218e ]
Before this patch, sister functions gfs2_make_fs_rw and gfs2_make_fs_ro locked
(held) the freeze glock by calling gfs2_freeze_lock and gfs2_freeze_unlock.
The problem is, not all the callers of gfs2_make_fs_ro should
From: Bob Peterson
[ Upstream commit c77b52c0a137994ad796f44544c802b0b766e496 ]
Many places in the gfs2 code queued and dequeued the freeze glock.
Almost all of them acquire it in SHARED mode, and need to specify the
same LM_FLAG_NOEXP and GL_EXACT flags.
This patch adds common helper functions
From: Amir Goldstein
commit 775c5033a0d164622d9d10dd0f0a5531639ed3ed upstream.
Commit 5d069dbe8aaf ("fuse: fix bad inode") replaced make_bad_inode()
in fuse_iget() with a private implementation fuse_make_bad().
The private implementation fails to remove the bad inode from inode
cache, so the re
From: Piotr Krysiuk
commit f232326f6966cf2a1d1db7bc917a4ce5f9f55f76 upstream.
The purpose of this patch is to streamline error propagation and in particular
to propagate retrieve_ptr_limit() errors for pointer types that are not defining
a ptr_limit such that register-based alu ops against these
From: Bob Peterson
[ Upstream commit d5bf630f355d8c532bef2347cf90e8ae60a5f1bd ]
Before this patch, function signal_our_withdraw referenced the journal
inode immediately. But corrupt file systems may have some invalid
journals, in which case our attempt to read it in will withdraw and the
resulti
From: Piotr Krysiuk
commit b5871dca250cd391885218b99cc015aca1a51aea upstream.
Instead of having the mov32 with aux->alu_limit - 1 immediate, move this
operation to retrieve_ptr_limit() instead to simplify the logic and to
allow for subsequent sanity boundary checks inside retrieve_ptr_limit().
T
From: Piotr Krysiuk
commit 1b1597e64e1a610c7a96710fc4717158e98a08b3 upstream.
Given we know the max possible value of ptr_limit at the time of retrieving
the latter, add basic assertions, so that the verifier can bail out if
anything looks odd and reject the program. Nothing triggered this so fa
From: Piotr Krysiuk
commit 10d2bb2e6b1d8c4576c56a748f697dbeb8388899 upstream.
retrieve_ptr_limit() computes the ptr_limit for registers with stack and
map_value type. ptr_limit is the size of the memory area that is still
valid / in-bounds from the point of the current position and direction
of
From: Piotr Krysiuk
commit 0a13e3537ea67452d549a6a80da3776d6b7dedb3 upstream.
Fix up test_verifier error messages for the case where the original error
message changed, or for the case where pointer alu errors differ between
privileged and unprivileged tests. Also, add alternative tests for keep
Hello,
Here is the 3rd version of the series to fix the stacktrace with kretprobe
on x86.
The previous version is;
https://lore.kernel.org/bpf/161553130371.1038734.7661319550287837734.stgit@devnote2/
Instead of solving generic stacktrace, this version is focusing on x86
stack unwinders. Anyway
Commit e792ff804f49 ("ia64: kprobes: Use generic kretprobe trampoline handler")
missed to pass the wrong trampoline address (it passes the descriptor address
instead of function entry address).
This fixes it to pass correct trampoline address to
__kretprobe_trampoline_handler().
This also changes
Replace arch_deref_entry_point() with dereference_function_descriptor()
because those are doing same thing.
Signed-off-by: Masami Hiramatsu
---
arch/ia64/kernel/kprobes.c|5 -
arch/powerpc/kernel/kprobes.c | 11 ---
include/linux/kprobes.h |1 -
kernel/kprobes.c
From: Frieder Schrempf
[ Upstream commit f7684f5a048febd2a7bc98ee81d6dce52f7268b8 ]
By default the PCA9450 doesn't handle the assertion of the WDOG_B
signal, but this is required to guarantee that things like software
resets triggered by the watchdog work reliably.
As we don't want to rely on t
On Fri 2021-03-19 18:15:19, Yafang Shao wrote:
> On Fri, Mar 19, 2021 at 6:13 PM Yafang Shao wrote:
> Hi Petr,
>
> Any comments on this version ?
I have been busy this week with some other work. I am going to review
the original v6 either later today or the following week.
Best Regards,
Petr
P
Remove trampoline_address from kretprobe_trampoline_handler().
Instead of passing the address, kretprobe_trampoline_handler()
can use new kretprobe_trampoline_addr().
Signed-off-by: Masami Hiramatsu
---
Changes in v3:
- Remove wrong kretprobe_trampoline declaration from
arch/x86/include/
Add kretprobe_find_ret_addr() for searching correct return address
from kretprobe instance list.
Signed-off-by: Masami Hiramatsu
---
Changes in v3:
- Remove generic stacktrace fixup. Instead, it should be solved in
each unwinder. This just provide the generic interface.
Changes in v2:
-
From: Josh Poimboeuf
Add UNWIND_HINT_FUNC on kretporbe_trampoline code so that ORC
information is generated on the kretprobe_trampoline correctly.
Signed-off-by: Josh Poimboeuf
---
[MH] Add patch description.
---
arch/x86/include/asm/unwind_hints.h |5 +
arch/x86/kernel/kprobes/core.c
Add instruction_pointer_set() API for arc.
Signed-off-by: Masami Hiramatsu
---
arch/arc/include/asm/ptrace.h |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arc/include/asm/ptrace.h b/arch/arc/include/asm/ptrace.h
index 4c3c9be5bd16..cca8d6583e31 100644
--- a/arch/arc/include/as
Add instruction_pointer_set() API for ia64.
Signed-off-by: Masami Hiramatsu
---
arch/ia64/include/asm/ptrace.h |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/ia64/include/asm/ptrace.h b/arch/ia64/include/asm/ptrace.h
index b3aa46090101..e382f1a6bff3 100644
---
To simplify the stacktrace with pt_regs from kretprobe handler,
set the correct return address to the instruction pointer in
the pt_regs before calling kretprobe handlers.
Suggested-by: Josh Poimboeuf
Signed-off-by: Masami Hiramatsu
---
Changes in v3:
- Cast the correct_ret_addr to unsigned l
This changes x86/kretprobe stack frame on kretprobe_trampoline
a bit, which now push the kretprobe_trampoline as a fake return
address at the bottom of the stack frame. With this fix, the ORC
unwinder will see the kretprobe_trampoline as a return address.
Signed-off-by: Masami Hiramatsu
Suggested
ftrace shows "[unknown/kretprobe'd]" indicator all addresses in the
kretprobe_trampoline, but the modified address by kretprobe should
be only kretprobe_trampoline+0.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_output.c | 17 -
1 file changed, 4 insertions(+), 13 del
Since the kretprobe replaces the function return address with
the kretprobe_trampoline on the stack, x86 unwinders can not
continue the stack unwinding at that point, or record
kretprobe_trampoline instead of correct return address.
To fix this issue, find the correct return address from task's
kr
The following commit has been merged into the locking/urgent branch of tip:
Commit-ID: 68b1eddd421d2b16c6655eceb48918a1e896bbbc
Gitweb:
https://git.kernel.org/tip/68b1eddd421d2b16c6655eceb48918a1e896bbbc
Author:Peter Zijlstra
AuthorDate:Thu, 18 Mar 2021 11:27:19 +01:00
Com
The following commit has been merged into the locking/urgent branch of tip:
Commit-ID: 698bacefe993ad2922c9d3b1380591ad489355e9
Gitweb:
https://git.kernel.org/tip/698bacefe993ad2922c9d3b1380591ad489355e9
Author:Peter Zijlstra
AuthorDate:Thu, 18 Mar 2021 11:29:56 +01:00
Com
The following commit has been merged into the locking/urgent branch of tip:
Commit-ID: 38c93587375053c5b9ef093f4a5ea754538cba32
Gitweb:
https://git.kernel.org/tip/38c93587375053c5b9ef093f4a5ea754538cba32
Author:Peter Zijlstra
AuthorDate:Thu, 18 Mar 2021 11:31:51 +01:00
Com
On Thu, Mar 18, 2021 at 09:41:54AM +0100, Arnd Bergmann wrote:
> On Wed, Mar 17, 2021 at 5:18 PM Catalin Marinas
> wrote:
> >
> > On Wed, Mar 17, 2021 at 02:37:57PM +, Catalin Marinas wrote:
> > > On Thu, Feb 25, 2021 at 12:20:56PM +0100, Arnd Bergmann wrote:
> > > > diff --git a/arch/arm64/k
On Fri, Mar 19, 2021 at 09:57:50AM +, Colin King wrote:
> From: Colin Ian King
>
> There is a spelling mistake in a dev_err message. Fix it.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/iommu/sprd-iommu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
>
>
On 3/19/21 1:19 PM, Greg Kroah-Hartman wrote:
From: Andy Shevchenko
[ Upstream commit b41ba2ec54a70908067034f139aa23d0dd2985ce ]
On STM32MP1, the GPIO banks are subnodes of pin-controller@50002000,
see arch/arm/boot/dts/stm32mp151.dtsi. The driver for
pin-controller@50002000 is in drivers/pinc
On Thu, Mar 18, 2021 at 04:48:43PM -0700, Sami Tolvanen wrote:
> On Thu, Mar 18, 2021 at 3:29 PM Peter Zijlstra wrote:
> >
> > On Thu, Mar 18, 2021 at 10:10:55AM -0700, Sami Tolvanen wrote:
> > > +static void update_shadow(struct module *mod, unsigned long base_addr,
> > > + update_sha
On Thu, Mar 18, 2021 at 03:26:13PM -0500, Madhavan T. Venkataraman wrote:
> On 3/18/21 10:09 AM, Mark Brown wrote:
> > If we are going to add the extra record there would probably be less
> > potential for confusion if we pointed it at some sensibly named dummy
> > function so anything or anyone t
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: 21d6a7dcbfba5e7b31f4e9d555a9be362578bfc3
Gitweb:
https://git.kernel.org/tip/21d6a7dcbfba5e7b31f4e9d555a9be362578bfc3
Author:Jiapeng Chong
AuthorDate:Tue, 09 Mar 2021 17:59:23 +08:00
Commit
On Mon, Mar 01, 2021 at 10:02:06AM +0530, Anshuman Khandual wrote:
> early_memtest() does not get called from all architectures. Hence enabling
> CONFIG_MEMTEST and providing a valid memtest=[1..N] kernel command line
> option might not trigger the memory pattern tests as would be expected in
> nor
On Fri, 2021-03-19 at 11:43 +, Alexander Lobakin wrote:
> I'm not sure if you did it on purpose in commit aaa5d90b395a7
> ("net: use indirect call wrappers at GRO network layer").
> Was that intentional
I must admit that 2y+ later my own intentions are not so clear to me
too;)
> for the sake
In hist__find_annotations function, since different hist_entry may point to same
symbol, we free notes->src to signal already processed this symbol in stdio
mode;
when annotate, entry will skipped if notes->src is NULL to avoid repeated
output.
However, there is a problem, for example, run the f
On 19.03.21 13:15, Muchun Song wrote:
On Fri, Mar 19, 2021 at 4:59 PM Oscar Salvador wrote:
On Mon, Mar 15, 2021 at 05:20:14PM +0800, Muchun Song wrote:
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -34,6 +34,7 @@
#include
#include
#include
+#include
#include
#inc
On Fri, Mar 19, 2021 at 01:27:23PM +0100, Marek Vasut wrote:
> On 3/19/21 1:19 PM, Greg Kroah-Hartman wrote:
> > From: Andy Shevchenko
> >
> > [ Upstream commit b41ba2ec54a70908067034f139aa23d0dd2985ce ]
> >
> > On STM32MP1, the GPIO banks are subnodes of pin-controller@50002000,
> > see arch/ar
> On Mar 18, 2021, at 11:05 PM, Peter Zijlstra wrote:
>
> On Thu, Mar 18, 2021 at 09:26:58AM +0800, changhuaixin wrote:
>>> On Mar 17, 2021, at 4:06 PM, Peter Zijlstra wrote:
>
>>> So what is the typical avg,stdev,max and mode for the workloads where you
>>> find
>>> you need this?
>>>
>>>
On 03/13/21 at 02:35am, menglong8.d...@gmail.com wrote:
> From: Zhang Yunkai
>
> 'linux/pgtable.h' included in 'crash_dump.h' is duplicated.
> It is also included in the 8th line.
Tian Tao posted one to address the same issue, his log is better. Please
update with below to repost.
linux/pgtable
On 3/18/21 11:55 PM, Leon Romanovsky wrote:
On Thu, Mar 18, 2021 at 11:29:22PM -0500, Alex Elder wrote:
Create a new macro ipa_assert() to verify that a condition is true.
This produces a build-time error if the condition can be evaluated
at build time; otherwise __ipa_assert_runtime() is called
On 2021/3/18 14:13, Namhyung Kim wrote:
Hello,
On Wed, Mar 17, 2021 at 6:44 PM Yang Jihong wrote:
In hist__find_annotations function, since different hist_entry may point to same
symbol, we free notes->src to signal already processed this symbol in stdio
mode;
when annotate, entry will sk
On 3/19/21 12:00 AM, Leon Romanovsky wrote:
On Thu, Mar 18, 2021 at 11:29:23PM -0500, Alex Elder wrote:
Convert some commented assertion statements into real calls to
ipa_assert(). If the IPA device pointer is available, provide it,
otherwise pass NULL for that.
There are lots more places to c
This LTE modem (M.2 card) has a bug in its power managment:
there is some kind of race condition for U3 wake-up between the host and
the device. The modem firmware sometimes crashes/locks when both events
happen at the same time and the modem fully drops off the USB bus (and
sometimes re-enumerates
On 19.03.21 13:36, David Hildenbrand wrote:
On 19.03.21 13:15, Muchun Song wrote:
On Fri, Mar 19, 2021 at 4:59 PM Oscar Salvador wrote:
On Mon, Mar 15, 2021 at 05:20:14PM +0800, Muchun Song wrote:
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -34,6 +34,7 @@
#include
#incl
Get pll_cmnlc and pll_cmnlc1 optional clocks and enable them.
This will enable REFRCV/1 in case the pll_cmnlc/1 takes input
from REFRCV/1 respectively.
Signed-off-by: Kishon Vijay Abraham I
Reviewed-by: Swapnil Jakhade
---
drivers/phy/cadence/phy-cadence-sierra.c | 40 ++--
Patch series adds support in Sierra driver to use external clock.
v1 of the patch series can be found @ [1]
v2 of the patch series can be found @ [2]
v3 of the patch series can be found @ [3]
v4 of the patch series can be found @ [5]
v5 of the patch series can be found @ [6]
v6 of the patch series
Commit 44d30d622821d ("phy: cadence: Add driver for Sierra PHY")
de-asserts PHY_RESET even before the configurations are loaded in
phy_init(). However PHY_RESET should be de-asserted only after
all the configurations has been initialized, instead of de-asserting
in probe. Fix it here.
Fixes: 44d30
Invoke wiz_init() before configuring anything else in Sierra/Torrent
(invoked as part of of_platform_device_create()). wiz_init() resets the
SERDES device and any configuration done in the probe() of
Sierra/Torrent will be lost. In order to prevent SERDES configuration
from getting reset, invoke wi
"serdes" node (child node of WIZ) can have sub-nodes for representing links
or it can have sub-nodes for representing the various clocks within the
serdes. Instead of trying to read "reg" from every child node used for
assigning "lane_phy_type", read only if the child node's name is "phy"
or "link"
Cadence Sierra PHY driver registers PHY using devm_phy_create()
for all sub-nodes of Sierra device tree node. However Sierra device
tree node can have sub-nodes for the various clocks in addtion to the
PHY. Use devm_phy_create() only for nodes with name "phy" (or "link"
for old device tree) which r
No functional change. Group devm_reset_control_get() and
devm_reset_control_get_optional() to a separate function.
Signed-off-by: Kishon Vijay Abraham I
Reviewed-by: Philipp Zabel
---
drivers/phy/cadence/phy-cadence-sierra.c | 36
1 file changed, 25 insertions(+), 11 de
No functional change. Group all devm_clk_get_optional() to a
separate function.
Signed-off-by: Kishon Vijay Abraham I
Reviewed-by: Swapnil Jakhade
---
drivers/phy/cadence/phy-cadence-sierra.c | 57 +++-
1 file changed, 35 insertions(+), 22 deletions(-)
diff --git a/drivers/
GFP_KERNEL|__GFP_ZERO);
Use kcalloc().
Code identation is wrong, please use checkpatch.
> + if (ZERO_OR_NULL_PTR(cma_stats))
> + goto out;
> +
> + do {
> + cma = &cma_areas[i];
> + cma->stat = &cma_stats[i
No functional change. Since the reset controls obtained in
Sierra is exclusively used by the Sierra device, use
exclusive reset control request API calls.
Signed-off-by: Kishon Vijay Abraham I
Reviewed-by: Philipp Zabel
---
drivers/phy/cadence/phy-cadence-sierra.c | 4 ++--
1 file changed, 2 in
Instead of having separate structure members for each input clock, add
an array for the input clocks within "struct cdns_sierra_phy". This is
in preparation for adding more input clocks required for supporting
additional clock combination.
Signed-off-by: Kishon Vijay Abraham I
Reviewed-by: Swapni
No functional change. In order to have a single header file for all
Cadence SERDES move phy-cadence-torrent.h to phy-cadence.h. This is
in preparation for adding Cadence Sierra SERDES specific macros.
Signed-off-by: Kishon Vijay Abraham I
Reviewed-by: Swapnil Jakhade
---
.../devicetree/bindings
commit 44d30d622821 ("phy: cadence: Add driver for Sierra PHY") enabled
the clock in probe and failed to disable in remove callback. Add missing
clk_disable_unprepare() in cdns_sierra_phy_remove().
Fixes: 44d30d622821 ("phy: cadence: Add driver for Sierra PHY")
Signed-off-by: Kishon Vijay Abraham
Add #clock-cells binding to model Sierra as clock provider and include
clock IDs for PLL_CMNLC and PLL_CMNLC1.
Signed-off-by: Kishon Vijay Abraham I
Reviewed-by: Rob Herring
---
.../bindings/phy/phy-cadence-sierra.yaml| 17 -
include/dt-bindings/phy/phy-cadence.h
Sierra has two PLLs, PLL_CMNLC and PLL_CMNLC1 and each of these PLLs has
two inputs, plllc_refclk (input from pll0_refclk) and refrcv (input from
pll1_refclk). Model PLL_CMNLC and PLL_CMNLC1 as clocks so that it's
possible to select one of these two inputs from device tree.
Signed-off-by: Kishon V
On 3/19/21 1:36 PM, Greg Kroah-Hartman wrote:
On Fri, Mar 19, 2021 at 01:27:23PM +0100, Marek Vasut wrote:
On 3/19/21 1:19 PM, Greg Kroah-Hartman wrote:
From: Andy Shevchenko
[ Upstream commit b41ba2ec54a70908067034f139aa23d0dd2985ce ]
On STM32MP1, the GPIO banks are subnodes of pin-controll
On Fri, Mar 19, 2021 at 1:41 PM Vincent Palatin wrote:
>
> This LTE modem (M.2 card) has a bug in its power managment:
> there is some kind of race condition for U3 wake-up between the host and
> the device. The modem firmware sometimes crashes/locks when both events
> happen at the same time and
On Fri, Mar 19, 2021 at 10:58:41AM +0100, Jean-Philippe Brucker wrote:
> Although there is no use for it at the moment (only two upstream users and
> it looks like amdkfd always uses current too), I quite like the
> client-server model where the privileged process does bind() and programs
> the ha
This LTE modem (M.2 card) has a bug in its power management:
there is some kind of race condition for U3 wake-up between the host and
the device. The modem firmware sometimes crashes/locks when both events
happen at the same time and the modem fully drops off the USB bus (and
sometimes re-enumerate
All the drivers that implement HDR output call pretty much the same
function to initialise the hdr_output_metadata property, and while the
creation of that property is in a helper, every driver uses the same
code to attach it.
Provide a helper for it as well
Signed-off-by: Maxime Ripard
---
...
All the drivers that support the HDR metadata property have a similar
function to compare the metadata from one connector state to the next,
and force a mode change if they differ.
All these functions run pretty much the same code, so let's turn it into
an helper that can be shared across those dr
From: Dave Stevenson
Now that we can export deeper colour depths, add in the signalling
for HDR metadata.
Signed-off-by: Dave Stevenson
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/vc4/vc4_hdmi.c | 53 ++
drivers/gpu/drm/vc4/vc4_hdmi.h | 3 ++
2 files chan
> On Mar 18, 2021, at 8:59 PM, Phil Auld wrote:
>
> On Thu, Mar 18, 2021 at 09:26:58AM +0800 changhuaixin wrote:
>>
>>
>>> On Mar 17, 2021, at 4:06 PM, Peter Zijlstra wrote:
>>>
>>> On Wed, Mar 17, 2021 at 03:16:18PM +0800, changhuaixin wrote:
>>>
> Why do you allow such a large burst
From: Paolo Abeni
Date: Fri, 19 Mar 2021 13:35:41 +0100
> On Fri, 2021-03-19 at 11:43 +, Alexander Lobakin wrote:
> > I'm not sure if you did it on purpose in commit aaa5d90b395a7
> > ("net: use indirect call wrappers at GRO network layer").
> > Was that intentional
>
> I must admit that 2y+
Hi René,Ilya
> Gesendet: Freitag, 19. März 2021 um 11:25 Uhr
> Von: "René van Dorst"
> Hi Ilya,
>
> Thanks for fixing this issue.
>
> I remember that Frank also had an issue with TRGMII on his MT7623 ARM board.
> I never found why it did not work but this may be also fix his issue
> on the MT
On Tue, Mar 16, 2021 at 08:10:49AM -0700, Yu-cheng Yu wrote:
> To deliver a signal, create a shadow stack restore token and put the token
> and the signal restorer address on the shadow stack. For sigreturn, verify
> the token and restore from it the shadow stack pointer.
>
> A shadow stack resto
Rather than have separate opaque setter functions that are easy to
overlook and lead to repetitive boilerplate in drivers, let's pass the
relevant initialisation parameters directly to iommu_device_register().
Signed-off-by: Robin Murphy
---
drivers/iommu/amd/init.c| 3 +--
It happens that the 3 drivers which first supported being modular are
also ones which play games with their pgsize_bitmap, so have non-const
iommu_ops where dynamically setting the owner manages to work out OK.
However, it's less than ideal to force that upon all drivers which want
to be modular -
On Thu, Mar 18, 2021 at 02:37:03PM -0400, Richard Guy Briggs wrote:
> On 2021-03-18 17:30, Phil Sutter wrote:
[...]
> > Why did you leave the object-related logs in place? They should reappear
> > at commit time just like chains and sets for instance, no?
>
> There are other paths that can trigger
Hi Linus,
Did you have a chance to take a look at my reply below? I would greatly
appreciate your feedback to decide how I should restructure this code moving
forward.
Thank you.
Asmaa
-Original Message-
From: Asmaa Mnebhi
Sent: Wednesday, March 10, 2021 3:38 PM
To: Asmaa Mnebhi ; li
The following commit has been merged into the locking/core branch of tip:
Commit-ID: aa3a5f31877e5dc131cc286ce707413d441c8375
Gitweb:
https://git.kernel.org/tip/aa3a5f31877e5dc131cc286ce707413d441c8375
Author:Waiman Long
AuthorDate:Thu, 18 Mar 2021 13:28:13 -04:00
Committe
The following commit has been merged into the locking/core branch of tip:
Commit-ID: 5261ced47f8e89173c3b015f6152a05f11a418c3
Gitweb:
https://git.kernel.org/tip/5261ced47f8e89173c3b015f6152a05f11a418c3
Author:Waiman Long
AuthorDate:Thu, 18 Mar 2021 13:28:12 -04:00
Committe
The following commit has been merged into the locking/core branch of tip:
Commit-ID: 8c52cca04f97a4c09ec2f0bd8fe6d0cdf49834e4
Gitweb:
https://git.kernel.org/tip/8c52cca04f97a4c09ec2f0bd8fe6d0cdf49834e4
Author:Waiman Long
AuthorDate:Thu, 18 Mar 2021 13:28:14 -04:00
Committe
The following commit has been merged into the locking/core branch of tip:
Commit-ID: 2ea55bbba23e9d36996299664d618393c8602646
Gitweb:
https://git.kernel.org/tip/2ea55bbba23e9d36996299664d618393c8602646
Author:Waiman Long
AuthorDate:Thu, 18 Mar 2021 13:28:11 -04:00
Committe
During crtc disable, display perf structures are reset to 0
which includes state varibles which are immutable. On crtc
enable, we use the same structures and they don't refelect
the actual values
1) Fix is to avoid updating the state structures during disable.
2) Reset the perf structures during a
Hi Paul,
I'll post a v2 shortly but will address your comments here.
> > include/linux/lsm_hooks.h | 7 +++
> > include/linux/security.h | 5 +
> > net/vmw_vsock/af_vsock.c | 1 +
> > security/security.c | 5 +
> > security/selinux/hooks.c | 10 ++
On 2021-03-18 23:47, Dario Binacchi wrote:
Il 17/03/2021 09:19 Tomi Valkeinen ha scritto:
On 14/03/2021 17:13, Dario Binacchi wrote:
> As reported by TI spruh73x RM, the LCD pixel clock (LCD_PCLK) frequency
> is obtained by dividing LCD_CLK, the LCD controller reference clock,
> for CLKDIV:
>
On 2021-03-19 13:52, Phil Sutter wrote:
> On Thu, Mar 18, 2021 at 02:37:03PM -0400, Richard Guy Briggs wrote:
> > On 2021-03-18 17:30, Phil Sutter wrote:
> [...]
> > > Why did you leave the object-related logs in place? They should reappear
> > > at commit time just like chains and sets for instanc
On Thu, Mar 18, 2021 at 05:58:38PM +0100, Peter Zijlstra wrote:
> > For CONFIG_MODULE_UNLOAD, the code ends up in the normal text area, so
> > static_call_is_init() is false and kernel_text_address() is true.
> >
> > For !CONFIG_MODULE_UNLOAD, the code gets discarded during module load,
> > so st
On Thu, Mar 18, 2021 at 07:34:56PM +0100, Enrico Weigelt, metux IT consult
wrote:
> On 18.03.21 18:22, Leon Romanovsky wrote:
>
> > Which email client do you use?
> > Your responses are grouped as one huge block without any chance to respond
> > to you on specific point or answer to your question
On 3/19/21 3:47 AM, Dan Carpenter wrote:
> On Thu, Mar 18, 2021 at 02:42:33PM -0600, Jens Axboe wrote:
>> On 3/18/21 2:24 PM, Colin Ian King wrote:
>>> On 18/03/2021 20:12, Jens Axboe wrote:
On 3/18/21 9:16 AM, Colin King wrote:
> From: Colin Ian King
>
> The 3rd argument to alloc
On Thu, Mar 18, 2021 at 03:19:00PM +0100, Thomas Bogendoerfer wrote:
> On Thu, Mar 18, 2021 at 05:57:04AM +0100, Christoph Hellwig wrote:
> > arch/mips/configs/malta_kvm_guest_defconfig | 3 ---
>
> that file is gone in mips-next.
>
> I could take all MIPS patches into mips-next, if you want...
On 3/19/21 3:59 AM, Krzysztof Kozlowski wrote:
> On 18/03/2021 21:42, Jens Axboe wrote:
>> On 3/18/21 2:24 PM, Colin Ian King wrote:
>>> On 18/03/2021 20:12, Jens Axboe wrote:
On 3/18/21 9:16 AM, Colin King wrote:
> From: Colin Ian King
>
> The 3rd argument to alloc_workqueue shou
On Thu, Mar 18, 2021 at 11:13:44PM +0530, Amey Narkhede wrote:
> On 21/03/18 07:35PM, Leon Romanovsky wrote:
> > On Thu, Mar 18, 2021 at 10:31:43PM +0530, Amey Narkhede wrote:
> > > On 21/03/18 04:57PM, Leon Romanovsky wrote:
> > > > On Thu, Mar 18, 2021 at 07:52:52PM +0530, Amey Narkhede wrote:
>
Hi Christoph
While backporting the patch I realised of a bug.
On Sat, Mar 13, 2021 at 12:55 AM Ricardo Ribalda wrote:
>
> On architectures where there is no coherent caching such as ARM use the
> dma_alloc_noncontiguous API and handle manually the cache flushing using
> dma_sync_sgtable().
>
> I
Hi Alistair,
the patch looks quite good only a few notes inline.
PS: It would be cool to have a log to previous patch versions.
On 21-03-15 22:27, Alistair Francis wrote:
...
> +&crypto {
> + status = "disabled";
> +};
Why do you disable the crypto subsystem?
> +&dma_apbh {
> + statu
On Thu, Mar 18, 2021 at 06:58:25PM +0100, Enrico Weigelt, metux IT consult
wrote:
> On 18.03.21 18:35, Leon Romanovsky wrote:
>
> > I see it as a good example of cheap solution. Vendor won't fix your
> > touchpad because distros provide workaround. The same will be with reset.
>
> Usually, vendo
On Thu, Mar 18, 2021 at 09:03:33PM -0700, Florian Fainelli wrote:
> #ifdef CONFIG_ARM_LPAE
> + if (swiotlb_force == SWIOTLB_FORCE ||
> + max_pfn > arm_dma_pfn_limit)
Does arm_dma_pfn_limit do the right thing even with the weirdest
remapping ranges? Maybe a commen here would be useful
For AF_VSOCK, accept() currently returns sockets that are unlabelled.
Other socket families derive the child's SID from the SID of the parent
and the SID of the incoming packet. This is typically done as the
connected socket is placed in the queue that accept() removes from.
Reuse the existing 'se
On 3/19/21 2:02 AM, Stefan Metzmacher wrote:
>
> Am 19.03.21 um 00:25 schrieb Jens Axboe:
>> On 3/18/21 5:16 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Commit
>>>
>>> c2c6c067c050 ("io_uring: remove structures from include/linux/io_uring.h")
>>>
>>> is missing a Signed-off-by from its autho
On Fri, Mar 19, 2021 at 02:05:21PM +0100, Ricardo Ribalda wrote:
> > + uvc_urb->sgt,
> > + uvc_stream_dir(uvc_urb->stream));
> > + return usb_submit_urb(uvc_urb->urb, GFP_KERNEL);
> > +}
>
> We should have mem_flags instead
501 - 600 of 1480 matches
Mail list logo
