From: Andrew Morton <akpm@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>, Jan Harkes <jaharkes@cs.cmu.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: wrong order of arguments of ->readdir()
Date: Mon, 16 Jul 2007 13:44:24 -0700 [thread overview]
Message-ID: <20070716134424.0cd870b4.akpm@linux-foundation.org> (raw)
In-Reply-To: <200707152359.l6FNx3oN023117@hera.kernel.org>
On Sun, 15 Jul 2007 23:59:03 GMT
Linux Kernel Mailing List <linux-kernel@vger.kernel.org> wrote:
> Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c9e3c2e3b0437d10a09b77769baf325b94aa436
> Commit: 7c9e3c2e3b0437d10a09b77769baf325b94aa436
> Parent: 53b67950026ee642b43615f46df22ec3d36b4a53
> Author: Al Viro <viro@ftp.linux.org.uk>
> AuthorDate: Sun Jul 15 20:59:31 2007 +0100
> Committer: Linus Torvalds <torvalds@woody.linux-foundation.org>
> CommitDate: Sun Jul 15 16:40:51 2007 -0700
>
> wrong order of arguments of ->readdir()
>
> Shows how many people are testing coda - the bug had been there for 5 years
> and results of stepping on it are not subtle.
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> ---
> fs/coda/dir.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/coda/dir.c b/fs/coda/dir.c
> index 9ddf5ed..898a86d 100644
> --- a/fs/coda/dir.c
> +++ b/fs/coda/dir.c
> @@ -470,7 +470,7 @@ int coda_readdir(struct file *coda_file, void *dirent, filldir_t filldir)
>
> ret = -ENOENT;
> if (!IS_DEADDIR(host_inode)) {
> - ret = host_file->f_op->readdir(host_file, filldir, dirent);
> + ret = host_file->f_op->readdir(host_file, dirent, filldir);
> file_accessed(host_file);
> }
> }
Today is not being a good day.
This bug was already fixed. The following mistakes were made:
a) Jan's patch was misleadingly titled "coda: avoid lockdep warning in
coda_readdir"
b) Jan's patch had no changelog
c) Jen's patch was not cc'ed to any mailing list
d) Al's patch was not sent to the maintainer. Nor to me. Nor was it
staged in any tree which I can get at so that I could inform people of
the upcoming conflict/duplication/etc.
Guys (and I mean all guys): things are really shit at present. Please try
to do better.
next parent reply other threads:[~2007-07-16 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707152359.l6FNx3oN023117@hera.kernel.org>
2007-07-16 20:44 ` Andrew Morton [this message]
2007-07-16 20:49 ` wrong order of arguments of ->readdir() Al Viro
2007-07-16 21:01 ` Andrew Morton
2007-07-16 23:04 ` Jan Harkes
2007-07-16 21:47 ` Jan Harkes
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=20070716134424.0cd870b4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.