From: Jiri Pirko <jiri@resnulli.us>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: netdev@vger.kernel.org, jbohac@suse.cz,
benoit.boissinot@ens-lyon.org, davem@davemloft.net,
hideaki.yoshifuji@miraclelinux.com, dsahern@kernel.org,
pabeni@redhat.com, kuba@kernel.org
Subject: Re: [PATCH net-next v2 1/4] net: ipv6/addrconf: clamp preferred_lft to the maximum allowed
Date: Thu, 26 Oct 2023 07:11:44 +0200 [thread overview]
Message-ID: <ZTn1EKPzt4NaXN6y@nanopsycho> (raw)
In-Reply-To: <CAMMLpeRcM2iv2oUDk4=zPehS_+qPh3eD1aa1adST300N_cHS5A@mail.gmail.com>
Wed, Oct 25, 2023 at 06:28:00PM CEST, alexhenrie24@gmail.com wrote:
>On Wed, Oct 25, 2023 at 6:23 AM Jiri Pirko <jiri@resnulli.us> wrote:
>>
>> Tue, Oct 24, 2023 at 11:23:07PM CEST, alexhenrie24@gmail.com wrote:
>> >Without this patch, there is nothing to stop the preferred lifetime of a
>> >temporary address from being greater than its valid lifetime. If that
>> >was the case, the valid lifetime was effectively ignored.
>> >
>>
>> Sounds like a bugfix, correct? In that case, could you please
>> provide a proper Fixes tag and target -net tree?
>
>Paolo requested no Fixes tag, and Jakub seemed to agree:
>
>https://lore.kernel.org/all/60d9d5f57fdb55a27748996d807712c680c4e7f9.camel@redhat.com/
Okay, makes sense.
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2023-10-26 5:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 21:23 [PATCH net-next v2 0/4] net: ipv6/addrconf: ensure that temporary addresses' preferred lifetimes are in the valid range Alex Henrie
2023-10-24 21:23 ` [PATCH net-next v2 1/4] net: ipv6/addrconf: clamp preferred_lft to the maximum allowed Alex Henrie
2023-10-25 12:23 ` Jiri Pirko
2023-10-25 16:28 ` Alex Henrie
2023-10-26 5:11 ` Jiri Pirko [this message]
2023-10-26 0:41 ` David Ahern
2023-10-24 21:23 ` [PATCH net-next v2 2/4] net: ipv6/addrconf: clamp preferred_lft to the minimum required Alex Henrie
2023-10-25 12:25 ` Jiri Pirko
2023-10-26 0:43 ` David Ahern
2023-10-24 21:23 ` [PATCH net-next v2 3/4] Documentation: networking: explain what happens if temp_valid_lft is too small Alex Henrie
2023-10-26 0:43 ` David Ahern
2023-10-24 21:23 ` [PATCH net-next v2 4/4] Documentation: networking: explain what happens if temp_prefered_lft is too small or too large Alex Henrie
2023-10-26 0:44 ` David Ahern
2023-10-26 1:30 ` [PATCH net-next v2 0/4] net: ipv6/addrconf: ensure that temporary addresses' preferred lifetimes are in the valid range patchwork-bot+netdevbpf
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=ZTn1EKPzt4NaXN6y@nanopsycho \
--to=jiri@resnulli.us \
--cc=alexhenrie24@gmail.com \
--cc=benoit.boissinot@ens-lyon.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=hideaki.yoshifuji@miraclelinux.com \
--cc=jbohac@suse.cz \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).