public inbox for xenomai@lists.linux.dev
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Tobias Schaffner <tobias.schaffner@siemens.com>
Cc: xenomai@lists.linux.dev
Subject: Re: [PATCH dovetail] net: skbuff: add missing OOB stubs for !CONFIG_NET_OOB
Date: Fri, 27 Mar 2026 09:33:13 +0100	[thread overview]
Message-ID: <87ecl5r7sm.fsf@xenomai.org> (raw)
In-Reply-To: <5d2efb94-81c2-4243-9801-3ccb7a4a29a7@siemens.com> (Tobias Schaffner's message of "Thu, 26 Mar 2026 10:03:35 +0100")

Tobias Schaffner <tobias.schaffner@siemens.com> writes:

> Hi!
>
> On 3/25/26 15:51, Philippe Gerum wrote:
>> Tobias Schaffner <tobias.schaffner@siemens.com> writes:
>> 
>>> skbuff.c calls skb_mark_oob() and variants behind runtime running_oob()
>>> checks but these are only implemented in the CONFIG_NET_OOB section.
>>>
>>> Add the missing stubs to the !CONFIG_NET_OOB section.
>>>
>>> Signed-off-by: Tobias Schaffner <tobias.schaffner@siemens.com>
>>> ---
>>>   include/linux/skbuff.h | 16 ++++++++++++++++
>>>   1 file changed, 16 insertions(+)
>>>
>>> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
>>> index 73dd4a58d181..1278d0a58677 100644
>>> --- a/include/linux/skbuff.h
>>> +++ b/include/linux/skbuff.h
>>> @@ -5630,6 +5630,22 @@ static inline struct sk_buff *get_oob_skb(void)
>>>   	return __get_oob_skb();
>>>   }
>>>   +static inline void skb_mark_oob(struct sk_buff *skb)
>>> +{
>>> +}
>>> +
>>> +static inline void skb_mark_oob_released(struct sk_buff *skb)
>>> +{
>>> +}
>>> +
>>> +static inline void skb_mark_oob_timestamped(struct sk_buff *skb)
>>> +{
>>> +}
>>> +
>>> +static inline void skb_mark_oob_managed(struct sk_buff *skb)
>>> +{
>>> +}
>>> +
>>>   #endif	/* !CONFIG_NET_OOB */
>>>     #endif	/* __KERNEL__ */
>> All current users of skb_oob_mark_*() calls are currently guarded by
>> CONFIG_NET_OOB sections, or enable CONFIG_NET_OOB, like the evl
>> core. Did you observe a build failure with CONFIG_NET_OOB=n, or is it
>> preventive fixup?
>
> I am building without CONFIG_NET_OOB at the moment and the build fails
> because of the unguarded skb_mark_oob calls in net/core/skbuff.c.
>

Correct, I overlooked the call to skb_mark_oob() introduced in
v7.0. Merged, thanks.

-- 
Philippe.

      reply	other threads:[~2026-03-27  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 21:19 [PATCH dovetail] net: skbuff: add missing OOB stubs for !CONFIG_NET_OOB Tobias Schaffner
2026-03-25 14:51 ` Philippe Gerum
2026-03-26  9:03   ` Tobias Schaffner
2026-03-27  8:33     ` Philippe Gerum [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=87ecl5r7sm.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=tobias.schaffner@siemens.com \
    --cc=xenomai@lists.linux.dev \
    /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