reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Kaelyn Uhrain <Kaelyn.Alexi+reiserfs@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Quick & dirty r4 for 2.6.37
Date: Wed, 26 Jan 2011 21:49:39 +0100	[thread overview]
Message-ID: <4D4088E3.8080800@gmail.com> (raw)
In-Reply-To: <AANLkTi=Mi1QEC+Wjr5ka4uMZH72WytvsszC+yycRKaqq@mail.gmail.com>

Kaelyn Uhrain wrote:
> Here's a quick patch I just made for the resier4-for-2.6.36 patch to
> compile against the 2.6.37 sources.  To use, apply
> resier4-for-2.6.36.patch to the 2.6.37 kernel sources (ignoring the
> one rejected chunk which just adds a comment at the end of
> fs/fs-writeback.c) then apply this patch.  My patch is a revert of
> 766f9164193f6dda1497bbf3861060198421fb92 along with three very small
> one-liner changes to fix compilation issues; I haven't had a chance to
> test it beyond building the kernel itself, and won't until after I'm
> off work tonight.  I also make no claims as to the correctness of my
> patch since it is my first venture into the reiser4 and linux fs code.
>
> Cheers,
> Kaelyn
>   

Hello.

Correct, but not enough:
return value BIO_EOPNOTSUPP has gone with WRITE_BARRIER,
and vfs changes in default_llseek() now cause self-blocking in ->llseek()
reiser4 file operation path.

Actually, I have already prepared the patch for .37 at last weekends
(still testing), will be available soon.

Anyway thanks!
Edward.
 


      parent reply	other threads:[~2011-01-26 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 20:14 Quick & dirty r4 for 2.6.37 Kaelyn Uhrain
2011-01-26 20:30 ` Kaelyn Uhrain
2011-01-26 20:51   ` Edward Shishkin
2011-01-26 21:00     ` Kaelyn Uhrain
2011-01-26 20:49 ` Edward Shishkin [this message]

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=4D4088E3.8080800@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=Kaelyn.Alexi+reiserfs@gmail.com \
    --cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).