From: "Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kyler-keyword-lkml.9c0da5@lairds.com, linux-kernel@vger.kernel.org
Subject: Re: Fw: 2.6.23-rc3-mm1 UnionFS "BUG: atomic counter underflow"
Date: Sun, 2 Sep 2007 17:53:51 -0400 [thread overview]
Message-ID: <20070902215351.GA23966@filer.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <20070902135957.e0903bbe.akpm@linux-foundation.org>
On Sun, Sep 02, 2007 at 01:59:57PM -0700, Andrew Morton wrote:
> > On Sun, 2 Sep 2007 12:48:35 -0400 "Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu> wrote:
> > On Sun, Sep 02, 2007 at 04:56:34AM -0700, Andrew Morton wrote:
> > >
> > > fyi..
> >
> > I got a bunch of patches queued up that should fix a few things - quite
> > possibly this one too.
> >
> > I want to push the patches to korg, but in the mix is a fs/stack.c change &
> > corresponding ecryptfs fix that should go to Linus's tree. The rest of the
> > patches depend on this change.
> >
> > How do you want me to do this? I guess I'll just send all of them to lkml,
> > and say which ones should go where in the 00/xx mail.
>
> Let's do that as a starting point.
Alright, I'll try to spam the lists later today.
> Perhaps we can fast-track the ecryptfs fix into mainline if it fixes
> something there.
Not necessary, they aren't bugfixes for fsstack/ecryptfs.
> I don't want to kep the unionfs tree hanging around forever. We need to
> work out whether we want to merge it.
Agreed.
Josef 'Jeff' Sipek.
--
Reality is merely an illusion, albeit a very persistent one.
- Albert Einstein
prev parent reply other threads:[~2007-09-02 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070902045634.fd2d2a5f.akpm@linux-foundation.org>
2007-09-02 16:48 ` Josef 'Jeff' Sipek
2007-09-02 20:59 ` Andrew Morton
2007-09-02 21:53 ` Josef 'Jeff' Sipek [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=20070902215351.GA23966@filer.fsl.cs.sunysb.edu \
--to=jsipek@cs.sunysb.edu \
--cc=akpm@linux-foundation.org \
--cc=kyler-keyword-lkml.9c0da5@lairds.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®