From: Leon Romanovsky <leon@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: Please return trailer-order option
Date: Fri, 2 Sep 2022 13:25:36 +0300 [thread overview]
Message-ID: <YxHaILXFF5Fzt4ig@unreal> (raw)
In-Reply-To: <20220901214047.oyrmg4hyyihkdbbg@meerkat.local>
On Thu, Sep 01, 2022 at 05:40:47PM -0400, Konstantin Ryabitsev wrote:
> On Thu, Jul 28, 2022 at 09:42:10PM +0300, Leon Romanovsky wrote:
> > >> Do you think that it is acceptable to return that option?
> > >
> > > Yes, it will probably come back as "trailer-priority" and preserve the
> > > chain-of-custody ordering as discussed on the list. It should make it back in
> > > by 0.10 release.
> >
> > Sounds awesome.
>
> FYI, this option is back as of today. It's still called "trailer-order", so
> you shouldn't need to change anything. There are some important changes in how
> it works:
>
> 1. we only reorder trailers that are in your own chain-of-custody section
> (below the last Signed-off-by that isn't yours)
> 2. we always move your own Signed-off-by to the bottom of your own
> chain-of-custody section
>
> Please let me know if this new behaviour is working as you would expect it.
Thank you for doing it.
I tried latest b4 with the following config:
[b4]
trailer-order = "Cc,Fixes*,Link*,Suggested*,Reviewed*,Tested*,*"
➜ kernel git:(tmp) ~/src/b4/b4.sh shazam -l -s https://lore.kernel.org/all/20220901202645.1463552-1-irogers@google.com
Grabbing thread from lore.kernel.org/all/20220901202645.1463552-1-irogers%40google.com/t.mbox.gz
Checking for newer revisions on https://lore.kernel.org/all/
Analyzing 2 messages in the thread
Checking attestation on all messages, may take a moment...
---
[PATCH v1] selftests/xsk: Avoid use-after-free on ctx
+ Acked-by: Magnus Karlsson <magnus.karlsson@intel.com>
+ Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
---
NOTE: install dkimpy for DKIM signature verification
---
Total patches: 1
---
Applying: selftests/xsk: Avoid use-after-free on ctx
The end result as an outcome of 1 is:
Fixes: 39e940d4abfa ("selftests/xsk: Destroy BPF resources only when ctx refcount drops to 0")
Signed-off-by: Ian Rogers <irogers@google.com>
Link: https://lore.kernel.org/r/20220901202645.1463552-1-irogers@google.com
Acked-by: Magnus Karlsson <magnus.karlsson@intel.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
While I would like to see Link being below Fixes line:
Fixes: 39e940d4abfa ("selftests/xsk: Destroy BPF resources only when ctx refcount drops to 0")
Link: https://lore.kernel.org/r/20220901202645.1463552-1-irogers@google.com
Signed-off-by: Ian Rogers <irogers@google.com>
Acked-by: Magnus Karlsson <magnus.karlsson@intel.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Thanks
>
> -K
next prev parent reply other threads:[~2022-09-02 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YtZZE/6BOR5m86Kq@unreal>
[not found] ` <7bb8b97f-dc03-41af-866e-767e4c15df62@www.fastmail.com>
[not found] ` <20220728171351.4v65ytd2s5wp2lb7@meerkat.local>
[not found] ` <20c1ca09-58e8-4ed4-a586-871a2daad70f@www.fastmail.com>
2022-09-01 21:40 ` Please return trailer-order option Konstantin Ryabitsev
2022-09-02 10:25 ` Leon Romanovsky [this message]
2022-09-02 14:40 ` Konstantin Ryabitsev
2022-09-03 6:31 ` Leon Romanovsky
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=YxHaILXFF5Fzt4ig@unreal \
--to=leon@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
/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