All of lore.kernel.org
 help / color / mirror / Atom feed
From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Christian Brauner <brauner@kernel.org>, Cyril Hrubis <chrubis@suse.cz>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v4 3/3] syscalls/openat: Add new regression test when using open(O_TMPFILE) under umask
Date: Mon, 26 Sep 2022 01:55:27 +0000	[thread overview]
Message-ID: <1a7955bb-5c22-4746-eaf5-597c00c4064c@fujitsu.com> (raw)
In-Reply-To: <20220923102753.4vu6id33obfi34qa@wittgenstein>

Hi Christian

> On Thu, Sep 22, 2022 at 11:27:43AM +0200, Cyril Hrubis wrote:
>> Hi!
>>>> And this one is probably missing some kernel commit tags too, since the only that that is attached is supposedly in 5.19 but the test still fails.
>>>
>>>> I supposed that we should add the 426b4ca2d6a5 to the test tags here as well, right?
>>>
>>> Yes, BTW,  I usually use git tag --contains command, so I know this kernel fix is belong to 6.0.
>>>
>>> git tag --contains ac6800e27
>>> v6.0-rc1
>>> v6.0-rc2
>>
>> Now I'm confused, if I do git describe ac6800e27 it says that it's a
>> second commit on the top of 5.19-rc7. So shouldn't the the git tag
>> --contains report 5.19-rc8 and newer? What do I miss?
> 
> So, ac6800e279a2 ("fs: Add missing umask strip in vfs_tmpfile") has been
> backported to kernels since before the dawn of time. But the the all the
> pieces that move setgid handling out of individual filesystems and into
> the vfs proper are only >= v6.0-rc1.

I search the commit mesage in the following url,but not find c6800e279a2 
commit

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?h=v5.19

@Cyril
I guess git describe ac6800e2 will serach the commit id because it is 
merge request"Merge tag 'fs.setgid.v6.0' of 
git://git.kernel.org/pub/scm/linux/kerne/git/brauner/linux"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=426b4ca2d6a5

then it will serach brauner linux fs.setgid. branch
see the following url
https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git/log/?h=fs.setgid

so git describe ac6800e27 it says that it's a second commit on the top 
of 5.19-rc7.


Best Regards
Yang Xu

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-09-26  1:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  8:12 [LTP] [PATCH v4 1/3] syscalls/creat09: Add umask test condition Yang Xu
2022-09-14  7:49 ` xuyang2018.jy
2022-09-14  8:12 ` [LTP] [PATCH v4 2/3] tst_safe_file_at: Add SAFE_FSTATAT macro Yang Xu
2022-09-14 11:30   ` Cyril Hrubis
2022-09-14  8:12 ` [LTP] [PATCH v4 3/3] syscalls/openat: Add new regression test when using open(O_TMPFILE) under umask Yang Xu
2022-09-22  8:52   ` Cyril Hrubis
2022-09-22  9:06     ` xuyang2018.jy
2022-09-22  9:27       ` Cyril Hrubis
2022-09-22 10:02         ` xuyang2018.jy
2022-09-23 10:27         ` Christian Brauner
2022-09-26  1:55           ` xuyang2018.jy [this message]
2022-10-10  6:32             ` xuyang2018.jy
2022-09-14 11:28 ` [LTP] [PATCH v4 1/3] syscalls/creat09: Add umask test condition Cyril Hrubis
2022-09-15  0:37   ` xuyang2018.jy
2022-09-20  1:08     ` xuyang2018.jy
2022-09-21 13:55       ` Cyril Hrubis
2022-09-21 15:40         ` Christian Brauner
2022-09-22  8:00           ` Cyril Hrubis

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=1a7955bb-5c22-4746-eaf5-597c00c4064c@fujitsu.com \
    --to=xuyang2018.jy@fujitsu.com \
    --cc=brauner@kernel.org \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.