linux-kernel - Re: [PATCH 2/2 v2] Unify rest of FAT messages.

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:	Thu, 11 Nov 2010 01:40:59 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Alexey Fisher <bug-track@...her-privat.net>
Cc:	linux-kernel@...r.kernel.org, joe@...ches.com
Subject: Re: [PATCH 2/2 v2] Unify rest of FAT messages.

Alexey Fisher <bug-track@...her-privat.net> writes:

>> It clealy can happen on all FSes, not only FAT. And I don't want to push
>> it (notification stuff) from FAT tree. (need the review from other guys).
>
> I do not blame FAT. It was just one example/usecase.

Yes. It is why I said the below.

>> IMHO, it should be kernel wide (or subsystem wide) notification system
>> even if you target is FAT-fs only.  (yeah, it's hard to push to
>> linus-tree than one FS though).
>
> Sound complicated. I will not get time for this, right now. Any way, at
> least if this patch set go upstream it will help investigate some FS
> related issues. For my work (Computer Forensic) it will be really
> helpful.

Also, yes. It would be complicate more or less than one FS. And maybe I
can understand why you want to concentrate FAT.

But I'm afraid to implement for only FAT. If there is not any some sort
of agreement by others, it may have to re-implement. If that happen, FAT
can be bothered by compatible (or have to maintain both of old and new
for a while). Because the notified data are some sort of ABI, IMO.

This is why I'm careful about this, and can't say easily - "let's try it
on FAT".

Thanks.
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
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/