All of lore.kernel.org
 help / color / mirror / Atom feed
From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Martin Doucha <mdoucha@suse.cz>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] syscalls/setsockopt09: Add another linux git
Date: Thu, 10 Mar 2022 06:07:42 +0000	[thread overview]
Message-ID: <622995E1.7020208@fujitsu.com> (raw)
In-Reply-To: <c25c192d-9848-d7cd-d4a1-4f1b924f67e8@suse.cz>

Hi Martin
> On 09. 03. 22 3:03, xuyang2018.jy@fujitsu.com wrote:
>> Hi Martin
>>> The timeout is controlled by req.tp_retire_blk_tov and the value is in
>>> milliseconds. So usleep(req.tp_retire_blk_tov * 3000) should be enough.
>> I tested this on my vm, it still can't ensure hit the old crash before
>> print PASS log.
>
> That is probably expected. You'll need make a taint check after the
> usleep() to detect failure. See setsockopt06 which tests for similar
> use-after-free in socket timer.

I add a sleep ie setsockopt06, but it doesn't detect the kernel tainted 
state in time and doesn't report "Kernel is vulnerable".

Best Regards
Yang Xu
>

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

      reply	other threads:[~2022-03-10  6:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03  8:54 [LTP] [PATCH] syscalls/setsockopt09: Add another linux git Yang Xu
2022-03-03  9:11 ` xuyang2018.jy
2022-03-03 14:04 ` Petr Vorel
2022-03-04  3:24   ` xuyang2018.jy
2022-03-04  8:01     ` Petr Vorel
2022-03-08 10:04       ` xuyang2018.jy
2022-03-08 10:44     ` Martin Doucha
2022-03-09  2:03       ` xuyang2018.jy
2022-03-09 10:51         ` Martin Doucha
2022-03-10  6:07           ` xuyang2018.jy [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=622995E1.7020208@fujitsu.com \
    --to=xuyang2018.jy@fujitsu.com \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@suse.cz \
    /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.