mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandra Winter <wintera@linux.ibm.com>
To: netdev-bot+sashiko@kernel.org, hppiscas@163.com
Cc: twinkler@linux.ibm.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, hca@linux.ibm.com,
	gor@linux.ibm.com, agordeev@linux.ibm.com,
	borntraeger@linux.ibm.com
Subject: Re: [PATCH net v3] net/iucv: require IUCV for AF_IUCV sockets
Date: Fri, 25 Sep 2026 17:16:50 +0200	[thread overview]
Message-ID: <717d9c0e-83e9-4ad7-82b6-7970a0ba6729@linux.ibm.com> (raw)
In-Reply-To: <d0c5ed89-f782-4acf-8c4c-4626f4be650a@linux.ibm.com>



On 24.09.26 20:52, Alexandra Winter wrote:
> Actually even with your v2 IUCV=M, AF_IUCV=M builds fine in an LPAR,
> but modprobe returns with
> modprobe: ERROR: could not insert 'af_iucv': Protocol not supported	(not expected)
> modprobe: ERROR: could not insert 'iucv': Protocol not supported   	(expected)
> 
> Is this a result of
>> 	if (machine_is_vm() && ...
>> 		err = -EPROTONOSUPPORT;
> I don't fully understand it yet.
> 
> But that combination can be defined, even with your v3, so we have another open issue here.
> 
> I definitively need to test all possible combinations! (Should have done that earlier, I admit)

That is the same root cause as IUCV=M, AF_IUCV=Y linker error with v2:
the reference to `iucv_if'.
So this probably would work with v3.

Nevertheless, I'm working on a clean solution on top of your v2. Let me see if I can come up with that.

Kind regards
Alexandra

      reply	other threads:[~2026-09-25 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20  3:45 Pengpeng Hou
2026-09-21  3:48 ` netdev-bot+sashiko
2026-09-24 18:52   ` Alexandra Winter
2026-09-25 15:16     ` Alexandra Winter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=717d9c0e-83e9-4ad7-82b6-7970a0ba6729@linux.ibm.com \
    --to=wintera@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=horms@kernel.org \
    --cc=hppiscas@163.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=twinkler@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®