From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: update max log size
Date: Mon, 11 May 2009 12:28:49 -0400 [thread overview]
Message-ID: <20090511162849.GA1430@infradead.org> (raw)
In-Reply-To: <4A085173.5040208@sandeen.net>
On Mon, May 11, 2009 at 11:25:23AM -0500, Eric Sandeen wrote:
> Christoph Hellwig wrote:
> > Commit a6634fba3dec4a92f0a2c4e30c80b634c0576ad5 in xfsprogs increased the
> > maximum log size supported by mkfs. Merged back the changes to xfs_fs.h
> > so the growfs enforced the same limit and the headers are in sync.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Ok, looks like kernelspace only cares about this during
> xfs_growfs_log_private(), and that's not actually implemented yet,
> right? So no worries about kernel<->userspace version correlation I think.
Indeed, I just did a quick grep what's actually using it.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-05-11 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 16:06 [PATCH] xfs: update max log size Christoph Hellwig
2009-05-11 16:25 ` Eric Sandeen
2009-05-11 16:28 ` Christoph Hellwig [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=20090511162849.GA1430@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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