linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@intercode.com.au>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
	Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: BUG at fs/jbd/transaction.c:684 during setxattr on 2.5.75
Date: Mon, 14 Jul 2003 11:21:28 +1000 (EST)	[thread overview]
Message-ID: <Mutt.LNX.4.44.0307141118400.5269-100000@excalibur.intercode.com.au> (raw)
In-Reply-To: <200307122159.49778.agruen@suse.de>

On Sat, 12 Jul 2003, Andreas Gruenbacher wrote:

> please find attached fixes for three bugs I found while looking into this. 

Works for me (patch needs to be applied with -l).


- James
-- 
James Morris
<jmorris@intercode.com.au>



      reply	other threads:[~2003-07-14  1:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11 20:41 BUG at fs/jbd/transaction.c:684 during setxattr on 2.5.75 Stephen Smalley
2003-07-12 19:59 ` Andreas Gruenbacher
2003-07-14  1:21   ` James Morris [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=Mutt.LNX.4.44.0307141118400.5269-100000@excalibur.intercode.com.au \
    --to=jmorris@intercode.com.au \
    --cc=agruen@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@epoch.ncsc.mil \
    /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).