linux-kernel - Re: [PATCH 2/2] io_getevents: Use timespec64 to represent timeouts

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] [day] [month] [year] [list]

Message-ID: <CABeXuvprdOGq1KgQocE9aRYomaFeT+b=-kR9G=C8V=Qs1LY8-w@mail.gmail.com>
Date:   Sat, 5 Aug 2017 20:44:23 -0700
From:   Deepa Dinamani <deepa.kernel@...il.com>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Al Viro <viro@...iv.linux.org.uk>,
        Thomas Gleixner <tglx@...utronix.de>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        y2038 Mailman List <y2038@...ts.linaro.org>,
        linux-aio@...ck.org, Benjamin LaHaise <bcrl@...ck.org>
Subject: Re: [PATCH 2/2] io_getevents: Use timespec64 to represent timeouts

> I guess these two functions are small enough that they could be merged
> into one, saving a few lines. Then again, fs/aio.c seems to generally use
> fairly short functions doing not too much at once, so your approach maybe
> fits better with the style of the subsystem.

I don't see a problem with combining the two functions either.
Unless someone has a strong preference, I will leave it the way it is
currently handled.

Thanks,
Deepa