linux-ext4 - Re: [PATCH 3/5] e2fsck: print a notice when we've started suppressing a problem code

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: <1D4F4E78-7F63-406D-9D35-09F716E04C43@dilger.ca>
Date:	Sun, 18 Mar 2012 17:17:20 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	Theodore Ts'o <tytso@....edu>
Cc:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH 3/5] e2fsck: print a notice when we've started suppressing a problem code

On 2012-03-18, at 1:52 PM, Theodore Ts'o wrote:
> Signed-off-by: "Theodore Ts'o" <tytso@....edu>
> ---
> e2fsck/problem.c |    5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/e2fsck/problem.c b/e2fsck/problem.c
> index 53e8e11..7d5b10d 100644
> --- a/e2fsck/problem.c
> +++ b/e2fsck/problem.c
> @@ -1868,6 +1868,11 @@ int fix_problem(e2fsck_t ctx, problem_t code, struct problem_context *pctx)
> 		if ((ptr->flags & PR_LATCH_MASK) &&
> 		    (ldesc->flags & (PRL_YES | PRL_NO)))
> 			suppress++;
> +		if (ptr->count == ptr->max_count + 1) {
> +			printf("...problem 0x%06x suppressed\n",
> +			       ptr->e2p_code);
> +			fflush(stdout);
> +		}


Did a patch ever land to allow an interactive e2fsck run to set
a sticky answer (y/n) for a particular problem?  I know it has
been proposed several times.

Cheers, Andreas





--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html