linux-kernel - Re: [PATCH] Add explanation of I_DIRTY

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 6 Feb 2008 17:54:57 +0100
From:	Jan Kara <jack@...e.cz>
To:	Andreas Schwab <schwab@...e.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Add explanation of I_DIRTY_DATASYNC bit

On Wed 06-02-08 17:35:39, Andreas Schwab wrote:
> Jan Kara <jack@...e.cz> writes:
> 
> > Add explanation of I_DIRTY_DATASYNC bit.
> >
> > Signed-off-by: Jan Kara <jack@...e.cz>
> >
> > diff --git a/include/linux/fs.h b/include/linux/fs.h
> > index 56bd421..475125e 100644
> > --- a/include/linux/fs.h
> > +++ b/include/linux/fs.h
> > @@ -1280,7 +1280,10 @@ struct super_operations {
> >   * Two bits are used for locking and completion notification, I_LOCK and I_SYNC.
> >   *
> >   * I_DIRTY_SYNC		Inode itself is dirty.
> > - * I_DIRTY_DATASYNC	Data-related inode changes pending
> > + * I_DIRTY_DATASYNC	Data-related inode changes pending. We keep track of
> > + *		`	these changes separately from I_DIRTY_SYNC so that we
>                 ^
> 
> Looks like a typo.
  Oh, OK. Thanks for spotting this. Just next to tab ;). I'll resend a
patch without the typo.

										Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/