| 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
| ||
|
Message-ID: <AANLkTi=FrmB=u09wvLoXzQstnV3h-U58R728t3k6_-B-@mail.gmail.com> Date: Wed, 30 Mar 2011 17:51:27 +0530 From: Pavan Savoy <pavan_savoy@...y.com> To: linux-kernel@...r.kernel.org, alan@...rguk.ukuu.org.uk Subject: locks inside receive_buf Hi, Does holding a lock make any sense inside the line discipline's ops->receive_buf? I see the locks being held and released - during some calls like flush_to_ldisc, which end up calling receive_buf.... and yes, I would like to have a lock because, there are other functions in my ldisc driver executed in process context ... Is there some hints as to what should be the do's and don'ts inside the ldisc ops functions ? (say tty_wakeup ...) regards, Pavan -- 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/
Powered by blists - more mailing lists