public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] Bug Report: diotest4 fails on mips64
Date: Wed, 3 Jul 2019 08:53:07 -0400 (EDT)	[thread overview]
Message-ID: <818477200.31466413.1562158387201.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <77f916ad-58e3-bf0c-e1e7-da8fc3397ba4@windriver.com>


----- Original Message -----
> Thanks for your work.
> 
> I will backport the patch to my project after merged.

Does it mean, that patch I posted fixes problem for you?

Do you have good/bad kernel version? I was looking at recent
upstream changes, but didn't spot anything that could explain
that EINVAL.

> 
> 
> --Hongzhi
> 
> 
> 
> On 6/28/19 7:09 PM, Jan Stancek wrote:
> >
> > ----- Original Message -----
> >> *Ltp:*
> >>
> >> latest master
> >>
> >>
> >> *Kernel:*
> >>
> >> After v5.1 ARCH=mips64
> >>
> >>
> >> *Error info:*
> >>
> >> diotest4 10 TBROK : diotest4.c:368: can't mmap file: Invalid argument
> >> diotest4 11 TBROK : diotest4.c:368: Remaining cases broken
> >>
> >>
> >> I think the first argument of mmap is invalid.
> >>
> >>   ?? >shm_base = (char *)(((long)sbrk(0) + (shmsz - 1)) & ~(shmsz - 1));
> >>
> >>   ?? >shm_base = mmap(shm_base, 0x100000, PROT_READ | PROT_WRITE,
> > I don't see any note why that mmap needs to be MAP_FIXED. I'd drop it,
> > let kernel pick an address:
> >
> > diff --git a/testcases/kernel/io/direct_io/diotest4.c
> > b/testcases/kernel/io/direct_io/diotest4.c
> > index e4616e400abd..bf200cd41a27 100644
> > --- a/testcases/kernel/io/direct_io/diotest4.c
> > +++ b/testcases/kernel/io/direct_io/diotest4.c
> > @@ -352,18 +352,14 @@ int main(int argc, char *argv[])
> >          total++;
> >
> >          /* Test-10: read, write to a mmaped file */
> > -       shm_base = (char *)(((long)sbrk(0) + (shmsz - 1)) & ~(shmsz - 1));
> > -       if (shm_base == NULL) {
> > -               tst_brkm(TBROK, cleanup, "sbrk failed: %s",
> > strerror(errno));
> > -       }
> >          offset = 4096;
> >          count = bufsize;
> >          if ((fd = open(filename, O_DIRECT | O_RDWR)) < 0) {
> >                  tst_brkm(TBROK, cleanup, "can't open %s: %s",
> >                           filename, strerror(errno));
> >          }
> > -       shm_base = mmap(shm_base, 0x100000, PROT_READ | PROT_WRITE,
> > -                       MAP_SHARED | MAP_FIXED, fd, 0);
> > +       shm_base = mmap(0, 0x100000, PROT_READ | PROT_WRITE,
> > +                       MAP_SHARED, fd, 0);
> >          if (shm_base == (caddr_t) - 1) {
> >                  tst_brkm(TBROK, cleanup, "can't mmap file: %s",
> >                           strerror(errno));
> >
> 

  reply	other threads:[~2019-07-03 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 10:32 [LTP] Bug Report: diotest4 fails on mips64 Hongzhi, Song
2019-06-28 11:09 ` Jan Stancek
2019-07-01  9:16   ` Hongzhi, Song
2019-07-03 12:53     ` Jan Stancek [this message]
2019-07-04  0:02       ` Jan Stancek
2019-07-04  7:44         ` Hongzhi, Song
2019-07-04  8:17           ` Jan Stancek
2019-07-04  8:29             ` Hongzhi, Song
2019-07-04  1:56       ` Hongzhi, Song

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=818477200.31466413.1562158387201.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.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