linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: npiggin@suse.de
To: stable@kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@vger.kernel.org
Subject: [2.6.27.stable][patch 0/6] page_mkwrite fixes
Date: Tue, 12 May 2009 16:23:46 +1000	[thread overview]
Message-ID: <20090512062346.554974013@suse.de> (raw)

Hi stable team,

This is the sequence of applicable fixes for 2.6.27.stable to solve
the page_mkwrite issues. The series solves 2 problems in the core APIs:
- the problem of incorrect return values (eg. causing SIGBUS when there is an
  OOM or page invalidation).
- the problem of insufficient synchronisation between mm and filesystem,
  which results in at least NFS being quite easily broken with mmap()ed
  writes.

And it also updates several filesystems to fix the issues on their side.

I think it has been agreed to get these fixes into .stable kernels (they
are all upstream).

One issue is that there are several filesystems (basically, any which
supply ->page_mkwrite) which could be broken but maybe have not had
anybody look at them yet (OCFS2, UBIFS maybe). Anyway, if fs maintainers
eventually do add any fixes here, it would be appreciated if you keep
.stable in mind as well.

Thanks,
Nick



             reply	other threads:[~2009-05-12  7:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  6:23 npiggin [this message]
2009-05-12  6:23 ` [2.6.27.stable][patch 1/6] mm: page_mkwrite change prototype to match fault npiggin
2009-05-12  6:23 ` [2.6.27.stable][patch 2/6] fs: fix page_mkwrite error cases in core code and btrfs npiggin
2009-05-12  6:23 ` [2.6.27.stable][patch 3/6] mm: close page_mkwrite races npiggin
2009-05-12  6:23 ` [2.6.27.stable][patch 4/6] GFS2: Fix page_mkwrite() return code npiggin
2009-05-12  6:23 ` [2.6.27.stable][patch 5/6] NFS: Fix the return value in nfs_page_mkwrite() npiggin
2009-05-12  6:23 ` [2.6.27.stable][patch 6/6] NFS: Close page_mkwrite() races npiggin
2009-05-12 22:07 ` [stable] [2.6.27.stable][patch 0/6] page_mkwrite fixes Greg KH

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=20090512062346.554974013@suse.de \
    --to=npiggin@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@vger.kernel.org \
    --cc=stable@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).