From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: odd code in xfs_remove
Date: Thu, 10 Apr 2008 20:54:45 +0200 [thread overview]
Message-ID: <20080410185445.GA7521@lst.de> (raw)
unlike xfs_rmdir or xfs_rename xfs_remove always passes 0 instead of the
reserved blocks to xfs_dir_removename which means the latter always
operated in the ENOSPC mode. This seems rather strange to me, so a
second pair of eyes, especially on a tree with history back to day 0
would be nice.
next reply other threads:[~2008-04-10 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 18:54 Christoph Hellwig [this message]
2008-04-11 2:31 ` odd code in xfs_remove David Chinner
2008-04-11 7:40 ` Christoph Hellwig
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=20080410185445.GA7521@lst.de \
--to=hch@lst.de \
--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