All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Avinesh Kumar <akumar@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] flock: Add test for verifying EINTR errno
Date: Mon, 3 Feb 2025 11:12:54 +0100	[thread overview]
Message-ID: <20250203101254.GA1237315@pevik> (raw)
In-Reply-To: <6151942.lOV4Wx5bFT@thinkpad>

Hi Avinesh,

...
> > > Hi Petr,

> > > I am sorry, I completely missed this.
> > > I sent the patch for EWOULDBLOCK case now -
> > > https://lore.kernel.org/ltp/20250114155013.7644-1-akumar@suse.de/T/#u

> > Thanks for info. I'm closing this as rejected. Please let me know if I did not
> > understand you and this is a valid patch.

> Hi Petr, the above v3 patch (for new test of flock/EINTR errno) is still valid.
> I took out the EWOULDBLOCK test from the original patch (by Yang Xu) and
> added that to flock02, you already merged that one.
> So you can review flock07.c patch just for the EINTR case.

Thanks for info, I reopened it in patchwork and I'll have look later.

I see, the crash is workarounded by forking child and verifying, that's why it's
not in flock02.c (which has other errnos, which don't need a workaround with
forking).

Kind regards,
Petr

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

  reply	other threads:[~2025-02-03 10:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16  8:02 [LTP] [PATCH] flock: Add negative tests for flock Yang Xu via ltp
2024-05-30 14:13 ` Avinesh Kumar
2024-10-21 14:28   ` Petr Vorel
2024-05-30 14:40 ` [LTP] [PATCH v2] flock: Add test for verifying EINTR errno Avinesh Kumar
2024-05-30 14:48   ` [LTP] [PATCH v3] " Avinesh Kumar
2024-10-21 19:55     ` Petr Vorel
2025-01-14 15:54       ` Avinesh Kumar
2025-01-31 11:01         ` Petr Vorel
2025-02-03  9:41           ` Avinesh Kumar
2025-02-03 10:12             ` Petr Vorel [this message]
2025-02-03 14:22     ` Petr Vorel
2025-02-03 14:55       ` Avinesh Kumar
2025-02-03 15:33         ` Petr Vorel

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=20250203101254.GA1237315@pevik \
    --to=pvorel@suse.cz \
    --cc=akumar@suse.de \
    --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.