From: "Stephen C. Tweedie" <sct@redhat.com>
To: Alan Cox <alan@redhat.com>
Cc: Stephen Tweedie <sct@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: O_DIRECT
Date: 27 Jun 2003 11:35:21 +0100 [thread overview]
Message-ID: <1056710121.2418.19.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <1056706819.2418.11.camel@sisko.scot.redhat.com>
Hi Alan,
On Fri, 2003-06-27 at 10:40, Stephen C. Tweedie wrote:
> On Thu, 2003-06-26 at 21:21, Alan Cox wrote:
> > So its now confirmed with 3 distros, two file systems and several
> > compilers. It certainly seems to be the O_DIRECT patches but I'll pull
> > the back out for the next -ac and check I guess
Ouch ouch ouch, there's nasty merge conflict between the O_DIRECT patch
and an existing 64-bit rlimit chunk in -ac3. You really, really want
the change below. :-) Marcelo's tree appears OK, and this is a common
code path for all filesystems in -ac, so it matches the failure patterns
that far.
Cheers,
Stephen
--- mm/filemap.c.~1~ 2003-06-27 09:58:08.000000000 +0100
+++ mm/filemap.c 2003-06-27 11:13:07.000000000 +0100
@@ -2995,8 +2995,8 @@
}
/* Fix this up when we got to rlimit64 */
if (pos > 0xFFFFFFFFULL)
- count = 0;
- else if(count > limit - (u32)pos) {
+ *count = 0;
+ else if(*count > limit - (u32)pos) {
/* send_sig(SIGXFSZ, current, 0); */
*count = limit - (u32)pos;
}
next parent reply other threads:[~2003-06-27 10:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200306262021.h5QKLhN10771@devserv.devel.redhat.com>
[not found] ` <1056706819.2418.11.camel@sisko.scot.redhat.com>
2003-06-27 10:35 ` Stephen C. Tweedie [this message]
2003-06-27 11:07 ` O_DIRECT Alan Cox
2004-07-20 17:27 O_DIRECT Shesha Sreenivasamurthy
2004-07-20 18:48 ` O_DIRECT bert hubert
[not found] ` <40FD6FCB.5020408@inostor.com>
2004-07-20 20:17 ` O_DIRECT bert hubert
2004-07-21 0:10 ` O_DIRECT Rob van Nieuwkerk
2004-07-21 14:45 ` O_DIRECT Devel
[not found] ` <40FE9F3F.2090205@inostor.com>
2004-07-22 9:46 ` O_DIRECT Devel
2004-07-24 9:56 ` O_DIRECT Rogier Wolff
2004-07-26 1:24 ` O_DIRECT Andrew Morton
2004-07-21 0:05 ` O_DIRECT Rob van Nieuwkerk
[not found] ` <40FEA382.8050700@inostor.com>
2004-07-21 17:20 ` O_DIRECT Rob van Nieuwkerk
[not found] ` <40FEAF70.4070407@inostor.com>
2004-07-21 18:15 ` O_DIRECT Rob van Nieuwkerk
2004-07-21 18:45 ` O_DIRECT Shesha Sreenivasamurthy
2004-07-21 23:18 ` O_DIRECT Shesha Sreenivasamurthy
2004-07-21 23:54 ` O_DIRECT Rob van Nieuwkerk
2004-07-22 0:00 ` O_DIRECT Shesha Sreenivasamurthy
2004-07-22 0:18 ` O_DIRECT Rob van Nieuwkerk
2004-07-22 0:48 ` O_DIRECT Shesha Sreenivasamurthy
[not found] <200208291113.g7TBDut26852@tench.street-vision.com>
2002-08-29 11:22 ` O_DIRECT Peter T. Breuer
2002-08-29 12:14 ` O_DIRECT Peter T. Breuer
-- strict thread matches above, loose matches on Subject: below --
2002-08-29 11:04 O_DIRECT Peter T. Breuer
2001-04-12 21:09 O_DIRECT Andrea Arcangeli
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=1056710121.2418.19.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®