From: Jan Kara <jack@suse.cz>
To: Jeff Mahoney <jeffm@suse.com>
Cc: reiserfs-devel <reiserfs-devel@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] reiserfs: fix race in readdir
Date: Wed, 2 Apr 2014 20:29:01 +0200 [thread overview]
Message-ID: <20140402182901.GA15907@quack.suse.cz> (raw)
In-Reply-To: <20140402180955.GA13479@quack.suse.cz>
On Wed 02-04-14 20:09:55, Jan Kara wrote:
> On Wed 02-04-14 11:57:54, Jeff Mahoney wrote:
> > jdm-20004 reiserfs_delete_xattrs: Couldn't delete all xattrs (-2)
> >
> > The -ENOENT is due to readdir calling dir_emit on the same entry twice.
> >
> > If the dir_emit callback sleeps and the tree is changed underneath us,
> > we won't be able to trust deh_offset(deh) anymore. We need to save
> > next_pos before we might sleep so we can find the next entry.
> >
> > This can also affect non-xattr users of readdir, though the race is tighter.
> >
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Jeff Mahoney <jeffm@suse.com>
> The patch looks good to me so unless someone objects, I'll merge this
> patch with Linus.
Umm, actually, what if dir_emit() returns error? Previously we tried
again the same entry, now we continue with the next one. Is that intended?
If yes, please comment on that in the changelog.
Honza
> > ---
> > fs/reiserfs/dir.c | 9 +++++++--
> > 1 file changed, 7 insertions(+), 2 deletions(-)
> >
> > --- a/fs/reiserfs/dir.c
> > +++ b/fs/reiserfs/dir.c
> > @@ -179,6 +179,13 @@ int reiserfs_readdir_inode(struct inode
> > memcpy(local_buf, d_name, d_reclen);
> >
> > /*
> > + * deh_offset(deh) will be invalid if dir_emit
> > + * sleeps. We need to know the offset after
> > + * this one to continue.
> > + */
> > + next_pos = deh_offset(deh) + 1;
> > +
> > + /*
> > * Since filldir might sleep, we can release
> > * the write lock here for other waiters
> > */
> > @@ -196,8 +203,6 @@ int reiserfs_readdir_inode(struct inode
> > if (local_buf != small_buf) {
> > kfree(local_buf);
> > }
> > - // next entry should be looked for with such offset
> > - next_pos = deh_offset(deh) + 1;
> >
> > if (item_moved(&tmp_ih, &path_to_entry)) {
> > set_cpu_key_k_offset(&pos_key,
> >
> > --
> > Jeff Mahoney
> > SUSE Labs
> --
> Jan Kara <jack@suse.cz>
> SUSE Labs, CR
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2014-04-02 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 15:57 [PATCH] reiserfs: fix race in readdir Jeff Mahoney
2014-04-02 18:09 ` Jan Kara
2014-04-02 18:29 ` Jan Kara [this message]
2014-04-02 18:34 ` Jeff Mahoney
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=20140402182901.GA15907@quack.suse.cz \
--to=jack@suse.cz \
--cc=jeffm@suse.com \
--cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).