On 10/2/24 5:31 PM, Corentin LABBE wrote:
> Hello
>
> I have a 8335-GCA POWER8 which got a kernel crash during boot:
> [ 11.754238] Kernel attempted to read user page (0) - exploit attempt?
> (uid: 0)
> [ 11.754437] BUG: Kernel NULL pointer dereference on read at 0x
> [ 11.754499
On 01/10/24 8:23 pm, Alexei Starovoitov wrote:
On Tue, Oct 1, 2024 at 12:18 AM Hari Bathini wrote:
On 30/09/24 6:25 pm, Alexei Starovoitov wrote:
On Sun, Sep 29, 2024 at 10:33 PM Hari Bathini wrote:
On 17/09/24 1:20 pm, Alexei Starovoitov wrote:
On Sun, Sep 15, 2024 at 10:58 PM Har
Hello Kasan/kfence-devs,
Wanted your inputs on this kfence kunit test [PATCH-1] and it's respective
powerpc fix [Patch-2]. The commit msgs has a good description of it. I
see that the same problem was noticed on s390 as well [1] a while ago.
So that makes me believe that maybe we should have a
On 02 October 2024 at 3:43pm, Hoi Pok Wu wrote:
Thanks to Christophe.
I have figured out what happened.
The connector is registered before the device,
where drm_connector_register() states that,
drm_dev_register() has to be called before it.
Assuming this is the fix, I will send the patch for t
if (ret)
goto err;
- }
ret = tsa_of_parse_tdm_tx_route(tsa, tdm_np, tsa->tdms, tdm_id);
- if (ret) {
- of_node_put(tdm_np);
+ if (ret)
goto err;
- }
tdm->is_enable = true;
}
---
base-commit: fe21733536749bb1b31c9c84e0b8d2ab8d82ce13
change-id: 20241002-tsa-scoped-7565f74fe3c0
Best regards,
--
Javier Carrasco
From: Markus Elfring
Date: Wed, 2 Oct 2024 21:50:27 +0200
An of_node_put(bk_node) call was immediately used after a pointer check
for an of_get_property() call in this function implementation.
Thus call such a function only once instead directly before the check.
This issue was transformed by us
On Wed, Oct 02, 2024 at 01:58:15PM +0100, Maciej W. Rozycki wrote:
> On Tue, 1 Oct 2024, Matthew W Carlis wrote:
>
> > I just wanted to follow up with our testing results for the mentioned
> > patches. It took me a while to get them running in our test pool, but
> > we just got it going yesterday
Le 02/10/2024 à 22:02, Markus Elfring a écrit :
From: Markus Elfring
Date: Wed, 2 Oct 2024 21:50:27 +0200
An of_node_put(bk_node) call was immediately used after a pointer check
for an of_get_property() call in this function implementation.
Thus call such a function only once instead directl
On Mon, Sep 16 2024 at 22:20, Christophe JAILLET wrote:
> Le 11/09/2024 à 07:13, Anna-Maria Behnsen a écrit :
>
> not directly related to your serie, but some time ago I sent a patch to
> micro-optimize Optimize usleep_range(). (See [1])
>
> The idea is that the 2 parameters of usleep_range() are
On Fri, 13 Sep 2024 14:04:06 PDT (-0700), Charlie Jenkins wrote:
> On Fri, Sep 13, 2024 at 08:41:34AM +0100, Lorenzo Stoakes wrote:
>> On Wed, Sep 11, 2024 at 11:18:12PM GMT, Charlie Jenkins wrote:
>> > On Wed, Sep 11, 2024 at 07:21:27PM +0100, Catalin Marinas wrote:
>> > > On Tue, Sep 10, 2024 at
Thanks to Christophe.
I have figured out what happened.
The connector is registered before the device,
where drm_connector_register() states that,
drm_dev_register() has to be called before it.
Assuming this is the fix, I will send the patch for testing soon.
On Tue, Oct 1, 2024 at 8:23 PM Christ
On Tue, 1 Oct 2024, Matthew W Carlis wrote:
> I just wanted to follow up with our testing results for the mentioned
> patches. It took me a while to get them running in our test pool, but
> we just got it going yesterday and the initial results look really good.
> We will continue running them in
Hello
I have a 8335-GCA POWER8 which got a kernel crash during boot:
[ 11.754238] Kernel attempted to read user page (0) - exploit attempt? (uid:
0)
[ 11.754437] BUG: Kernel NULL pointer dereference on read at 0x
[ 11.754499] Faulting instruction address: 0xc00c3758
[ 11.7
Hi Christophe,
On Wed, Oct 02, 2024 at 12:10:08PM GMT, Christophe Leroy wrote:
> Le 02/10/2024 à 10:54, Thomas Weißschuh a écrit :
> > On Wed, Oct 02, 2024 at 10:39:28AM GMT, Christophe Leroy wrote:
> > > The page containing VDSO time data is swapped with the one containing
> > > TIME namespace da
On 06. 09. 24 11:43, Shengjiu Wang wrote:
This function is base on the accelerator implementation
for compress API:
https://patchwork.kernel.org/project/alsa-devel/patch/20240731083843.59911-1-pe...@perex.cz/
Audio signal processing also has the requirement for memory to
memory similar as Video.
Le 02/10/2024 à 10:54, Thomas Weißschuh a écrit :
[Vous ne recevez pas souvent de courriers de thomas.weisssc...@linutronix.de.
D?couvrez pourquoi ceci est important ?
https://aka.ms/LearnAboutSenderIdentification ]
Hi Christophe,
On Wed, Oct 02, 2024 at 10:39:28AM GMT, Christophe Leroy wr
On Mon, Sep 16 2024 at 15:20, Costa Shulyupin wrote:
> Interrupts disturb real-time tasks on affined cpus.
> To ensure CPU isolation for real-time tasks, interrupt handling must
> be adjusted accordingly.
> Non-managed interrupts can be configured from userspace,
> while managed interrupts require
On Mon, Sep 16 2024 at 15:20, Costa Shulyupin wrote:
> +/*
> + * housekeeping_update - change housekeeping.cpumasks[type] and propagate the
> + * change.
> + */
> +static int housekeeping_update(enum hk_type type, const struct cpumask
> *update)
> +{
> + struct {
> + struct cpumask
Hi Christophe,
On Wed, Oct 02, 2024 at 10:39:28AM GMT, Christophe Leroy wrote:
> The page containing VDSO time data is swapped with the one containing
> TIME namespace data when a process uses a non-root time namespace.
> For other data like powerpc specific data and RNG data, it means
> tracking
On 9/30/24 20:20, Julia Lawall wrote:
> Reorganize kerneldoc parameter names to match the parameter
> order in the function header.
>
> Problems identified using Coccinelle.
>
> Signed-off-by: Julia Lawall
>
> ---
> arch/powerpc/platforms/ps3/interrupt.c |2 +-
> arch/powerpc/platforms/ps
On 9/30/24 11:32, Shen Lichuan wrote:
> Fixed some confusing typos that were currently identified with codespell,
> the details are as follows:
>
> -in the code comments:
> drivers/ps3/ps3-lpm.c:94: rigths ==> rights
> drivers/ps3/ps3-sys-manager.c:365: acnowledge ==> acknowledge
> drivers/ps3/ps3
VDSO time functions do not call any other function, so they don't
need to save/restore LR. However, retrieving the address of VDSO data
page requires using LR hence saving then restoring it, which can be
heavy on some CPUs. On the other hand, VDSO functions on powerpc are
not standard functions and
The page containing VDSO time data is swapped with the one containing
TIME namespace data when a process uses a non-root time namespace.
For other data like powerpc specific data and RNG data, it means
tracking whether time namespace is the root one or not to know which
page to use.
Simplify the l
23 matches
Mail list logo
