From: Cyril Hrubis <chrubis@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: mszeredi@redhat.com, brauner@kernel.org, Jan Kara <jack@suse.cz>,
Matthew Wilcox <willy@infradead.org>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 3/4] syscalls: accept: Add tst_fd test
Date: Tue, 24 Oct 2023 11:34:33 +0200 [thread overview]
Message-ID: <ZTePqRn48CjcZT1T@yuki> (raw)
In-Reply-To: <87fs20v07j.fsf@suse.de>
Hi!
> > int invalid_socketfd = 400; /* anything that is not an open file */
> > -int devnull_fd;
> > int socket_fd;
> > int udp_fd;
> >
> > @@ -45,10 +44,6 @@ static struct test_case {
> > (struct sockaddr *)&fsin1, sizeof(fsin1), EBADF,
> > "bad file descriptor"
> > },
> > - {
> > - PF_INET, SOCK_STREAM, 0, &devnull_fd, (struct sockaddr *)&fsin1,
> > - sizeof(fsin1), ENOTSOCK, "fd is not socket"
> > - },
> > {
> > PF_INET, SOCK_STREAM, 0, &socket_fd, (struct sockaddr *)3,
> > sizeof(fsin1), EINVAL, "invalid socket buffer"
> > @@ -73,8 +68,6 @@ static void test_setup(void)
> > sin0.sin_port = 0;
> > sin0.sin_addr.s_addr = INADDR_ANY;
> >
> > - devnull_fd = SAFE_OPEN("/dev/null", O_WRONLY);
> > -
> > socket_fd = SAFE_SOCKET(PF_INET, SOCK_STREAM, 0);
> > SAFE_BIND(socket_fd, (struct sockaddr *)&sin0, sizeof(sin0));
> >
> > @@ -88,7 +81,6 @@ static void test_setup(void)
> >
> > static void test_cleanup(void)
> > {
> > - SAFE_CLOSE(devnull_fd);
> > SAFE_CLOSE(socket_fd);
> > SAFE_CLOSE(udp_fd);
> > }
>
> Is this supposed to be part of the patchset?
>
> I don't mind, but if we are strict, it should be in another commit.
That removes ENOTSOCK test that is now handled in accept03, I suppose I
should have explained that better in the comit message.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: mszeredi@redhat.com, brauner@kernel.org, Jan Kara <jack@suse.cz>,
Matthew Wilcox <willy@infradead.org>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 3/4] syscalls: accept: Add tst_fd test
Date: Tue, 24 Oct 2023 11:34:33 +0200 [thread overview]
Message-ID: <ZTePqRn48CjcZT1T@yuki> (raw)
In-Reply-To: <87fs20v07j.fsf@suse.de>
Hi!
> > int invalid_socketfd = 400; /* anything that is not an open file */
> > -int devnull_fd;
> > int socket_fd;
> > int udp_fd;
> >
> > @@ -45,10 +44,6 @@ static struct test_case {
> > (struct sockaddr *)&fsin1, sizeof(fsin1), EBADF,
> > "bad file descriptor"
> > },
> > - {
> > - PF_INET, SOCK_STREAM, 0, &devnull_fd, (struct sockaddr *)&fsin1,
> > - sizeof(fsin1), ENOTSOCK, "fd is not socket"
> > - },
> > {
> > PF_INET, SOCK_STREAM, 0, &socket_fd, (struct sockaddr *)3,
> > sizeof(fsin1), EINVAL, "invalid socket buffer"
> > @@ -73,8 +68,6 @@ static void test_setup(void)
> > sin0.sin_port = 0;
> > sin0.sin_addr.s_addr = INADDR_ANY;
> >
> > - devnull_fd = SAFE_OPEN("/dev/null", O_WRONLY);
> > -
> > socket_fd = SAFE_SOCKET(PF_INET, SOCK_STREAM, 0);
> > SAFE_BIND(socket_fd, (struct sockaddr *)&sin0, sizeof(sin0));
> >
> > @@ -88,7 +81,6 @@ static void test_setup(void)
> >
> > static void test_cleanup(void)
> > {
> > - SAFE_CLOSE(devnull_fd);
> > SAFE_CLOSE(socket_fd);
> > SAFE_CLOSE(udp_fd);
> > }
>
> Is this supposed to be part of the patchset?
>
> I don't mind, but if we are strict, it should be in another commit.
That removes ENOTSOCK test that is now handled in accept03, I suppose I
should have explained that better in the comit message.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2023-10-24 9:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 12:33 [LTP] [PATCH v2 0/4] Add tst_fd iterator API Cyril Hrubis
2023-10-16 12:33 ` Cyril Hrubis
2023-10-16 12:33 ` [LTP] [PATCH v2 1/4] lib: Add tst_fd iterator Cyril Hrubis
2023-10-16 12:33 ` Cyril Hrubis
2023-10-24 9:39 ` [LTP] " Richard Palethorpe
2023-10-24 9:39 ` Richard Palethorpe
2024-01-05 0:42 ` Petr Vorel
2024-01-05 0:42 ` Petr Vorel
2024-01-15 12:19 ` Cyril Hrubis
2024-01-15 12:19 ` Cyril Hrubis
2024-01-15 22:52 ` Petr Vorel
2024-01-15 22:52 ` Petr Vorel
2023-10-16 12:33 ` [LTP] [PATCH v2 2/4] syscalls: readahead01: Make use of tst_fd Cyril Hrubis
2023-10-16 12:33 ` Cyril Hrubis
2023-10-24 9:31 ` [LTP] " Richard Palethorpe
2023-10-24 9:31 ` Richard Palethorpe
2023-10-16 12:33 ` [LTP] [PATCH v2 3/4] syscalls: accept: Add tst_fd test Cyril Hrubis
2023-10-16 12:33 ` Cyril Hrubis
2023-10-24 9:26 ` [LTP] " Richard Palethorpe
2023-10-24 9:26 ` Richard Palethorpe
2023-10-24 9:34 ` Cyril Hrubis [this message]
2023-10-24 9:34 ` Cyril Hrubis
2023-10-16 12:33 ` [LTP] [PATCH v2 4/4] syscalls: splice07: New splice tst_fd iterator test Cyril Hrubis
2023-10-16 12:33 ` Cyril Hrubis
2023-10-23 15:59 ` [LTP] " Richard Palethorpe
2023-10-23 15:59 ` Richard Palethorpe
2023-10-24 7:56 ` Cyril Hrubis
2023-10-24 7:56 ` Cyril Hrubis
2023-10-24 9:33 ` Jan Kara
2023-10-24 9:33 ` Jan Kara
2024-01-04 23:11 ` Petr Vorel
2024-01-04 23:11 ` 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=ZTePqRn48CjcZT1T@yuki \
--to=chrubis@suse.cz \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=mszeredi@redhat.com \
--cc=rpalethorpe@suse.de \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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.