From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] 答复: [PATCH v3 0/3] Fix bug caused by default umask
Date: Mon, 30 Mar 2020 16:59:01 +0800 [thread overview]
Message-ID: <5E81B4D5.9070706@cn.fujitsu.com> (raw)
In-Reply-To: <C3CD0DF8AD11A84CB25A1426DE537C61E5928002@dggeml524-mbx.china.huawei.com>
On 2020/3/30 16:22, Zouwei (Samuel) wrote:
> Hi Yang,
>
> I downloaded the development version of ltp two weeks ago, ran the cases in the runtest directory, and analyzed all the failed cases.
> I found that these 3 cases have the umask issue.
>
> Due to the limited time invested by individuals, it is possible that other cases with the same issue will not be discovered.
> I will analyze the other failed cases that have not been concluded further in the next few weeks.
Hi Zou,
Thanks, I have pushed the patch set.
Perhaps, you can fix all same umask issues by a single patch in future.
Thanks,
Xiao Yang
>
> Thanks for your suggestions and reviews.
>
> Best Regards
> Zou Wei
> -----????-----
> ???: Xiao Yang [mailto:yangx.jy@cn.fujitsu.com]
> ????: 2020?3?30? 15:34
> ???: Zouwei (Samuel)<zou_wei@huawei.com>
> ??: ltp@lists.linux.it
> ??: Re: [LTP] [PATCH v3 0/3] Fix bug caused by default umask
>
> On 2020/3/30 15:27, Zou Wei wrote:
>> v3:
>> The case is only successful when system default umask is 0022.
>> When default umask is 0077 or other values, should clear umask by umask(0) in setup().
> Hi Zou,
>
> Thanks for your patch set.
> Did you find any other cases related with the same issue?
>
> Thanks,
> Xiao Yang
>>
>> Zou Wei (3):
>> security/dirtyc0w: Fix bug caused by default umask
>> syscalls/fstat: Fix bug caused by default umask
>> syscalls/statx01: Fix bug caused by default umask
>>
>> testcases/kernel/security/dirtyc0w/dirtyc0w.c | 2 ++
>> testcases/kernel/syscalls/fstat/fstat02.c | 2 ++
>> testcases/kernel/syscalls/statx/statx01.c | 2 ++
>> 3 files changed, 6 insertions(+)
>>
>> --
>> 2.6.2
>>
>>
>
>
>
>
>
prev parent reply other threads:[~2020-03-30 8:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 7:27 [LTP] [PATCH v3 0/3] Fix bug caused by default umask Zou Wei
2020-03-30 7:27 ` [LTP] [PATCH v3 1/3] security/dirtyc0w: " Zou Wei
2020-03-30 9:18 ` Cyril Hrubis
2020-03-30 9:20 ` Cyril Hrubis
2020-03-30 12:33 ` Xiao Yang
2020-03-31 2:30 ` [LTP] 答复: " Zouwei
2020-03-30 12:48 ` [LTP] " Xiao Yang
2020-03-30 12:52 ` Cyril Hrubis
2020-03-30 7:27 ` [LTP] [PATCH v3 2/3] syscalls/fstat: " Zou Wei
2020-03-30 7:27 ` [LTP] [PATCH v3 3/3] syscalls/statx01: " Zou Wei
2020-03-30 7:34 ` [LTP] [PATCH v3 0/3] " Xiao Yang
2020-03-30 8:22 ` [LTP] 答复: " Zouwei
2020-03-30 8:59 ` Xiao Yang [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=5E81B4D5.9070706@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox