linux-kernel - Re: [PATCH 2/4] fsfreeze: manage kill signal when sb_start

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]

Message-ID: <51603799.9070008@gmail.com>
Date:	Sat, 06 Apr 2013 16:56:25 +0200
From:	Marco Stornelli <marco.stornelli@...il.com>
To:	Matthew Wilcox <matthew@....cx>
CC:	Linux FS Devel <linux-fsdevel@...r.kernel.org>,
	Chris Mason <chris.mason@...ionio.com>,
	Steve French <sfrench@...ba.org>,
	Theodore Ts'o <tytso@....edu>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	Miklos Szeredi <miklos@...redi.hu>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Anton Altaparmakov <anton@...era.com>,
	Mark Fasheh <mfasheh@...e.com>,
	Joel Becker <jlbec@...lplan.org>, Ben Myers <bpm@....com>,
	Alex Elder <elder@...nel.org>, xfs@....sgi.com,
	Mike Snitzer <snitzer@...hat.com>,
	Alasdair G Kergon <agk@...hat.com>,
	linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-cifs@...r.kernel.org, samba-technical@...ts.samba.org,
	linux-ext4@...r.kernel.org, fuse-devel@...ts.sourceforge.net,
	linux-ntfs-dev@...ts.sourceforge.net, ocfs2-devel@....oracle.com,
	linux-mm@...ck.org, Jan Kara <jack@...e.cz>
Subject: Re: [PATCH 2/4] fsfreeze: manage kill signal when sb_start_write
 is called

Il 06/04/2013 15:17, Matthew Wilcox ha scritto:
> On Sat, Apr 06, 2013 at 12:04:52PM +0200, Marco Stornelli wrote:
>> In every place where sb_start_write was called now we must manage
>> the error code and return -EINTR.
>
> If we must manage the error code, then these functions should be marked
> __must_check.
>

Yep, good point.

Marco
--
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/