[PATCH] net: remove sb1000 cable modem driver

[Arnd Bergmann]

From: Arnd Bergmann 

This one is hilariously outdated, it provided a faster downlink over
TV cable for users of analog modems in the 1990s, through an ISA card.

The web page for the userspace tools has been broken for 25 years, and
the driver has only ever seen mechanical updates.

Link: 
http://web.archive.org/web/2611165545/http://home.adelphia.net:80/~siglercm/sb1000.html
Signed-off-by: Arnd Bergmann 
---
 .../networking/device_drivers/cable/index.rst |   18 -
 .../device_drivers/cable/sb1000.rst   |  222 
 .../networking/device_drivers/index.rst   |1 -
 arch/powerpc/configs/ppc6xx_defconfig |1 -
 drivers/acpi/acpi_pnp.c   |2 -
 drivers/net/Kconfig   |   24 -
 drivers/net/Makefile  |1 -
 drivers/net/sb1000.c  | 1179 -
 include/uapi/linux/if_cablemodem.h|   23 -
 9 files changed, 1471 deletions(-)
 delete mode 100644 Documentation/networking/device_drivers/cable/index.rst
 delete mode 100644 Documentation/networking/device_drivers/cable/sb1000.rst
 delete mode 100644 drivers/net/sb1000.c
 delete mode 100644 include/uapi/linux/if_cablemodem.h

diff --git a/Documentation/networking/device_drivers/cable/index.rst 
b/Documentation/networking/device_drivers/cable/index.rst
deleted file mode 100644
index cce3c4392972..
--- a/Documentation/networking/device_drivers/cable/index.rst
+++ /dev/null
@@ -1,18 +0,0 @@
-.. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
-
-Cable Modem Device Drivers
-==
-
-Contents:
-
-.. toctree::
-   :maxdepth: 2
-
-   sb1000
-
-.. only::  subproject and html
-
-   Indices
-   ===
-
-   * :ref:`genindex`
diff --git a/Documentation/networking/device_drivers/cable/sb1000.rst 
b/Documentation/networking/device_drivers/cable/sb1000.rst
deleted file mode 100644
index c8582ca4034d..
--- a/Documentation/networking/device_drivers/cable/sb1000.rst
+++ /dev/null
@@ -1,222 +0,0 @@
-.. SPDX-License-Identifier: GPL-2.0
-
-===
-SB100 device driver
-===
-
-sb1000 is a module network device driver for the General Instrument (also known
-as NextLevel) SURFboard1000 internal cable modem board.  This is an ISA card
-which is used by a number of cable TV companies to provide cable modem access.
-It's a one-way downstream-only cable modem, meaning that your upstream net link
-is provided by your regular phone modem.
-
-This driver was written by Franco Venturi .  He deserves
-a great deal of thanks for this wonderful piece of code!
-
-Needed tools
-
-
-Support for this device is now a part of the standard Linux kernel.  The
-driver source code file is drivers/net/sb1000.c.  In addition to this
-you will need:
-
-1. The "cmconfig" program.  This is a utility which supplements "ifconfig"
-   to configure the cable modem and network interface (usually called "cm0");
-
-2. Several PPP scripts which live in /etc/ppp to make connecting via your
-   cable modem easy.
-
-   These utilities can be obtained from:
-
-  http://www.jacksonville.net/~fventuri/
-
-   in Franco's original source code distribution .tar.gz file.  Support for
-   the sb1000 driver can be found at:
-
-  - 
http://web.archive.org/web/%2E/http://home.adelphia.net/~siglercm/sb1000.html
-  - http://web.archive.org/web/%2E/http://linuxpower.cx/~cable/
-
-   along with these utilities.
-
-3. The standard isapnp tools.  These are necessary to configure your SB1000
-   card at boot time (or afterwards by hand) since it's a PnP card.
-
-   If you don't have these installed as a standard part of your Linux
-   distribution, you can find them at:
-
-  http://www.roestock.demon.co.uk/isapnptools/
-
-   or check your Linux distribution binary CD or their web site.  For help with
-   isapnp, pnpdump, or /etc/isapnp.conf, go to:
-
-  http://www.roestock.demon.co.uk/isapnptools/isapnpfaq.html
-
-Using the driver
-
-
-To make the SB1000 card work, follow these steps:
-
-1. Run ``make config``, or ``make menuconfig``, or ``make xconfig``, whichever
-   you prefer, in the top kernel tree directory to set up your kernel
-   configuration.  Make sure to say "Y" to "Prompt for development drivers"
-   and to say "M" to the sb1000 driver.  Also say "Y" or "M" to all the 
standard
-   networking questions to get TCP/IP and PPP networking support.
-
-2. **BEFORE** you build the kernel, edit drivers/net/sb1000.c.  Make sure
-   to redefine the value of READ_DATA_PORT to match the I/O address used
-   by isapnp to access your PnP cards.  This is the value of READPORT in
-   /etc/isapnp.conf or given by the output of pnpdump.
-
-3. Build and install the kernel and modules as usual.
-
-4. Boot your new kernel following the usual procedures.
-
-5. Set up to configure the new SB1000 PnP card by capturing the output
-   of "pnpdump" to a file and editing this file to set 

Re: [linux-next-20250307] Build Failure

[Christophe Leroy]

Le 12/03/2025 à 11:11, Venkat Rao Bagalkote a écrit :


On 12/03/25 4:20 am, Christophe Leroy wrote:



Le 09/03/2025 à 13:38, Venkat Rao Bagalkote a écrit :

Greetings!!,

I see linux-next-20250307 fails to build on IBM Power9 and Power10 
servers.



Errors:

In file included from ^[[01m^[[K^[[m^[[K:
^[[01m^[[K./usr/include/cxl/features.h:11:10:^[[m^[[K 
^[[01;31m^[[Kfatal error: ^[[m^[[Kuuid/uuid.h: No such file or directory

    11 | #include ^[[01;31m^[[K^[[m^[[K
   |  ^[[01;31m^[[K^^[[m^[[K


This is unreadable. Please avoid fancy colors that add escapes to 
logs. You can unset LANG environment var before building in order to 
get pastable stuff.


By the way I don't think it is a kernel issue because nowhere in the 
kernel you have uuid/uuid.h


But can you provide your .config (the actual one, not an old one from 
kernel 6.0.0-rc3 like last time) and tell which version of GCC you are 
using.


Attached are the two config files on both CI nodes build failures were 
reported.


On both the CI nodes gcc version is 11.5.0.

Below data are from the failure nodes.

commit-time: 2025-03-07 20:31:46 +1100
commit-id: 0a2f889128969dab41861b6e40111aa03dc57014
version: 6.14.0-rc5-next-20250307-auto



Sorry I'm still puzzled with your config files.


The one named p10_build_failure contains:

# Linux/powerpc 6.3.0-rc3 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)"


The one named p10_kdump_config_build_failure contains:

# Linux/powerpc 6.3.0 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-18)"


You are talking about CI nodes, do you have an online link to the full 
report ?


Christophe

[PATCH v2] Documentation: ocxl.rst: Update consortium site

[Fritz Koenig]

Point to post-merger site.

Signed-off-by: Fritz Koenig 
---
Changes in v2:
- Update link per feedback
- Update commit message to reflect sureness in corectness
- Link to v1: 
https://lore.kernel.org/r/20250311-dead_site-v1-1-7ab3cea37...@chromium.org
---
 Documentation/userspace-api/accelerators/ocxl.rst | 7 +--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/Documentation/userspace-api/accelerators/ocxl.rst 
b/Documentation/userspace-api/accelerators/ocxl.rst
index db7570d5e50d..4e213af70237 100644
--- a/Documentation/userspace-api/accelerators/ocxl.rst
+++ b/Documentation/userspace-api/accelerators/ocxl.rst
@@ -3,8 +3,11 @@ OpenCAPI (Open Coherent Accelerator Processor Interface)
 
 
 OpenCAPI is an interface between processors and accelerators. It aims
-at being low-latency and high-bandwidth. The specification is
-developed by the `OpenCAPI Consortium `_.
+at being low-latency and high-bandwidth.
+
+The specification was developed by the OpenCAPI Consortium, and is now
+available from the `Compute Express Link Consortium
+`_.
 
 It allows an accelerator (which could be an FPGA, ASICs, ...) to access
 the host memory coherently, using virtual addresses. An OpenCAPI

---
base-commit: 0b46b049d6eccd947c361018439fcb596e741d7a
change-id: 20250311-dead_site-e96834910663

Best regards,
-- 
Fritz Koenig 

Re: [PATCH 10/13] arch, mm: set high_memory in free_area_init()

[Mark Brown]

On Tue, Mar 11, 2025 at 10:41:28PM +0100, Geert Uytterhoeven wrote:
> On Tue, 11 Mar 2025 at 22:33, Mark Brown  wrote:

> > [0.00] efi: UEFI not found.
> > [0.00] cma: Reserved 64 MiB at 0x

> > - I'd only been sampling the logs for the physical platforms, none of
> > which had shown anything.

> Hangs that early need "earlycon", which the qemu boot above does have.

Indeed, the physical platforms either don't support earlycon or I just
don't wire it up as standard in my CI.  I see a fix should already be on
the way, but FWIW the physical platforms do seem to have bisected to the
same commit.


signature.asc
Description: PGP signature

Re: [linux-next-20250307] Build Failure

[Christophe Leroy]

Le 12/03/2025 à 11:11, Venkat Rao Bagalkote a écrit :


On 12/03/25 4:20 am, Christophe Leroy wrote:



Le 09/03/2025 à 13:38, Venkat Rao Bagalkote a écrit :

Greetings!!,

I see linux-next-20250307 fails to build on IBM Power9 and Power10 
servers.



Errors:

In file included from ^[[01m^[[K^[[m^[[K:
^[[01m^[[K./usr/include/cxl/features.h:11:10:^[[m^[[K 
^[[01;31m^[[Kfatal error: ^[[m^[[Kuuid/uuid.h: No such file or directory

    11 | #include ^[[01;31m^[[K^[[m^[[K
   |  ^[[01;31m^[[K^^[[m^[[K


This is unreadable. Please avoid fancy colors that add escapes to 
logs. You can unset LANG environment var before building in order to 
get pastable stuff.




Allthought not really readable, it seems to mention that uuid/uuid.h is 
missing.


Can you confirm that you have installed libuuid package in your system ? 
Maybe you also need some libuuid-dev packet to get headers ?


Christophe

Re: [PATCH 07/13] s390: make setup_zero_pages() use memblock

[Ard Biesheuvel]

On Tue, 11 Mar 2025 at 06:56, Mike Rapoport  wrote:
>
> On Fri, Mar 07, 2025 at 04:28:15PM +0100, Heiko Carstens wrote:
> > On Thu, Mar 06, 2025 at 08:51:17PM +0200, Mike Rapoport wrote:
> > > From: "Mike Rapoport (Microsoft)" 
> > >
> > > Allocating the zero pages from memblock is simpler because the memory is
> > > already reserved.
> > >
> > > This will also help with pulling out memblock_free_all() to the generic
> > > code and reducing code duplication in arch::mem_init().
> > >
> > > Signed-off-by: Mike Rapoport (Microsoft) 
> > > ---
> > >  arch/s390/mm/init.c | 14 +++---
> > >  1 file changed, 3 insertions(+), 11 deletions(-)
> >
> > Acked-by: Heiko Carstens 
> >
> > > -   empty_zero_page = __get_free_pages(GFP_KERNEL | __GFP_ZERO, order);
> > > +   empty_zero_page = (unsigned long)memblock_alloc(PAGE_SIZE << order, 
> > > order);
> > > if (!empty_zero_page)
> > > panic("Out of memory in setup_zero_pages");
> >
> > This could have been converted to memblock_alloc_or_panic(), but I
> > guess this can also be done at a later point in time.
>
> Duh, I should have remembered about memblock_alloc_or_panic() :)
>
> @Andrew, can you please pick this as a fixup?
>
> From 344fec8519e5152c25809c9277b54a68f9cde0e9 Mon Sep 17 00:00:00 2001
> From: "Mike Rapoport (Microsoft)" 
> Date: Tue, 11 Mar 2025 07:51:27 +0200
> Subject: [PATCH] s390: use memblock_alloc_or_panic() in setup_zero_page()
>
> Signed-off-by: Mike Rapoport (Microsoft) 
> ---
>  arch/s390/mm/init.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/arch/s390/mm/init.c b/arch/s390/mm/init.c
> index ab8ece3c41f1..c6a97329d7e7 100644
> --- a/arch/s390/mm/init.c
> +++ b/arch/s390/mm/init.c
> @@ -81,9 +81,7 @@ static void __init setup_zero_pages(void)
> while (order > 2 && (total_pages >> 10) < (1UL << order))
> order--;
>
> -   empty_zero_page = (unsigned long)memblock_alloc(PAGE_SIZE << order, 
> order);
> -   if (!empty_zero_page)
> -   panic("Out of memory in setup_zero_pages");
> +   empty_zero_page = (unsigned long)memblock_alloc_or_panic(PAGE_SIZE << 
> order, order);
>

memblock_alloc_or_panic() takes the alignment is in bytes, no? So
shouldn't the second argument be BIT(order)?

Re: [PATCH] Documentation: ocxl.rst: Update consortium site

[Fritz Koenig]

On Tue, Mar 11, 2025 at 9:20 PM Andrew Donnellan  wrote:
>
> On Tue, 2025-03-11 at 11:24 -0700, Fritz Koenig wrote:
> > Old site no longer associated with consortium.
>
> Thanks for catching this!
>
> >
> > Signed-off-by: Fritz Koenig 
> > ---
> > After mergers the OpenCAPI Consortium does not seem to exist.
> > The github page is the only seemingly relevant site, but it
> > has not been updated in 4 years.
> > ---
> >  Documentation/userspace-api/accelerators/ocxl.rst | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/userspace-api/accelerators/ocxl.rst
> > b/Documentation/userspace-api/accelerators/ocxl.rst
> > index db7570d5e50d..5fc86ead39f4 100644
> > --- a/Documentation/userspace-api/accelerators/ocxl.rst
> > +++ b/Documentation/userspace-api/accelerators/ocxl.rst
> > @@ -3,8 +3,8 @@ OpenCAPI (Open Coherent Accelerator Processor
> > Interface)
> >  
> >
> >  OpenCAPI is an interface between processors and accelerators. It
> > aims
> > -at being low-latency and high-bandwidth. The specification is
> > -developed by the `OpenCAPI Consortium `_.
> > +at being low-latency and high-bandwidth. The specification is
> > developed
> > +by the `OpenCAPI Consortium
> > `_.
>
> This link is to the OC-Accel framework documentation, which isn't the
> core set of OpenCAPI specifications. Those specs are now hosted by CXL,
> post-merger.
>
> I think I'd update this to say:
>
> The specification was developed by the OpenCAPI Consortium, and is now
> available from the `Compute Express Link Consortium
> _.
>
Thanks for the feedback, V2 posted.

-Fritz

> Thanks,
> Andrew
>
> --
> Andrew DonnellanOzLabs, ADL Canberra
> a...@linux.ibm.com   IBM Australia Limited

Re: [PATCH 07/13] s390: make setup_zero_pages() use memblock

[Mike Rapoport]

On Wed, Mar 12, 2025 at 04:56:59PM +0100, Ard Biesheuvel wrote:
> On Tue, 11 Mar 2025 at 06:56, Mike Rapoport  wrote:
> >
> > On Fri, Mar 07, 2025 at 04:28:15PM +0100, Heiko Carstens wrote:
> > > On Thu, Mar 06, 2025 at 08:51:17PM +0200, Mike Rapoport wrote:
> > > > From: "Mike Rapoport (Microsoft)" 
> > > >
> > > > Allocating the zero pages from memblock is simpler because the memory is
> > > > already reserved.
> > > >
> > > > This will also help with pulling out memblock_free_all() to the generic
> > > > code and reducing code duplication in arch::mem_init().
> > > >
> > > > Signed-off-by: Mike Rapoport (Microsoft) 
> > > > ---
> > > >  arch/s390/mm/init.c | 14 +++---
> > > >  1 file changed, 3 insertions(+), 11 deletions(-)
> > >
> > > Acked-by: Heiko Carstens 
> > >
> > > > -   empty_zero_page = __get_free_pages(GFP_KERNEL | __GFP_ZERO, order);
> > > > +   empty_zero_page = (unsigned long)memblock_alloc(PAGE_SIZE << order, 
> > > > order);
> > > > if (!empty_zero_page)
> > > > panic("Out of memory in setup_zero_pages");
> > >
> > > This could have been converted to memblock_alloc_or_panic(), but I
> > > guess this can also be done at a later point in time.
> >
> > Duh, I should have remembered about memblock_alloc_or_panic() :)
> >
> > @Andrew, can you please pick this as a fixup?
> >
> > From 344fec8519e5152c25809c9277b54a68f9cde0e9 Mon Sep 17 00:00:00 2001
> > From: "Mike Rapoport (Microsoft)" 
> > Date: Tue, 11 Mar 2025 07:51:27 +0200
> > Subject: [PATCH] s390: use memblock_alloc_or_panic() in setup_zero_page()
> >
> > Signed-off-by: Mike Rapoport (Microsoft) 
> > ---
> >  arch/s390/mm/init.c | 4 +---
> >  1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/arch/s390/mm/init.c b/arch/s390/mm/init.c
> > index ab8ece3c41f1..c6a97329d7e7 100644
> > --- a/arch/s390/mm/init.c
> > +++ b/arch/s390/mm/init.c
> > @@ -81,9 +81,7 @@ static void __init setup_zero_pages(void)
> > while (order > 2 && (total_pages >> 10) < (1UL << order))
> > order--;
> >
> > -   empty_zero_page = (unsigned long)memblock_alloc(PAGE_SIZE << order, 
> > order);
> > -   if (!empty_zero_page)
> > -   panic("Out of memory in setup_zero_pages");
> > +   empty_zero_page = (unsigned long)memblock_alloc_or_panic(PAGE_SIZE 
> > << order, order);
> >
> 
> memblock_alloc_or_panic() takes the alignment is in bytes, no? So
> shouldn't the second argument be BIT(order)?

The second argument should be PAGE_SIZE. Thanks for catching that!

-- 
Sincerely yours,
Mike.

Re: [PATCH v13 00/11] Support page table check on PowerPC

[Andrew Donnellan]

On Wed, 2025-02-12 at 03:13 +1100, Andrew Donnellan wrote:
> Support page table check on all PowerPC platforms. This works by
> serialising assignments, reassignments and clears of page table
> entries at each level in order to ensure that anonymous mappings
> have at most one writable consumer, and likewise that file-backed
> mappings are not simultaneously also anonymous mappings.
> 
> In order to support this infrastructure, a number of stubs must be
> defined for all powerpc platforms. Additionally, seperate
> set_pte_at()
> and set_pte_at_unchecked(), to allow for internal, uninstrumented
> mappings.

Talking to Maddy about this off-list - given that this series touches
on generic code and several architectures, would it be best to take it
through the mm tree rather than powerpc?

-- 
Andrew DonnellanOzLabs, ADL Canberra
a...@linux.ibm.com   IBM Australia Limited

Re: [PATCH v2] kbuild: Add missing $(objtree) prefix to powerpc crtsavres.o artifact

[Mathieu Desnoyers]

On 18-Feb-2025 03:26:39 PM, Kienan Stewart wrote:
> In the upstream commit 214c0eea43b2ea66bcd6467ea57e47ce8874191b
> ("kbuild: add $(objtree)/ prefix to some in-kernel build artifacts")
> artifacts required for building out-of-tree kernel modules had
> $(objtree) prepended to them to prepare for building in other
> directories.
> 
> When building external modules for powerpc,
> arch/powerpc/lib/crtsavres.o is required for certain
> configurations. This artifact is missing the prepended $(objtree).

FYI, the issue resolved here breaks the build of LTTng-modules against
recent kernels on powerpc. I would gladly welcome upstreaming of this
fix into the Linux kernel.

Thanks!

Mathieu

> 
> Fixes: 13b25489b6f8 ("kbuild: change working directory to external module 
> directory with M=")
> Acked-by: Masahiro Yamada 
> Reviewed-by: Nicolas Schier 
> Tested-by: Nicolas Schier 
> Signed-off-by: Kienan Stewart 
> ---
> Changes in v2:
> - Added Review-by/Tested-by/Fixes/Acked-By
> - Removed mention of possible work-around for external modules (while
> the build will pass, `make modules_install` will fail)
> - Link to v1: 
> https://lore.kernel.org/r/20250127-buildfix-extmod-powerpc-v1-1-450012b16...@efficios.com
> ---
>  arch/powerpc/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
> index 
> f3804103c56ccfdb16289468397ccaea71bf721e..9933b98df69d7f7b9aaf33d36155cc61ab4460c7
>  100644
> --- a/arch/powerpc/Makefile
> +++ b/arch/powerpc/Makefile
> @@ -58,7 +58,7 @@ ifeq ($(CONFIG_PPC64)$(CONFIG_LD_IS_BFD),yy)
>  # There is a corresponding test in arch/powerpc/lib/Makefile
>  KBUILD_LDFLAGS_MODULE += --save-restore-funcs
>  else
> -KBUILD_LDFLAGS_MODULE += arch/powerpc/lib/crtsavres.o
> +KBUILD_LDFLAGS_MODULE += $(objtree)/arch/powerpc/lib/crtsavres.o
>  endif
>  
>  ifdef CONFIG_CPU_LITTLE_ENDIAN
> 
> ---
> base-commit: ffd294d346d185b70e28b1a28abe367bbfe53c04
> change-id: 20250127-buildfix-extmod-powerpc-a744e1331f83
> 
> Best regards,
> -- 
> Kienan Stewart 
> 

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

[PATCH 1/4] spufs: fix a leak on spufs_new_file() failure

[Al Viro]

It's called from spufs_fill_dir(), and caller of that will do
spufs_rmdir() in case of failure.  That does remove everything
we'd managed to create, but... the problem dentry is still
negative.  IOW, it needs to be explicitly dropped.

Fixes: 3f51dd91c807 "[PATCH] spufs: fix spufs_fill_dir error path"
Signed-off-by: Al Viro 
---
 arch/powerpc/platforms/cell/spufs/inode.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/arch/powerpc/platforms/cell/spufs/inode.c 
b/arch/powerpc/platforms/cell/spufs/inode.c
index 70236d1df3d3..793c005607cf 100644
--- a/arch/powerpc/platforms/cell/spufs/inode.c
+++ b/arch/powerpc/platforms/cell/spufs/inode.c
@@ -192,8 +192,10 @@ static int spufs_fill_dir(struct dentry *dir,
return -ENOMEM;
ret = spufs_new_file(dir->d_sb, dentry, files->ops,
files->mode & mode, files->size, ctx);
-   if (ret)
+   if (ret) {
+   dput(dentry);
return ret;
+   }
files++;
}
return 0;
-- 
2.39.5

[PATCH 3/4] spufs: fix a leak in spufs_create_context()

[Al Viro]

Leak fixes back in 2008 missed one case - if we are trying to set affinity
and spufs_mkdir() fails, we need to drop the reference to neighbor.

Fixes: 58119068cb27 "[POWERPC] spufs: Fix memory leak on SPU affinity"
Signed-off-by: Al Viro 
---
 arch/powerpc/platforms/cell/spufs/inode.c | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/arch/powerpc/platforms/cell/spufs/inode.c 
b/arch/powerpc/platforms/cell/spufs/inode.c
index c566e7997f2c..9f9e4b871627 100644
--- a/arch/powerpc/platforms/cell/spufs/inode.c
+++ b/arch/powerpc/platforms/cell/spufs/inode.c
@@ -460,8 +460,11 @@ spufs_create_context(struct inode *inode, struct dentry 
*dentry,
}
 
ret = spufs_mkdir(inode, dentry, flags, mode & 0777);
-   if (ret)
+   if (ret) {
+   if (neighbor)
+   put_spu_context(neighbor);
goto out_aff_unlock;
+   }
 
if (affinity) {
spufs_set_affinity(flags, SPUFS_I(d_inode(dentry))->i_ctx,
-- 
2.39.5

[PATCHES] several fixes from tree-in-dcache stuff

[Al Viro]

Several fixes for fairly old crap - qibfs leak, a couple
of spufs ones and a spufs double-dput() memory corruptor.

This stuff sits in viro/vfs.git#fixes; individual patches
in followups.  Review would be very welcome.

Re: [PATCH v2] Documentation: ocxl.rst: Update consortium site

[Jonathan Corbet]

Fritz Koenig  writes:

> Point to post-merger site.
>
> Signed-off-by: Fritz Koenig 
> ---
> Changes in v2:
> - Update link per feedback
> - Update commit message to reflect sureness in corectness
> - Link to v1: 
> https://lore.kernel.org/r/20250311-dead_site-v1-1-7ab3cea37...@chromium.org
> ---
>  Documentation/userspace-api/accelerators/ocxl.rst | 7 +--
>  1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/userspace-api/accelerators/ocxl.rst 
> b/Documentation/userspace-api/accelerators/ocxl.rst
> index db7570d5e50d..4e213af70237 100644
> --- a/Documentation/userspace-api/accelerators/ocxl.rst
> +++ b/Documentation/userspace-api/accelerators/ocxl.rst
> @@ -3,8 +3,11 @@ OpenCAPI (Open Coherent Accelerator Processor Interface)
>  
>  
>  OpenCAPI is an interface between processors and accelerators. It aims
> -at being low-latency and high-bandwidth. The specification is
> -developed by the `OpenCAPI Consortium `_.
> +at being low-latency and high-bandwidth.
> +
> +The specification was developed by the OpenCAPI Consortium, and is now
> +available from the `Compute Express Link Consortium
> +`_.
>  

Applied, thanks.

jon