From: Jeff Layton <jlayton@kernel.org>
To: Zorro Lang <zlang@redhat.com>, Alexander Aring <aahringo@redhat.com>
Cc: fstests@vger.kernel.org, gfs2@lists.linux.dev
Subject: Re: [PATCHv2] generic: add fcntl corner cases tests
Date: Fri, 02 Feb 2024 07:36:11 -0500 [thread overview]
Message-ID: <43df69aa93418c35dad23d3c115241ee9170a5fc.camel@kernel.org> (raw)
In-Reply-To: <20240202122744.ejfpfrfbt6gnrese@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Fri, 2024-02-02 at 20:27 +0800, Zorro Lang wrote:
> On Fri, Feb 02, 2024 at 07:19:53AM -0500, Alexander Aring wrote:
> > Hi Zorro,
> >
> > On Fri, Feb 2, 2024 at 7:04 AM Zorro Lang <zlang@redhat.com> wrote:
> > >
> > > On Thu, Feb 01, 2024 at 12:10:44PM -0500, Jeff Layton wrote:
> > > > On Mon, 2023-09-25 at 16:18 -0400, Alexander Aring wrote:
> > > > > This patch adds fcntl corner cases that was being used to confirm issues
> > > > > on a GFS2 filesystem. The GFS2 filesystem has it's own ->lock()
> > > > > implementation and in those corner cases issues was being found and
> > > > > fixed.
> > > > >
> > > > > Signed-off-by: Alexander Aring <aahringo@redhat.com>
> > > > > ---
> > > > > changes since v2:
> > > > > - move fcntl tests into one fcntl c file
> > > > > - remove ofd and same owner tests, should be reflected by only one test
> > > > > - simplify commit message (remove testname out of it)
> > > > > - add error messages in fcntl.c to give more information if an error
> > > > > occur
> > > > >
> > > > > src/Makefile | 3 +-
> > > > > src/fcntl.c | 322 ++++++++++++++++++++++++++++++++++++++++++
> > > > > tests/generic/732 | 32 +++++
> > > > > tests/generic/732.out | 2 +
> > > > > 4 files changed, 358 insertions(+), 1 deletion(-)
> > > > > create mode 100644 src/fcntl.c
> > > > > create mode 100755 tests/generic/732
> > > > > create mode 100644 tests/generic/732.out
> > > > >
> > > > > diff --git a/src/Makefile b/src/Makefile
> > > > > index 2815f919..67f936d3 100644
> > > > > --- a/src/Makefile
> > > > > +++ b/src/Makefile
> > > > > @@ -19,7 +19,8 @@ TARGETS = dirstress fill fill2 getpagesize holes lstat64 \
> > > > > t_ofd_locks t_mmap_collision mmap-write-concurrent \
> > > > > t_get_file_time t_create_short_dirs t_create_long_dirs t_enospc \
> > > > > t_mmap_writev_overlap checkpoint_journal mmap-rw-fault allocstale \
> > > > > - t_mmap_cow_memory_failure fake-dump-rootino dio-buf-fault rewinddir-test
> > > > > + t_mmap_cow_memory_failure fake-dump-rootino dio-buf-fault rewinddir-test \
> > > > > + fcntl
> > > >
> > > > I think this function needs a less-generic name than "fcntl". Other the
> > > > lock tests themselves look like a nice addition though.
> > >
> > > Yeah, the "fcntl" name is too "big", please rename it to show what it trys
> > > to test. Hi Alexander, you can tell me the new name you'd like to change,
> > > if you don't want to send a V2. That might help to catch the fstests release
> > > of this weekend :)
> > >
> >
> > I was thinking about "fcntl_corner_tests", if this is okay.
>
> Good to me, I'm rename to that if no more objection :)
>
>
Can we make it "fcntl_lock_corner_tests"?
These tests are all about file locking, but fcntl() is a generic system
call that does a lot of different things besides that.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-02-02 12:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 20:18 [PATCHv2] generic: add fcntl corner cases tests Alexander Aring
2023-11-02 14:37 ` Alexander Aring
2024-02-01 15:03 ` Alexander Aring
2024-02-01 17:10 ` Jeff Layton
2024-02-02 12:04 ` Zorro Lang
2024-02-02 12:19 ` Alexander Aring
2024-02-02 12:27 ` Zorro Lang
2024-02-02 12:36 ` Jeff Layton [this message]
2024-02-02 12:46 ` Zorro Lang
2024-02-09 5:26 ` Zorro Lang
2024-02-09 5:35 ` Steve French
2024-02-09 11:43 ` Zorro Lang
2024-03-01 10:38 ` Zorro Lang
2024-03-01 14:08 ` Alexander Aring
2024-03-01 16:25 ` Paulo Alcantara
2024-03-01 17:23 ` Alexander Aring
2024-03-01 23:59 ` Paulo Alcantara
2024-03-03 5:08 ` Zorro Lang
2024-03-07 15:58 ` Anand Jain
2024-03-30 7:25 ` Zorro Lang
2024-04-02 14:56 ` Alexander Aring
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=43df69aa93418c35dad23d3c115241ee9170a5fc.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=aahringo@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=gfs2@lists.linux.dev \
--cc=zlang@redhat.com \
/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